Schema Markup for Real Estate Agents: Types, Facts and Checks

A real estate website can describe several different things: a person, their business, a service, a profile or a published guide. Putting the same type on every page can blur those distinctions. Our recommended first step is a short inventory: write down the URL, its main subject and the facts a visitor can actually see.

Google’s structured-data policies require markup to represent the visible content accurately. That makes the page inventory more useful than starting with a list of keywords you want to rank for. If a claim has no support on the page, adding it to JSON-LD does not make it true.

This guide is an implementation checklist for agents reviewing their websites with a developer. It does not establish that a particular business qualifies for every Google feature or that a change will cause an AI system to cite it.

Schema.org’s Person type describes an individual. Its RealEstateAgent type sits under LocalBusiness, with Organization and Place in its hierarchy. The latter is a business type, not a schema label that verifies a professional license. An individual profile and the business that person works with may therefore need separate descriptions.

Google’s local-business documentation recommends the most specific applicable LocalBusiness subtype. That is a reason to choose a type that fits an actual business, not to invent an office or add unrelated professional types. Names, contact details and locations still need to be accurate.

Our recommendation is to agree on the identities before implementation. If the brokerage, team and individual have different names, records or contact routes, document those differences. Do not silently assign the brokerage’s awards, sales history or reviews to an individual agent.

Google documents ProfilePage for qualifying pages focused primarily on one person or organization affiliated with the website. Its examples include an employee page and an author page. A directory listing many agents is a different page purpose; do not assume it qualifies merely because it contains bios.

Schema.org defines BlogPosting as a blog post. BreadcrumbList describes a chain of linked pages with an order. These can describe an article and its place on the site without pretending the article itself is the real estate business.

For example, this article is a BlogPosting published by AutoAuthority AI. Its subject is real estate schema. It is not a profile of an individual agent and does not turn our marketing company into a real estate brokerage.

The following is a hypothetical worksheet. Bracketed values are placeholders, not published facts about a client. Replace them only after verification; do not put the example into a live site unchanged.

Suppose /about-agent introduces [Agent name] and explains their role with [Brokerage name]. The person record describes [Agent name]. A separate organization or business record describes [Brokerage name]. The profile page connects to the entity it is primarily about, if the page meets the relevant profile guidance.

Now suppose /blog/[guide-slug] contains an original local guide. The article record describes that guide, with its own headline, canonical URL, author or publisher and real dates. Its navigation trail can connect Home, Blog and the guide. A matching business identity elsewhere in the graph does not make the guide a second business location.

For each proposed field, add three notes to the worksheet: where the visitor can see it, what source supports it and who must confirm a discrepancy. This catches a mistaken brokerage name or an invented address before a syntax validator gives the code a clean result.

Google’s review-snippet rules exclude self-serving reviews of a LocalBusiness or Organization from the star-review feature, including reviews embedded through a third-party widget. Do not assume that copying your own testimonials into AggregateRating earns review stars. Review the current feature’s eligibility and content rules before making an implementation decision.

Useful questions and answers can still help visitors, but Google’s documentation updates say its FAQ rich-result feature stopped appearing in Search on May 7, 2026. FAQ markup is not a promise of that retired search feature. Keep visible answers useful instead of selling a search appearance that is no longer offered.

Google’s generative-AI optimization guidance also says there is no special schema required for generative AI search. Accurate markup can be part of ordinary SEO work; it is not a universal way to get recommended by ChatGPT, Claude, Gemini, Grok or Perplexity.

Our recommended audit has three passes. First, read the page and verify the facts. Second, inspect and validate the structured data the page actually delivers. Third, compare the proposed search feature with its current documentation. Passing one check does not establish the other two.

If your audit finds an old brokerage, a wrong contact route or unsupported experience, correct the underlying page and its data together. If the page is inaccessible, use our AI crawler-access checklist to investigate that separate problem.

If the facts and markup are already sound, choose the next task by the page’s actual usefulness. The real estate AI SEO guide explains how this fits a wider content plan. For help reviewing the site and priorities, see our real estate AEO service page.