Real Estate Listing Schema: What Agents Should Mark Up

At a glance

Sources: schema.org; Google Search Central Search Gallery (updated Oct. 16, 2026), feature docs and documentation updates log. Checked Oct. 25, 2026.

What the RealEstateListing type is

schema.org defines RealEstateListing as "a listing that describes one or more real-estate Offers (whose businessFunction is typically to lease out, or to sell)." It sits under WebPage, so it describes the listing page, not the house itself. It adds two properties of its own:

• datePosted: when the listing was published online.
• leaseLength: for rentals.

Because it's a WebPage, it inherits page properties such as breadcrumb, about, mainEntity and offers. schema.org lists it in its "new" area, which means the definition is still open to implementation feedback.

What Google does with it

Google's Search Gallery lists the structured data features Google Search supports. As of Oct. 25, 2026 it includes Article, Breadcrumb, Event, Image metadata, Local business, Organization, Profile page, Video, Vacation rental and others, but no real estate listing feature. Google's own guidance also says to rely on Search Central documentation, not schema.org, for how Google Search behaves.

Two adjacent features don't apply to sales listings:

• Vacation rental markup is limited to sites already connected with a Google Technical Account Manager and with access to Hotel Center.
• FAQ rich results are gone. Google stopped showing them on May 7, 2026 and removed the documentation in June 2026.

And for AI search, Google says there is "no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode. Its advice is to make sure structured data matches the visible text on the page.

So why mark up a listing at all?

• Clarity. Labeled fields (price, address, bedrooms, square footage) remove ambiguity for any system that parses the page.
• Consistency with MLS data. Several schema.org properties map to RESO fields. numberOfBathroomsTotal follows the RESO "Bathrooms Total Integer" convention, and yearBuilt corresponds to RESO's YearBuilt.
• The parts Google does support (photos, video, breadcrumbs, your brokerage identity) can change how your pages appear.
• Cost is low once it's in your listing template. Do it once, and every listing inherits it.

What it won't do: guarantee rankings, rich results or AI citations. Google says correct markup "does not guarantee" a feature will appear.

What to mark up on a listing page

1. The page: RealEstateListing with name, url, datePosted and image.
2. The offer: an Offer with price and priceCurrency ("USD"). businessFunction defaults to sell; set the lease value for rentals and add leaseLength.
3. The home: a residence type (SingleFamilyResidence, House, Apartment) with address (PostalAddress), numberOfBedrooms, numberOfBathroomsTotal, floorSize (a QuantitativeValue; unit code FTK for square feet), yearBuilt and amenityFeature. Connect it to the page with mainEntity or about.
4. The agent: offeredBy on the Offer, pointing to the listing agent (Person or RealEstateAgent) with the same name, brokerage and contact details used everywhere else.
5. Photos and video: ImageObject with creator and credit, and VideoObject for tours, following Google's image metadata and video docs.
6. Breadcrumbs: BreadcrumbList for Home > Listings > City > Address.

schema.org doesn't prescribe one way to connect the listing, offer and home. Validate your structure with the Schema Markup Validator and Google's Rich Results Test.

A JSON-LD example (placeholders only)

{
    "@context": "https://schema.org",
    "@type": "RealEstateListing",
    "name": "[Listing headline exactly as shown on the page]",
    "url": "https://www.example.com/listings/[listing-slug]",
    "datePosted": "[YYYY-MM-DD]",
    "image": ["https://www.example.com/photos/[photo-1].jpg"],
    "offers": {
    "@type": "Offer",
    "price": "[list price, numbers only]",
    "priceCurrency": "USD",
    "offeredBy": {
      "@type": "RealEstateAgent",
      "name": "[Agent or team name]",
      "url": "https://www.example.com/about"
    }
    },
    "mainEntity": {
    "@type": "SingleFamilyResidence",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "[Street address]",
      "addressLocality": "[City]",
      "addressRegion": "[State]",
      "postalCode": "[ZIP]",
      "addressCountry": "US"
    },
    "numberOfBedrooms": "[number]",
    "numberOfBathroomsTotal": "[number]",
    "floorSize": { "@type": "QuantitativeValue", "value": "[number]", "unitCode": "FTK" },
    "yearBuilt": "[year]"
    }
}

Illustrative only. Replace every bracketed value with what the page visibly shows, and validate before publishing.

Rules that matter more than the markup

• Match the page. Google's guidelines say structured data must represent the page's main content and must not describe content hidden from users. A price in the markup that isn't on the page, or an old price after a reduction, is a problem.
• Keep it current. When a listing goes under contract, sells or comes off the market, update or remove the offer markup the same day.
• Use JSON-LD. Google lists JSON-LD as its recommended format.
• Rendering counts. Google can read structured data that JavaScript adds to the page when it renders. But Google also says server-side or pre-rendering is still a great idea because "not all bots can run JavaScript." If your listing pages are built in the browser, check what a crawler actually receives.
• Don't mark up what you can't show. Off-market details, private remarks or unverified claims ("best view in the city") don't belong in markup.
• Manual actions are real. Misleading structured data can cost a page its rich-result eligibility. Google says that kind of manual action doesn't affect web ranking, but it removes the feature.

Questions to ask your web team or IDX vendor

• Does our listing template output JSON-LD, and which types?
• Is the markup in the HTML we serve, or only added by JavaScript?
• Does the markup update automatically when price or status changes in the MLS feed?
• Do our photos carry creator and credit metadata?
• Is our agent and brokerage name, address and phone identical in markup, on the page and on our profiles?
• Are we still adding FAQPage markup expecting a rich result?

Talk with an agent

Browse member agents in Find a Realtor.

Featured agents: Debbi DiMaggio & Adam Betta (DiMaggio + Betta Group | Corcoran Icon Properties, Piedmont, California) and Wesley Ulloa & Bianca Guevara (LUXE Properties, Coral Gables, Florida).

Related pages

• What Real Estate Agents Get Wrong About AI Search in 2026
• How to Track AI Overviews Traffic in Search Console
• Luxury Real Estate Advertising vs. Getting Cited in AI Search
• Luxury Real Estate Marketing: The 2026 Guide

Sources

1. schema.org, "RealEstateListing." https://schema.org/RealEstateListing (fetched 2026-10-25).
2. schema.org, "Offer." https://schema.org/Offer (fetched 2026-10-25).
3. schema.org, "Accommodation" (floorSize, numberOfBedrooms, numberOfBathroomsTotal, yearBuilt). https://schema.org/Accommodation (fetched 2026-10-25).
4. schema.org, "SingleFamilyResidence." https://schema.org/SingleFamilyResidence (fetched 2026-10-25).
5. schema.org, "RealEstateAgent." https://schema.org/RealEstateAgent (fetched 2026-10-25).
6. Google Search Central, "Structured data markup that Google Search supports" (Search Gallery; last updated 2026-10-16). https://developers.google.com/search/docs/appearance/structured-data/search-gallery (fetched 2026-10-25).
7. Google Search Central, "Latest Google Search Documentation Updates" (FAQ rich result deprecation May 8, 2026 and documentation removal June 2026; breadcrumb desktop-only Jan. 22, 2025). https://developers.google.com/search/updates (fetched 2026-10-25).
8. Google Search Central, "AI features and your website" (last updated 2025-12-10). https://developers.google.com/search/docs/appearance/ai-features (fetched 2026-10-25).
9. Google Search Central, "General structured data guidelines" (last updated 2026-07-10). https://developers.google.com/search/docs/appearance/structured-data/sd-policies (fetched 2026-10-25).
10. Google Search Central, "Intro to how structured data markup works." https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data (fetched 2026-10-25).
11. Google Search Central, "Generate structured data with JavaScript" (last updated 2025-12-10). https://developers.google.com/search/docs/appearance/structured-data/generate-structured-data-with-javascript (fetched 2026-10-25).
12. Google Search Central, "Understand JavaScript SEO basics." https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics (fetched 2026-10-25).
13. Google Search Central, "Vacation rental (VacationRental) structured data" (last updated 2026-09-08). https://developers.google.com/search/docs/appearance/structured-data/vacation-rental (fetched 2026-10-25).
14. Google Search Central, "Breadcrumb (BreadcrumbList)" (last updated 2026-09-08). https://developers.google.com/search/docs/appearance/structured-data/breadcrumb (fetched 2026-10-25).
15. Google Search Central, "Local business (LocalBusiness) structured data" (last updated 2026-09-08). https://developers.google.com/search/docs/appearance/structured-data/local-business (fetched 2026-10-25).
16. Google Search Central, "Organization" (last updated 2026-09-08). https://developers.google.com/search/docs/appearance/structured-data/organization (fetched 2026-10-25).
17. Google Search Central, "Image metadata" (last updated 2025-12-10). https://developers.google.com/search/docs/appearance/structured-data/image-license-metadata (fetched 2026-10-25).
18. Google Search Central, "Video structured data" (last updated 2026-09-24). https://developers.google.com/search/docs/appearance/structured-data/video (fetched 2026-10-25).
19. Schema Markup Validator. https://validator.schema.org/ and Google Rich Results Test. https://search.google.com/test/rich-results (both 200, 2026-10-25).

This article is general information about web markup, not a guarantee of search placement, rich results or AI citations.