A listing page can outrank a competitor's without a line of structured data on it. Real estate schema markup doesn't change whether Google can find that page. It changes how accurately Google, and increasingly an AI answer, can describe what's on it once found.
That distinction matters because Google is blunt about what markup buys you. Its general structured data guidelines state plainly that valid markup doesn't guarantee a rich result or a ranking boost, even when a page is coded correctly.
JSON-LD is the format Google recommends. It's easier to maintain at scale than markup woven directly into the HTML.
What Google's structured data rules actually require
For a real estate brokerage or agent site, the closest fit in Google's documentation is LocalBusiness, and it comes with a catch. Google requires only two properties: a name and a postal address. Everything else, including phone number, hours, coordinates, price range and reviews, is recommended rather than mandatory.
The documentation doesn't mention real estate agents or property listings by name. It's written around physical locations like restaurants and stores, so a brokerage adapting it is filling gaps the spec never addressed directly.
Getting the basics right still matters most at the point of a rebuild, since it's easier to build markup into new templates than retrofit it page by page. That's one reason a website rebuild and a schema audit tend to happen together rather than as separate projects.
Real estate schema markup: which types matter
Individual listings need a different type than the brokerage itself. RealEstateListing describes one or more Offers tied to a property, whether the goal is to sell it or lease it.
It carries properties LocalBusiness doesn't, including datePosted and leaseLength, and connects to Offer objects that hold the actual transaction terms.
A single property page often needs both types working together: RealEstateListing for the property and offer details, LocalBusiness for the brokerage behind it. Neither substitutes for the other.
Local listing accuracy carries weight beyond schema markup itself. The same name, address and phone details that go into LocalBusiness markup also need to match what shows up on a Google Business Profile, and inconsistency between the two undercuts both.
Getting that alignment right is closer to ongoing SEO work than a one-time code change.
Why buyers starting on AI changes the stakes
The bigger shift isn't about Google's search results page at all. In June 2026, the National Association of REALTORS® reported that a Bank of America survey found one in five prospective buyers and current homeowners had already used AI tools or chatbots for homebuying research.
That usage skewed young: 28% of millennials and 32% of Gen Z said they'd used AI to support their home search.
Most of that usage is practical rather than exploratory. Buyers turn to AI mainly to estimate affordability and closing costs, get general education about the process, and research neighborhoods and property values, according to the same NAR reporting.
The same report found a stark gap: more than 60% of buyer-side real estate searches now start through an AI interface, yet fewer than 10% of agents turn up when someone asks an AI tool a location-based question about who to work with.
Structured data is part of what closes that gap, since it's one of the clearer signals a page can give about who a listing or an agent actually is. Pairing that groundwork with broader AI and automation work is what turns accurate markup into something a chatbot can actually surface.
Buyers aren't abandoning agents outright: 44% said they'd pay more for a human to verify what an AI tool told them. Getting the schema right is what gives that human something to be found next to.
Sources
- General Structured Data Guidelines — Google Search Central
- Local Business (LocalBusiness) Structured Data — Google Search Central
