Schema markup is the code that tells AI engines exactly who you are, what you do, and where you operate. Without it, your website is essentially invisible to ChatGPT, Gemini, and Google AI, not because your content is bad, but because the bots can't resolve your identity with confidence.
This guide shows you how to implement it correctly for your real estate website, with complete JSON-LD code examples you can use today.
If you're new to AEO, start with What Is AEO and Why Every Real Estate Agent Needs It Now before diving into implementation. For the broader 7-step optimization framework, see How to Optimize for AEO and Get Your Real Estate Website Noticed by AI.
What Is Schema Markup?
Schema markup is structured data, code written in a format called JSON-LD that you add to your website. It doesn't change how your site looks to visitors. It changes how AI and search engines understand your site.
Think of it as a business card that you hand directly to every AI bot that crawls your website. Without it, AI has to guess what your site is about. With it, AI knows exactly who you are and what you do.
Schema markup follows the vocabulary defined at Schema.org, a shared standard created by Google, Microsoft, Yahoo, and Yandex. When you use Schema.org types correctly, every major AI engine and search platform can read and trust your structured data.
Why Schema Markup Matters for AEO
AI systems like ChatGPT, Gemini, and Google AI Overviews are trained to surface authoritative, clearly identified entities. If your website doesn't identify itself with structured data, you're not an entity in their model. You're just another webpage.
In a recent schema audit we conducted for a real estate client, 81% of their site pages had schema issues, missing required fields, wrong business types, or no structured data at all. That meant 81% of the site was essentially unreadable to AI bots looking to verify and recommend the brand.
Here's how schema connects to actual AI recommendations: schema tells AI who you are, AI cross-references that identity with your citations and content, and if everything is consistent and authoritative, AI includes you in its answers. Schema is the first link in that chain. Without it, the rest of your AEO work has nothing to anchor to.
Schema markup is not optional for AEO. It is foundational.
The 3 Schema Types Every Real Estate Agent Needs
Before adding any code, understand the hierarchy: RealEstateAgent is a subtype of LocalBusiness in Schema.org's vocabulary. That means you can include all LocalBusiness fields (geo coordinates, opening hours, service area) directly inside your RealEstateAgent block, you don't need two separate schema blocks for both. The examples below show you how to combine them correctly.
1. RealEstateAgent (with LocalBusiness fields included)
This schema identifies you as a licensed real estate professional and ties your entity to a specific geographic area. The expanded version below includes the sameAs property, which is especially important for AEO, it's how AI engines connect your website entity to your profiles on other platforms. That cross-platform verification is the core of entity recognition.
{
"@context": "https://schema.org",
"@type": "RealEstateAgent",
"name": "Your Full Name",
"image": "https://yourwebsite.com/headshot.jpg",
"description": "Licensed real estate agent serving [City], [State], specializing in [buyer/seller/luxury] clients.",
"url": "https://yourwebsite.com",
"telephone": "+1-000-000-0000",
"areaServed": "Your City, State",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "Your City",
"addressRegion": "FL",
"postalCode": "00000",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 00.0000,
"longitude": -00.0000
},
"openingHours": "Mo-Fr 09:00-18:00",
"sameAs": [
"https://www.zillow.com/agent/your-profile",
"https://www.realtor.com/realestateagents/your-profile",
"https://www.linkedin.com/in/your-profile",
"https://www.facebook.com/yourpage"
]
}The sameAs array is what tells AI engines that your website, your Zillow profile, your Realtor.com listing, and your LinkedIn are all the same entity. Without it, AI sees four separate entities instead of one authoritative one. See Schema.org RealEstateAgent documentation for the full list of supported properties.
2. FAQPage
FAQPage schema is the most powerful schema type for AEO because it lets you feed AI the exact questions buyers and sellers are asking, and the answers you want AI to surface. However, this schema must be used carefully.
Important: Google has explicitly warned against using FAQ schema for self-promotional content. FAQs that exist only to say "we're the best" are filtered out or penalized. The example below shows the correct approach, a genuinely useful, locally specific answer that AI engines actually want to surface.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does it take to sell a home in [Your City]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The average time to sell a home in [City] is currently around [X] days, depending on pricing, market conditions, and property type. Homes priced competitively in [Neighborhood] tend to sell faster than the metro average. Contact [Your Name] for a current market analysis specific to your property."
}
},
{
"@type": "Question",
"name": "What is the average home price in [Your Neighborhood]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "As of [Month Year], the median home price in [Neighborhood] is approximately $[X]. Prices vary by property size, condition, and proximity to [local landmark/school/transit]."
}
}
]
}Every FAQ entry should answer a question a real buyer or seller would type into ChatGPT. Include your city and neighborhood by name in both the question and the answer, that local specificity is what makes the content useful to AI and to the people reading it.
Step-by-Step Implementation Walkthrough
Here is the complete process from start to finish:
- Decide which pages need schema. At minimum: your homepage (RealEstateAgent), your About page (RealEstateAgent), any service area pages (LocalBusiness fields), and your FAQ page (FAQPage). Each page should have schema relevant to its content.
- Customize the templates above. Replace every placeholder, your name, city, coordinates, phone, URLs, and sameAs links, with your real information. Incomplete or placeholder data is worse than no schema.
- Add the code to each page. The JSON-LD block goes inside the
<head>tag of your webpage, wrapped in<script type="application/ld+json">tags. See the "Where to Add Schema" section below for platform-specific instructions. - Test each page with Google's Rich Results Test. Paste your page URL and confirm the schema validates correctly. See what a passing result looks like in the "How to Test Your Schema" section below.
- Fix any errors flagged by the validator. Red errors must be resolved. Yellow warnings are less critical but worth addressing. Common errors are listed in the "Mistakes to Avoid" section.
- Retest and confirm every page passes. Don't move on until each page shows a valid result. One broken schema block can undermine the authority of the entire site.
Where to Add Schema Markup
Schema markup goes inside the <head> tag of your webpage, wrapped in a script tag. How you access that depends on your platform.
WordPress: Install RankMath or Yoast SEO. Both have built-in schema tools that let you add structured data without touching code. RankMath in particular has a dedicated schema generator for local businesses and professionals.
Custom website: Add the JSON-LD block directly to each page's HTML <head> section, or pass the code to your developer with clear instructions. Reference Google's structured data guidelines for the technical specification.
Compass, kvCORE, or other platform-controlled sites: These platforms control your site's HTML, which means you may not have direct access to add JSON-LD to the head tag. Your options are: (1) request schema additions through your platform's support team, (2) use Google Tag Manager to inject schema if your platform supports GTM, or (3) create a standalone landing page on a domain you fully control where you can implement schema without restrictions. Each path has tradeoffs, GTM injection is the most practical for most agents on platform-controlled sites.
How to Test Your Schema
After adding schema, verify it's working correctly using these free tools:
- Google Rich Results Test: paste your URL and see exactly which schema Google detects and whether it passes validation.
- Schema.org Validator: checks your JSON-LD for syntax errors and missing required fields.
- Search Atlas: our preferred tool for ongoing schema monitoring, showing which pages pass, which fail, and how your schema compares to competitors.
What a passing test looks like
In Google's Rich Results Test, a passing result shows your schema type (RealEstateAgent, FAQPage, etc.) with a green checkmark and a label that says "Detected" or "Valid item." If you see warnings in yellow, those are non-critical issues worth fixing. If you see errors in red, those must be resolved, red errors mean the schema is invalid and Google is ignoring it entirely.
A passing FAQPage schema will show each question and answer pair listed in the test results, you can verify the content is being read correctly before it ever goes live.
Common Schema Mistakes to Avoid
- Missing @context or @type: These are required fields. Without them, the schema is invalid and ignored entirely.
- Wrong business category: Using LocalBusiness when you should use RealEstateAgent means AI doesn't know you're a licensed professional. Use the correct subtype.
- NAP mismatch with citations: Your schema name and address must match exactly what's on Zillow, Google Business Profile, and your other citation sources. One difference breaks one trust signal.
- Schema that doesn't match page content: If your About page schema says you serve Miami but your content talks about Tampa, AI flags this as inconsistent and reduces your authority score.
- Duplicate or conflicting schema blocks: Many WordPress themes and plugins auto-generate schema in the background. If you add manual schema on top, you may end up with two competing RealEstateAgent blocks with slightly different information, which confuses AI engines. Before adding anything new, check for existing schema by running your page through Google's Rich Results Test or viewing your page source and searching for "application/ld+json". Remove or disable any conflicting auto-generated schema first.
Frequently Asked Questions About Schema Markup
Yes. Schema markup is just code, there's no licensing fee or platform cost to use it. If you use a WordPress plugin like RankMath or Yoast, those have free tiers that cover schema functionality. The only cost is the time to implement it correctly, or the cost of having a developer do it for you.
No, schema is necessary but not sufficient. It tells AI who you are, but AI also cross-references your citations, content quality, and domain authority before making a recommendation. Think of schema as making you eligible to be recommended. Your citations, content, and backlinks determine whether you actually are.
Update your schema any time your business information changes, new phone number, new address, new service areas, new headshot. For FAQPage schema, update it whenever your market data changes (median prices, days on market) so the answers stay accurate. Stale data in schema can signal to AI that your information isn't being maintained.
Yes, in two ways. First, invalid schema (syntax errors, missing required fields) wastes the opportunity, AI simply ignores it. Second, misleading schema (claiming you serve areas you don't, or using self-promotional FAQs) can trigger a manual penalty from Google. The safest approach is to be accurate, specific, and consistent with the rest of your site content.
Metadata (meta title, meta description) is what appears in search result snippets, it's written for human readers. Schema markup is structured data written for machines, it tells AI and search engines what your content means, not just what it says. Both matter for visibility, but schema has a more direct impact on AEO because AI engines rely on structured signals to build their knowledge of your entity.
The Bottom Line
Schema markup is one of the highest-leverage AEO actions you can take. The RealEstateAgent schema with sameAs links establishes your entity. The FAQPage schema puts your expertise directly into AI answers. And the step-by-step process above, customize, implement, test, fix, retest, takes less than an hour to complete correctly for most agents.
Most agents don't have it. The ones who do have a measurable advantage in AI visibility starting on day one.
Want to check whether your current schema is set up correctly? The free check covers schema validation along with citations and domain authority, so you can see exactly what AI currently knows about you and what's missing. See how your schema scores today.