Schema markup for real estate developers: what to mark up in 2026

Schema markup for real estate developers should cover four things: Organization on the corporate site, Place or ApartmentComplex for each project, Offer for prices and availability, and Event for public launches that meet Google's rules. FAQPage is still valid schema but no longer earns a rich result in Google. Markup helps engines understand your entities; it does not guarantee a display.

That last point matters. Much structured-data advice still promises stars and accordions in search results. For developers in 2026, the real benefit is clarity about who you are and what each project is.

01What does schema markup actually do for a developer in 2026?

Structured data tells search engines what a page is about in a machine-readable form. Google says Organization markup helps it "disambiguate your organization in search results" and can influence logos and knowledge panels.^[1] For a developer whose project names resemble other projects, or whose brand shares words with other companies, that disambiguation is the main value.

On AI features, Google is explicit: there is no special schema.org structured data needed to appear in AI Overviews or AI Mode, and structured data should match the visible text on the page.^[2] Schema supports understanding; it does not replace crawlable, accurate content.

02Which rich results does Google still support that matter to developers?

Fewer than many guides suggest. Google's search gallery lists the features it supports, and several common recommendations are gone; there is no dedicated rich result for residential projects.^[7]

03Which schema.org types fit a developer's site?

Organization (corporate site)

Use Organization on the home page or about page, with legalName, name, alternateName (Arabic name, short name), url, logo, address, contactPoint and sameAs links to your official profiles (LinkedIn, Wikidata if one exists, regulator listings, official social accounts). This is the anchor every project page should reference.

Schema.org also has RealEstateAgent, a subtype of LocalBusiness.^[6] It fits a brokerage or a developer's in-house sales centre with opening hours and a physical address; it is not the right type for the developer as a corporate entity.

Place, Residence and ApartmentComplex (project pages)

ApartmentComplex sits under Thing, Place and Residence, and adds properties such as numberOfAccommodationUnits, numberOfAvailableAccommodationUnits, petsAllowed and tourBookingPage.^[3] For a tower or apartment community, it is the closest fit. For villa communities, use Residence or Place with a clear description. Include geo coordinates, address, containedInPlace (the master community) and a link to the developer Organization.

Offer (pricing)

Attach an Offer with price or a price range, priceCurrency (AED or SAR), availability and validFrom or priceValidUntil, so that engines can tell which price is current. Only mark up prices you show on the page.

Event (launches)

Google's event guidelines require events to be bookable by the general public and held at a physical location, and they exclude promotions such as limited-time discounts.^[5] A public launch event or open house at a sales centre can qualify; an "early-bird price" campaign cannot.

BreadcrumbList and WebPage basics

Breadcrumb markup is still a supported Google feature,^[7] and it is cheap to add. For developers it also clarifies hierarchy: Home, then the master community, then the project, then the unit type. That structure helps engines understand that "Example Tower" belongs to "Example Community" and to your organization, rather than being a stand-alone name.

04How should developers handle multiple languages in schema?

Most UAE and Saudi developers publish in English and Arabic, and many add Russian, Chinese, Hindi or French pages. Each language version should carry markup in that language, but the entity identifiers should stay the same. Use one @id for the organization and one per project across all language versions, so that engines see five pages about one project rather than five projects.

Use alternateName for the Arabic or transliterated version of your company and project names. Buyers and AI engines often see the same project spelled several ways (with or without "The", in Arabic script, transliterated differently), and alternateName gives engines a documented link between them. Pair it with hreflang on the pages themselves.

05Where should markup live in a developer's CMS?

The safest pattern is to generate JSON-LD from the same structured fields that render the page: project name, price-from, currency, unit counts, handover quarter, coordinates. When marketing updates a price in the CMS, both the visible text and the markup change together. Hand-written JSON-LD pasted into a page template is where drift begins, because nobody remembers to update it when a campaign ends.

Agree who owns the fields. Sales usually owns prices and availability, marketing owns descriptions, and legal approves anything about handover or residency eligibility. A short field-ownership table saves months of mismatched markup.

06What does a project page JSON-LD look like?

A minimal example for an apartment project, with placeholder values. Replace every value with what the page actually shows.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example-developer.com/#org",
      "name": "Example Developer",
      "alternateName": "مطور المثال",
      "url": "https://www.example-developer.com/",
      "logo": "https://www.example-developer.com/logo.png",
      "sameAs": ["https://www.linkedin.com/company/example-developer"]
    },
    {
      "@type": "ApartmentComplex",
      "@id": "https://www.example-developer.com/projects/example-tower/#place",
      "name": "Example Tower",
      "description": "1–3 bedroom apartments in Example Community, handover expected Q4 2027.",
      "address": {
        "@type": "PostalAddress",
        "addressLocality": "Dubai",
        "addressCountry": "AE"
      },
      "geo": { "@type": "GeoCoordinates", "latitude": 25.0, "longitude": 55.0 },
      "numberOfAccommodationUnits": 240,
      "containedInPlace": { "@type": "Place", "name": "Example Community" }
    },
    {
      "@type": "Offer",
      "itemOffered": { "@id": "https://www.example-developer.com/projects/example-tower/#place" },
      "offeredBy": { "@id": "https://www.example-developer.com/#org" },
      "price": "1200000",
      "priceCurrency": "AED",
      "availability": "https://schema.org/InStock",
      "validFrom": "2026-10-01"
    }
  ]
}

Validate with Google's Rich Results Test and the Schema Markup Validator, and keep the markup generated from the same data that renders the page, so prices and dates cannot drift apart.

07What mistakes do developers make with schema?

08How do you check that markup stays correct?

Implementation is the easy part; drift is the risk. Build three checks into your routine:

• After every price or plan change, run the affected project pages through the Rich Results Test or the Schema Markup Validator and compare the Offer values with the visible page.
• Monthly, crawl the site and export every Offer price, unit count and handover description into a sheet. Compare it with the current fact sheet from sales.
• Quarterly, review sameAs links and alternateName values, especially after rebrands, new regulator listings or new official social accounts.

Search Console reports errors for supported features, but it will not tell you that a valid price is out of date. Only a comparison with your own fact source catches stale but valid markup, which is the kind most likely to reach buyers through search and AI answers.

09How does schema fit into AI visibility work?

Schema is one input among many. AI answers about developers draw heavily on portals, press, forums and official registries, as we describe in sources AI trusts. Clean markup helps engines connect those mentions to the right entity, which is especially useful when project names collide with other brands or places; see when ChatGPT confuses your company with another.

The work is rarely a one-time implementation. Prices, availability and handover dates change, new projects launch and language versions multiply. Keeping markup, page content and third-party sources aligned is part of the ongoing operating work OwnlyReal does as an AI marketing department for enterprises, through your CMS and approval chain.

For page structure, see the off-plan project landing page guide. For how measurement and fixes are run continuously, see how OwnlyReal works.