AI Search Visibility for Real Estate Agents

Everything in this guide

6 pages, grouped by what you are trying to do.

What actually happens when someone asks an AI for an agent

When a buyer types "who is a good realtor in Kitsilano" into ChatGPT or Google's AI Mode, the assistant does not consult a ranked list of agents. It runs searches, retrieves a set of pages, reads them, and composes an answer out of what those pages say. Google describes this behaviour in its own documentation on AI features in Search: its systems break a question into related sub-questions, issue many searches at once, and assemble a response from what comes back. Google calls this query fan-out.

Two consequences follow, and they explain most of what agents get wrong. First, the unit of visibility is a passage, not a website. The assistant quotes a specific paragraph that answers a specific sub-question. A homepage that says "your trusted local expert" answers no sub-question at all, so it is retrieved and then discarded. Second, the assistant has to be able to read the page as text. If the fact lives inside a script that only runs in a real browser, a text-only retrieval pass does not see it.

This is why AI visibility work looks less like traditional SEO and more like technical writing. The job is to state the facts a buyer would ask about, in text, on a page a crawler can fetch.

Why most agent websites are never in the running

The failures cluster into a short list, and they are mostly mechanical rather than creative. In rough order of how often they decide the outcome:

• The crawler is blocked. AI assistants use named crawlers, and a robots.txt rule or a bot-filtering firewall rule can exclude them while leaving Googlebot alone. OpenAI documents OAI-SearchBot as the crawler behind ChatGPT search results, separate from its training crawler GPTBot, and blocking the wrong one removes the site from ChatGPT's search index.
• The content is JavaScript-only. Many agent sites load listings, neighbourhood pages, and even the agent bio through an embedded IDX widget that renders client-side. To a retrieval pass reading raw HTML, those pages are close to empty.
• The facts are implied rather than stated. "Serving the Lower Mainland since day one" gives an assistant nothing to quote. "Licensed in British Columbia since 2011, working in Vancouver and Burnaby" gives it a sentence it can attribute.
• The page answers no specific question. A site made of service pages and a contact form has no passage matching "what are closing costs in BC" or "how long do homes sit on the market in Burnaby."
• The business is described inconsistently. A different name, phone number, or brokerage across the site, Google Business Profile, and directory listings gives the assistant competing versions of the same entity and no reason to trust any of them.

What the evidence actually supports about AI adoption

There is a lot of unverifiable marketing arithmetic in this niche, including confident claims that a specific share of agents are "invisible" to AI. Those figures usually trace back to a vendor's own benchmark of its own product. What can be checked is how quickly the tools themselves have been adopted, and that is the part that matters for deciding whether to act now.

The National Association of Realtors' 2025 Technology Survey found that 32% of members had not yet used AI in their business, meaning roughly 68% had adopted it to some degree. RPR, which is owned by NAR, surveyed 225 US real estate professionals in early 2026 and reported 82% currently using AI, a figure HousingWire covered independently. Both come from industry bodies surveying their own members rather than from a company selling AI visibility services.

Note what they do and do not show. They measure agents using AI, not buyers using AI to choose agents. The honest read is that the tools are now normal inside the industry, and consumer-side use is growing, but nobody has published a credible, independent figure for how many buyers pick an agent this way. Act on the trend, not on a fabricated percentage.

The order to fix things in

The sequence matters more than the individual items, because the early steps gate the later ones. Writing better passages on a page an assistant cannot fetch changes nothing.

• Confirm the assistants can reach you. Check robots.txt for rules affecting OAI-SearchBot, PerplexityBot, and Google-Extended, and confirm your host or firewall is not silently blocking them.
• Confirm your pages render as text. View the page source, not the page. If your bio, service area, and listings are not in the raw HTML, that is the first real problem.
• State your core facts in plain sentences. Licence and jurisdiction, brokerage, cities worked, years active, property types, languages spoken.
• Add pages that answer the specific questions buyers ask, with the answer in the first two sentences rather than after a scene-setting introduction.
• Make the description of your business identical everywhere it appears, starting with your Google Business Profile and the brokerage's agent roster page.
• Add schema markup last, to remove ambiguity about who you are. It is a clarity tool, not the thing that gets you cited.

Where schema markup genuinely helps, and where it does not

Schema markup is the most oversold item on every AI visibility checklist in this industry. The claim is that adding it makes ChatGPT and AI Overviews cite you. No search or AI vendor supports that claim, and Google contradicts it directly: its guidance on AI features in Search states that structured data is not required for AI Overviews or AI Mode and that there is no special markup for AI features.

What schema does is remove guesswork about identity. It states, in a format built for machines, that this business has this name, this phone number, this location, and this service. That helps Google's Knowledge Graph resolve who you are with more confidence, and it helps any automated reader get the facts right instead of inferring them from prose. Those are real gains. They are just not the gain usually advertised.

One practical change worth knowing: Google deprecated FAQ rich results on 7 May 2026, so FAQPage markup no longer produces the expandable questions in search results. The markup still has value for AI systems reading the page, but if you added it expecting the SERP feature, that feature is gone.

How to tell whether any of it worked

Most agents cannot see the AI traffic they already receive, which makes the whole channel feel imaginary. The reason is attribution: many AI assistants send visitors without a referrer that analytics recognises, so the visit is filed under Direct alongside bookmarks and typed URLs. If you judge this work by the size of an "AI" channel in a default Google Analytics report, you will conclude nothing happened.

Two measurements are worth more than any dashboard. First, ask the assistants the questions your buyers would ask, in a fresh session without your own site open, and record whether you are named and which page gets cited. Repeat monthly, keeping the wording identical, so the comparison means something. Second, check your server logs for the named AI crawlers to confirm they are fetching your pages at all. A site no AI crawler visits has a retrieval problem no amount of writing will fix.

Search crawlers and training crawlers are not the same thing

A decision that trips up a lot of agents: whether to let AI companies use your content. It is worth separating into two questions, because the vendors do.

Most AI companies run at least two crawlers. One builds the search index the assistant consults when answering questions, and one collects data to train the underlying model. Perplexity's documentation names PerplexityBot as the crawler that surfaces and links sites in its results, and states plainly that it is not used to crawl content for AI foundation models. OpenAI draws the same line between OAI-SearchBot for search results and GPTBot for training.

So the honest framing is not "block AI or allow AI." You can decline to have your content train a model while remaining fully findable in that same company's assistant. Agents who block everything usually did not intend the second outcome, and it is the one that costs them referrals. Whichever you choose, read the vendor's own crawler page before writing the rule, because the names change and a stale robots.txt enforces a decision you no longer meant to make.

What to do when you are still not being named

Suppose you have done the work and the assistants still recommend someone else. Before assuming the whole idea does not work, narrow down which stage is failing, because the fix is different at each one.

• No AI crawler hits in your server logs: this is an access problem. Recheck robots.txt and your CDN or firewall bot settings, not your content.
• Crawlers fetch you, but your pages are not in the cited sources: your pages are being retrieved and passed over. That usually means no passage answers the specific question, so add pages built around the actual queries.
• You are cited for some questions and not others: this is normal and it is useful information. The questions where you appear tell you what your site is genuinely the best answer for; the gaps tell you what to write next.
• Competitors with weaker sites appear instead: look at what is being cited rather than at their homepage. It is often a single well-targeted page, sometimes on a third-party site like a portal profile or a local publication, not their website at all.
• You appear but the details are wrong: this is the consistency problem. The assistant found conflicting facts about you and picked one. Audit every place your business is described.

Frequently asked questions

Related reading from the blog

• How AI Search Is Changing the Way Buyers Find a Realtor
• What Is AEO (Answer Engine Optimization) for Real Estate Agents
• AI SEO vs. Traditional SEO for Real Estate Agents
• How Many Real Estate Agents Actually Show Up in AI Search
• Schema Markup for Real Estate Websites: What It Actually Does
• Real Estate Agent Website Checklist: What to Check First
• Does Redesigning Your Real Estate Website Hurt Your Google Rankings

Sources

Every claim on this page that could be checked against a primary source is linked below. Where something is not publicly documented by a vendor, the page says so rather than filling the gap with an estimate.

• AI features and your website (Google Search Central)
• OpenAI crawlers and user agents (OpenAI)
• PerplexityBot crawler documentation (Perplexity)
• Search Central changelog: removing the FAQ rich result (Google Search Central)
• REALTORS® Embrace AI, Digital Tools to Enhance Client Service (2025 Technology Survey) (National Association of Realtors)
• AI adoption reaches 82% among real estate agents, RPR reports (HousingWire)