PPRD (v1.0)

Real Estate feed powered by web technologies

Abstract

Estate agents choose to list their properties on portals in a variety of ways, some choose to list manually through a CMS system, others prefer to provide a feed to one or more portals via their management system to eliminate the duplication of effort. Usually if an agent doesn’t use a management system, or uses one with limited feed functionality it has been hard to list properties automatically on portals.

PPRD (Property Pal Rich Data) is a feed designed for the modern web that allows estate agents to supply data to PropertyPal.com by utilizing their current website, if an agent maintains a list of properties on their own webiste, the feed allows them to transform it into an automated data feed thus allowing them to list details of their properties in one place and have those details replicated on portals.

PPRD is ideal if as an estate agent you:

PPRD is specifically designed to be easy to implement for any web developer with little additional effort beyond just building a normal website and to not have any visual or functional impact.

PPRD uses technologies that may already be in use on your site, and if they are not they should be somewhat familiar to any web developer, these are XML Sitemaps, HTML5 and RDFa.

In simple terms, you provide a XML Sitemap that lists all of the properties currently available on your website, then on your detail page you markup your HTML document using the RDFa the PPRD schema. PropertyPal then uses a crawler to access your sitemap and discover all of your listings extract the data and transform it into listings on PropertyPal.com.

Quick Start

This section is a short introduction to the steps involved in integrating PPRD into an existing website, the full schema listing all properties available is in the Schema section.

Step 1: Create a XML Sitemap

First, you need an XML Sitemap that lists all of the listings on your website, the sitemap should only contain links to listings so if you already have a sitemap or want to add additional links then create a second sitemap.

If possible, include the <lastmod> element for each link which should give the date and time the listing was last modified, if you include this updates can be published on PropertyPal.com within a matter of minutes whereas without it a 24 hour full update is performed.

For full details on how to build a sitemap, visit Google’s Build a sitemap page.

Example sitemap

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>http://amazingestateagents.com/94242</loc>
    <lastmod>2015-06-14T11:42:16</lastmod>
  </url>
  <url>
    <loc>http://amazingestateagents.com/94246</loc>
    <lastmod>2015-06-07T09:21:03</lastmod>
  </url>
  <url>
    <loc>http://amazingestateagents.com/94269</loc>
    <lastmod>2015-05-24T15:20:58</lastmod>
  </url>
  ...
</urlset>

While not specifically required for the PropertyPal crawler, its also a good idea to reference your new sitemap in your robots.txt file, this will allow search engines to pick up your new sitemap and help to get your website ranked higher in the search engines.

Example robots.txt

User-agent: *
Disallow:

Sitemap: http://amazingestateagents.com/listing-sitemap.xml
Sitemap: http://amazingestateagents.com/other-sitemap.xml

Step 2: Markup Listings With RDFa

The next step is to describe the structure of the data on your detail pages with RDFa, this essentially involves adding attributes to key elements within your web page so they can be picked up by our crawler. You can do this by adding property attributes to important elements and giving them a name.

In the below example we have identified the address, brief description and the status of the listing with the property attribute.

<!doctype html>
<html>
<head>
  ...
</head>
<body>
  ...
  <hgroup>
    <h1 property="pp:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="pp:brief">4 Bed Detached house</span>
      <span property="pp:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

Notice how the property names are prefixed with ‘pp:’, this is a namespace and is declared automatically by the crawler, all property names should be prefixed with ‘pp:’ but you can customize the prefix, should this happen to conflict with a different RDFa schema in use, this is discussed further in the Other Considerations section.

Step 3: Provide Extra Details

Because RDFa is based around adding attributes to html elements the example above requires the information to be included on the web page and therefore visible to the end user. This may not always be desirable, some information is not important to the end user such as a unique identifier for the property.

In the below example, you will see the addition of a ID to the document, the ID will allow PropertyPal it identify a property even if the URL changes on your website. But because its not information that is relevant to the end user then we have used the meta html tag in the head instead of placing it inside the body thus hiding it from the users of your website.

<!doctype html>
<html>
<head>
  <meta property="pp:id" content="12345" />
</head>
<body >
  ...
  <hgroup>
    <h1 property="pp:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="pp:brief">4 Bed Detached house</span>
      <span property="pp:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

An alternative approach would be to add the ID to another element within the document but use content to override the literal value of the element.

<!doctype html>
<html>
<head>
</head>
<body>
  ...
  <span property="pp:id" content="12345"></span>
  <hgroup>
    <h1 property="pp:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="pp:brief">4 Bed Detached house</span>
      <span property="pp:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

While this approach introduces a new HTML element it is a span and includes no literal value so it will not be displayed. This approach is less tidy than the meta tag but depending on the architecture of your website you this may be an easier option for you.

Step 4: Complete the schema

Now you have a basic web page setup that is declared as a listing, try and add as much information as you can from the Schema part of this document. The more data you can provide, the higher quality your listings will be when the make it onto PropertyPal.com.

Other Considerations

Custom Prefix

As discussed in step 2, the PropertyPal crawler automatically declares a namespace with a prefix of pp:, this is to simplify the implementation of PPRD, however in the unlikely event that you already use an RDFa schema with the same prefix, you can customize PPRD with the prefix attribute.

The below example includes an additional prefix attribute on the html element, which defines a namespace called xyz which uses the PropertyPal RDFa schema. Notice how the property names are now prefixed with xyx: instead of pp:.

<!doctype html>
<html prefix="xyz: http://docs.propertypal.com/pprd/1.0#">
<head>
  ...
</head>
<body>
  ...
  <hgroup>
    <h1 proeprty="xyz:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="xyz:brief">4 Bed Detached house</span>
      <span property="xyz:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

Alternative Parent Element

The crawler automatically assumes the html element and its child elements represent a listing, however should you include details of multiple listings on a page, for example with a listing and some similar properties, you may wish to have a standard include file which includes details such as the address and type of a property, this may duplicate some property attribute names in your document. e.g. you may have multiple pp:address elements.

In this instance you should be explicit about which element on the page holds all of the details of the listing using the typeof attribute.

In the example below, we have declared a namespace of xyz: and declared that the a div within the body represents the listing. Note that the prefix attribute in this case is also on the div tag, the prefix can be anywhere as long as it is on the same element or a parent of the typeof element.

Example: explicit type

<!doctype html>
<html>
<head>
  ...
</head>
<body>
  ...
  <div class="main-property" typeof="pp:Listing"
    prefix="pp: http://docs.propertypal.com/pprd/1.0#">
  <hgroup>
    <h1 proeprty="xyz:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="xyz:brief">4 Bed Detached house</span>
      <span property="xyz:status">For Sale</span>
    </h6>
  </hgroup>
  ...
  </div>
  ...
  <div class="similar-property">
    <hgroup>
      <h1 proeprty="xyz:address">
        4 College Drive, Belfast BT7 3LF
      </h1>
      <h6>
        <span property="xyz:brief">4 Bed Town House</span>
        <span property="xyz:status">For Sale</span>
      </h6>
    </hgroup>
  </div>
  ...
</body>

Using Other Schemas

PPRD is intended to be compatible with other schema’s commonly used with RDFa on web pages, the most popular of these being schema.org. If you already use schema.org on the same web page then you can continue to do so, for example if you used the schema.org ‘Residence’ type to describe the same listing the following would allow you to combine the two schemas.

<!doctype html>
<html>
<head>
</head>
<body
  vocab="http://schema.org/"
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="Residence pp:Listing">
  ...
  <hgroup>
    <h1 property="name pp:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="description pp:brief">4 Bed Detached house</span>
      <span property="pp:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

In the above example, the body is a pp:Listing and a schema.org Residence, the h1 is both the pp:address and the Residence name, the span is both a pp:brief and a Residence description.

This also works if schema.org or any other schema is given a prefix, just simply list every prefix in the prefix attribute.

<!doctype html>
<html>
<head>
</head>
<body
  prefix="schema: http://schema.org/ pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="schema:Residence pp:Listing">
  ...
  <hgroup>
    <h1 property="schema:name pp:address">
      7 Riverside, Gleno, Larne BT40 3JW
    </h1>
    <h6>
      <span property="schema:description pp:brief">4 Bed Detached house</span>
      <span property="pp:status">For Sale</span>
    </h6>
  </hgroup>
  ...
</body>

New Developments

PPRD supports reading new development details as well as regular listing details however this feature is turned off by default, please contact PropertyPal.com support if you require this feature.

Linking

New developments are crawled if they are linked to from a property details page, when providing a link, add the development property to the link, the crawler will follow the link and crawl the development details also. There is no need to include a development in the sitemap.

...
  <a property="pp:development"
    href="http://amazingestateagents.com/development/123">Development Details</a>
...

Declaring a Page

Like regular listings, new developments can be declared with the typeof attribute, however instead of pp:Listing use pp:Development.

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Development">
<head>  
  <meta property="pp:id" content="12345" />
</head>
<body>
  ...

  ...
</body>

If omitted, type attribute is assumed to be pp:Development if the crawler found the detail page via the pp:development href on a regular listing.

Marking Up Details

Marking up the details of a development listing is much the same as a normal listing and several of the properties are inherited, there are a few special attributes that apply just to developments though. Full details are in the pp:Development Schema.

Full Schema

The following sections describe all of the properties that can be read by the PropertyPal crawler. The properties and types can be used on any element but examples given use the recommended techniques for each property.

type: Listing

A type that will be identified and transformed into a listing on PropertyPal.com

Example

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>
</head>
<body>
  ...
</body>

Identification Properties

id

The unique identifier of the listing.

The id is usually not required to be presented to the user, so it is it can be included as a meta tag in the head of document.

Example

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  <meta property="pp:id" content="12345" />
</head>
<body>
  ...

  ...
</body>
branch

The unique identifier for the branch which is marketing the listing.

This will be used to link the property to an account on PropertyPal.com and used to route enquiries to the correct office. This can be your own identifier or if you prefer, one can be supplied by PropertyPal.com.

Example

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  <meta property="pp:branch" content="Belfast" />
</head>
<body>
  ...

  ...
</body>
agentref

A reference used by the estate agency to refer to the property.

This field while collected is not actively used by PropertyPal.com at this time.

Example

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  <meta property="pp:agentref" content="X123" />
</head>
<body>
  ...

  ...
</body>

Location Properties

address

The complete address of the property.

The address should be as complete as possible and include a full postcode, house number, building number, street, address line 2, county and if the property is not in the UK, the country.

The crawler tries its best to read every address, but the more help you can give it the better the results will be. You should seperate the elements of the address (such as street and town) with commas where possible to assist with parsing.

Example

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  ...
</head>
<body>
  ...
  <h1 property="pp:address">
    7 Riverside, Gleno, Larne BT40 3JW
  </h1>
  ...
</body>

If your website has a display address that doesn’t include much detail, then you can instead provide a meta element with the full address.

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  <meta property="pp:address" content="7 Riverside, Gleno, Larne BT40 3JW" />
</head>
<body>
  ...
  <h1>
    7 Riverside, Gleno
  </h1>
  ...
</body>
coordinate

The location of the property expressed as a comma separated latitude and logitude.

We may choose to ignore the coordinate if we think we can get a more accurate location.

<!doctype html>
<html
  prefix="pp: http://docs.propertypal.com/pprd/1.0#"
  typeof="pp:Listing">
<head>  
  <meta property="pp:coordinate" content="54.7992942234466,-5.8331061525578" />
</head>
<body>
  ...
  <h1 property="pp:address">
    7 Riverside, Gleno, Larne BT40 3JW
  </h1>
  ...
</body>

Price Properties

price

The price of the property.

Example: Price with currency

  ...
  <span class="price">
    <span>Asking price</span>
    <strong property="pp:price">£265,000</strong>
  </span>
  ...

Example: Price with currency and qualifier

If you include extra information with the price, the crawler will try its best to read as much as it can, such as this example where the crawler will identify the price as 265000, the currency as GBP and the price qualifier as ‘Asking Price’ without an special markup for the extra information.

  ...
  <span property="pp:price" class="price">
    <span>Asking price</span>
    <strong>£265,000</strong>
  </span>
  ...

Example: Price with rent period

In this example, the crawler will identify that the rental properties rent is payable per month without additional markup.

  ...
  <span property="pp:price" class="price">
    £550 per month
  </span>
  ...

Example: Price on application

If we the crawler can’t find the price, the listing will be marked as POA, so just specifying a price with the text POA is sufficient.

  ...
  <span property="pp:price" class="price">
    POA
  </span>
  ...
qualifier

The price qualifier.

  ...
  <span class="price">
    <span property="pp:qualifier">Asking price</span>
    <strong property="pp:price">£265,000</strong>
  </span>
  ...
rentperiod

The rent period of the price.

  ...
  <span class="price">
    <span property="pp:price">£550</span>
    <strong property="pp:rentperiod">per month</strong>
  </span>
  ...
currency

The currency of the price.

Currency symbols or currency codes are acceptable, if you used an image for a currency symbol or didn’t display it, you may wish to be explicit about the currency with a content attribute.

  ...
  <span class="price">
    <span property="pp:currency" content="GBP">£<span>
    <span property="pp:price">265,000</span>
    <strong property="pp:rentperiod">per month</strong>
  </span>
  ...
deposit

For rental properties, the deposit payable on the property.

  ...
  <span property="pp:deposit" class="deposit">
    <strong>£450</strong>
  </span>
  ...

Status Properties

available

For rental properties, the date the property is available to let.

Example

  ...
  <span property="pp:available">22nd July 2014</span>
  ...

Example: Computer readable value

The crawler supports a variety of date formats, but to be sure it is able to read your date, you can also provide a computer readable date with the content attribute.

  ...
  <span property="pp:available" content="2014-07-22">22nd July 2014</span>
  ...
status

The status of the listing, such as whether it is for sale, sale agreed, sold to let, let agreed or let.

Example: To let

  ...
  <span property="pp:status" class="status">
    For Sale
  </span>
  ...

Example: To let

  ...
  <span property="pp:status" class="status">
    To Let
  </span>
  ...

Example: To let alternatively described as for rent

  ...
  <span property="pp:status" class="status">
    For Rent
  </span>
  ...

Descriptive Properties

propertytype

The type of property being advertised, this can be any string but the crawler will attempt to convert it to one of the fixed list of available types on PropertyPal.com

Example: Residential property

  ...
  <span property="pp:propertytype" class="price">
    Semi-detached House
  </span>
  ...

Example: Commercial property

  ...
  <span property="pp:propertytype" class="price">
    Industrial Unit
  </span>
  ...
furnishing

For rental properties, the furnishing status of the property, such as unfurnished, part furnished, fully furnished etc…

Example

  ...
  <span property="pp:furnishing">Unfurnished</span>
  ...
heating

The heating type of a property

Example

  ...
  <span property="pp:heating">Gas</span>
  ...
bedrooms

The number of bedrooms for a residential listing.

Example: Absolute value

  ...
  <dl>
    <dt>Bedrooms </dt>
    <dd property="pp:bedrooms">4</dd>
  </dl>
  ...

Example: Free text

If the value includes the word ‘bedrooms’, ‘beds’ or similar the crawler will still be able to read it and extract the important information.

  ...
  <span property="pp:bedrooms">4 Bedrooms</span>
  ...
receptions

The number of reception rooms for a residential listing.

Example: Absolute value

  ...
  <dl>
    <dt>Reception Rooms </dt>
    <dd property="pp:receptions">4</dd>
  </dl>
  ...

Example: Free text

If the value includes the word ‘receptions’, ‘reception rooms’ or similar the crawler will still be able to read it and extract the important information.

  ...
  <span property="pp:receptions">4 Reception Rooms</span>
  ...
bathrooms

The number of bathrooms rooms for a residential listing.

Example: Absolute value

  ...
  <dl>
    <dt>Bathrooms </dt>
    <dd property="pp:bathrooms">4</dd>
  </dl>
  ...

Example: Free text

If the value includes the word ‘bathrooms’ or similar the crawler will still be able to read it and extract the important information.

  ...
  <span property="pp:bathrooms">2 Bathrooms</span>
  ...
student

Flag to mark a property as a student listing.

Example

...
<head>  
  <meta property="pp:student" content="true" />
</head>
...

For boolean properties, the crawler also understands ‘yes’.

parking

Flag to mark a property as having off street parking

Example

...
<head>  
  <meta property="pp:parking" content="true" />
</head>
...

For boolean properties, the crawler also understands ‘yes’.

garage

Flag to mark a property as having a garage

Example

...
<head>  
  <meta property="pp:garage" content="true" />
</head>
...

For boolean properties, the crawler also understands ‘yes’.

garden

Flag to mark a property as having a garden

Example

...
<head>  
  <meta property="pp:garden" content="true" />
</head>
...

For boolean properties, the crawler also understands ‘yes’.

newhomes

Identify a property as part of a new development or a newly build property. This property is set automatically if using the development property.

Example: Basic usage

...
<head>  
  <meta property="pp:newhome" content="true" />
</head>
...

For boolean properties, the crawler also understands ‘yes’.

development

For listings that are part of a development, it is possible to provide a development detail page which can also be published to PropertyPal.com, however this is an advanced use case which is turned off by default. You should contact ProprtyPal.com to discuss this further.

This feature is discussed further in New Developments.

Example: Advanced usage

In the advanced configuration, provide a URI to the new development page using one of the following techniques.

...
  <a property="pp:development"
    href="http://amazingestateagents.com/development/123">Development Details</a>
...

or

...
  <link property="pp:development" href="http://amazingestateagents.com/development/123" />
...
description

The description of the property including any structured html markup that is required to display correctly. The crawler will sanitise the html before it finds its way onto PropertyPal.com so the final listing may not include all styling present in the source document.

Example

...
  <h3>Additional Information</h3>
  <div property="pp:description">
    <p>
      Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
    </p>
  </div>
...

If you have multiple description elements seperated in the layout of the page you can wrap them in a container element or include multiple references to pp:description.

bullets

A description element including bullet points that will be displayed above the main description. Though the property can be on any element, only list items contained within a list such as a ul or ol element will be read by the crawler.

...
  <h3>Additional Information</h3>
  <ul property="pp:bullets>
    <li>Exposed log burner.</li>
    <li>Laura Ashley interior design</li>
    <li>Luxury ensuite and family bathroom</li>
    <li>A must see home</li>
  </ul>
...
auctionlot

If the property is up for auction, this property specifies the auction Lot number.

Example

...
  <h1>
    (<span property="pp:auctionlot">LOT 4</span>)
    <span property="pp:address">7 Riverside, Gleno, Larne BT40 3JW</span>
  </h1>
...

Resource Properties

photo

Used to identify a photograph of a listing, add to a tags or img tags it provide URLs to images.

Example: a tag

Add the photo property to a tags and the crawler will download the linked image and add to listings as photographs.

...
  <ul class="thumbs">
    <li>
      <a property="pp:photo"
        href="http://amazingestateagents.com/photographs/94246-1.jpg">
        <img src="http://amazingestateagents.com/photographs/94246-1-thumb.jpg" />
      </a>
    </li>
    <li>
      <a property="pp:photo"
        href="http://amazingestateagents.com/photographs/94246-2.jpg">
        <img src="http://amazingestateagents.com/photographs/94246-2-thumb.jpg" />
      </a>
    </li>
    <li>
      <a property="pp:photo"
        href="http://amazingestateagents.com/photographs/94246-3.jpg">
        <img src="http://amazingestateagents.com/photographs/94246-3-thumb.jpg" />
      </a>
    </li>
    ...
  </ul>
...

Example: img tag

Add the photo property to img tags and the crawler will download the linked image and add to listings as photographs.

...
  <ul class="slideshow">
    <li>
      <img property="pp:photo"
        src="http://amazingestateagents.com/photographs/94246-1-thumb.jpg" />
    </li>
    <li>
      <img property="pp:photo"
        src="http://amazingestateagents.com/photographs/94246-2.jpg" />
    </li>
    <li>
      <img property="pp:photo"
        src="http://amazingestateagents.com/photographs/94246-3.jpg" />
    </li>
    ...
  </ul>
...

Example: Provide large images to PropertyPal.com

If only small images such as thumbnails are directly linked from your detail page you can override the image URL with the content attribute.

<ul class="slideshow">
  <li>
    <img property="pp:photo"
      content="http://amazingestateagents.com/photographs/94246-1-huge.jpg"
      src="http://amazingestateagents.com/photographs/94246-1-thumb.jpg" />
  </li>
  <li>
    <img property="pp:photo"
      content="http://amazingestateagents.com/photographs/94246-2-huge.jpg"
      src="http://amazingestateagents.com/photographs/94246-2.jpg" />
  </li>
  <li>
    <img property="pp:photo"
      content="http://amazingestateagents.com/photographs/94246-3-huge.jpg"
      src="http://amazingestateagents.com/photographs/94246-3.jpg" />
  </li>
  ...
</ul>
brochure

Identify brochure downloads such as PDF files.

Example

...
  <a property="pp:brochure" href="http://amazingestateagents.com/94246.pdf">
    Download Brochure
  </a>
...

EPCs

epc

The epc rating of the property in the shorthand format such as ‘D55/C71’.

Example: Current rating only

...
  EPC Rating: <span property="pp:epc">D55</span>
...

Example: Current and potential

...
  EPC Rating: <span property="pp:epc">D55/C71</span>
...

Example: Just the numbers

...
  EPC Rating: <span property="pp:epc">55/71</span>
...
co2

The co2 rating of the property in the shorthand format such as ‘D55/C71’.

Example: Current rating only

...
  CO2 Rating: <span property="pp:co2">D55</span>
...

Example: Current and potential

...
  CO2 Rating: <span property="pp:co2">D55/C71</span>
...

Example: Just the numbers

...
  CO2 Rating: <span property="pp:co2">55/71</span>
...
epcdocument

Identify EPC document downloads when EPC ratings are not available.

Example

...
  <a property="pp:epcdocument" href="http://amazingestateagents.com/94246-epc.pdf">
    Download EPC
  </a>
...
epcchart

Identify EPC chart images when EPCs are not available as ratings.

Example

...
  <a property="pp:epcchart" href="http://amazingestateagents.com/94246-epc.png">
    Download EPC
  </a>
...
co2chart

Identify EPC chart images when EPCs are not available as ratings.

Example

...
  <a property="pp:co2chart" href="http://amazingestateagents.com/94246-co2.png">
    Download EPC
  </a>
...

type: Development

A type that will be identified and transformed into a development on PropertyPal.com, this feature is off by default please contact PropertyPal.com support if you wish to provide details of new developments.

This feature is discussed further in New Developments.

Development Properties

id

The unique identifier of the development.

The id is usually not required to be presented to the user, so it is it can be included as a meta tag in the head of document.

Example

  <meta property="pp:id" content="12345" />
name

The name of the development

Example

  <h1 property="pp:name">Millreagh</h1>
developer

The name of the developer who build the development.

Example

  <p>Build by <span property="pp:developer">Dingles Builders (NI) Ltd</span></p>
branch

The branch property for the development like the regular listing is a unqique identifier for the development, however it differs from in its usage in that it can be used multiple times for each branch which is selling the new development.

Example

<meta property="pp:branch" content="Belfast" />
<meta property="pp:branch" content="North Down" />

Inherited Properties

The following properties are inherited from the Listing type.