Composite example — Fernhollow Dental is not a client and these figures are illustrative. The sections, the quotes, the denominators and the fix text are produced by the same renderer that makes a client's report.
What AI gets wrong about your locations
7 contradiction(s) across 3 of 5 location(s), from 246 statements checked.
The same fact, wrong at several locations
Insurance accepted is wrong at 2 locations
Cedar Park, Round Rock · 2 engine(s): ChatGPT, Perplexity
“Fernhollow Dental in Cedar Park does not appear to accept Delta Dental. You may want to call to confirm.”
ChatGPT · asked: “which dentist in Cedar Park takes Delta Dental?”
We checked 46 statements against 4 declared fact(s) here and found no contradictions.
Pflugerville
Nothing wrong.
We checked 43 statements against 4 declared fact(s) here and found no contradictions.
Hutto
Not measured — the fact check did not run for this location.
Every quote above is the engine's own wording, checked to appear in its answer. A statement we could not stand behind calling wrong is reported as unverifiable, never as wrong.
Can AI read your sites?
AI crawlers do not run JavaScript and they obey robots.txt. A page they cannot fetch or cannot read is invisible to them however good it looks in a browser.
fernhollowdental.example
6 locations share this site: Cedar Park, Round Rock, Leander, Georgetown, Pflugerville, Hutto. One site, so one result.
AI crawler
robots.txt
GPTBot
allowed
OAI-SearchBot
allowed
ClaudeBot
not mentioned
PerplexityBot
disallowed
Google-Extended
not mentioned
BingBot
allowed
CCBot
disallowed
PerplexityBot is disallowed in robots.txt, and Perplexity still answered about this practice from third-party pages — blocking the crawler does not stop the answer, it only removes your own site from what the answer is based on.
llms.txt: absent
Server-rendered text: rendered (612 words)
One fetch of one page per site, with JavaScript off. It proves the server sent readable text; it cannot prove every page does.
Diagnosis only — nothing in this section contributes to any score.
Where you show up
Supporting context, not the headline. AI answers vary run to run, so these are frequencies across sampled answers rather than rankings.
Location
Mention rate
Answers
Cedar Park
42%
50
Round Rock
36%
50
Leander
28%
50
Georgetown
31%
50
Pflugerville
26%
50
Hutto
8%
50
No engine named you at all for: Hutto. That is a visibility problem rather than an accuracy one — there was nothing for a wrong answer to be wrong about.
Fixes
Cedar Park
Cedar Park — insurance list, corrected
Corrects your insurance — ChatGPT said “Fernhollow Dental in Cedar Park does not appear to accept Delta Dental. You may want to call to confirm.”
Insurance accepted at Cedar Park
---------------------------------
Delta Dental PPO — accepted
Cigna PPO — accepted
MetLife PDP Plus — accepted
Publish this list on the Cedar Park location page as text, not inside an image, and repeat it in the page's schema.org MedicalBusiness block so an assistant that never renders the page can still read it.
Round Rock
Round Rock — Saturday hours as structured data
Corrects your hours — Perplexity said “Fernhollow Dental in Round Rock is closed on weekends.”
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "08:00",
"closes": "14:00"
}
]
Add this to the Round Rock page's existing schema.org block. The visible hours table already says Saturday 8–2; nothing an assistant can parse did.
Leander
Leander — name the dentist on the page
Corrects your providers — Google Gemini said “The Leander office is led by Dr. Dilber Bulsara, DDS.”
Dentists at Leander
-------------------
Dr. Priyanka Agrawal, DDS — general and cosmetic dentistry
The Leander page lists no dentist by name, so an engine with nothing to read invented one. Publish the name as text and as a schema.org `employee` entry.
Grouped by location, and scoped to this run group. Corrections generated from earlier runs are in your fix list.