Most dental practices we audit have a Google ranking strategy from 2018 and zero AEO infrastructure. That means when a prospective patient asks ChatGPT 'who is a good Invisalign provider in downtown Toronto,' the engine pulls from sites with proper structured data and surfaces the three clinics that built for AI citation. Your clinic, with a single Services tab and no FAQPage schema, does not get named. The fix is mechanical, and the mechanics are public.
What AEO actually requires
Four things, ranked by impact. First, per-procedure pages with MedicalBusiness and Dentist schema rather than a single Services tab. Each procedure gets its own URL, its own headline, its own structured data block, and its own FAQ section. Second, FAQPage schema built from the questions your front desk actually fields, not the generic ones every dental SEO template ships with. Third, an llms.txt file at the root that tells AI crawlers which pages are canonical and how to read them. Fourth, a clean MedicalBusiness graph that connects your practice entity to your doctors, your locations, your accepted insurance, and your procedures.
Per-procedure pages: what they look like
A real per-procedure page for Invisalign runs 800 to 1,200 words, with sections on candidacy, on timeline, and on cost ranges carrying structured data, an FAQ section of eight to twelve questions, and a Dentist schema block that ties the page to your practice entity. The page links to your About the Doctors page, your Insurance Accepted page, and your contact form. It does not link out to a generic blog post about Invisalign, because that reads as thin content. For orthodontics specifically, the per-procedure pages are aligners, retainers, palatal expanders, lingual braces, ceramic braces, and Invisalign Teen. For general dentistry, the procedure list is crowns, implants, Invisalign, root canal, whitening, veneers, pediatric, oral surgery, and emergency dentistry.
FAQPage schema using real questions
Sit with your office manager for an hour and pull the top twenty questions patients call about in a week, and they will be specific. 'Does Dr. Lee take Manulife dental.' 'How much does an implant cost if I am paying out of pocket.' 'Can I get Invisalign if I have a crown.' Those are the questions the AI engines reward, not the generic 'what is Invisalign' that every template uses. The schema goes on the procedure pages, the About page, and the Insurance Accepted page.
llms.txt and the canonical signal
The llms.txt file at yourpractice.com/llms.txt tells AI crawlers which pages are canonical, how to describe the practice, and which procedure page is the authoritative source for each topic. It is a public standard rather than a trick, and the AI engines that read it are the ones citing dental practices today. We ship llms.txt at every build tier. The studio's own llms.txt is at spaceandstory.com/llms.txt, and the methodology is documented in our blog post on what answer engine optimization is.
The MedicalBusiness graph
This is where most dental sites lose. A clean MedicalBusiness graph connects your Dentist entity to each Physician entity (your doctors), each Place entity (your locations), each MedicalProcedure entity (your procedures), each AcceptedInsurance entity (your carriers), and the schedule and hours for each location. The AI engines build their internal knowledge graph from yours. If yours is incomplete, the engine fills in gaps with directory data, and the directory data is often wrong. We rebuild the graph as part of the Site tier and beyond.
Cite-met monitoring
Cite-met is the studio's monitoring tool. It runs your high-intent queries against ChatGPT, Perplexity, Gemini, Copilot, Claude.ai, and You.com on a monthly cadence and reports which engine named your clinic, which engine named a competitor, and which engine named a directory page. For dental practices the queries are typically the procedure-plus-city queries (Invisalign Toronto, dental implants Vancouver), the symptom queries (tooth pain dentist near me, broken crown emergency), and the insurance queries (does Manulife cover Invisalign). The monthly report is part of every retainer tier.
What this looks like in practice
The studio's own site pulls 32 percent of its traffic from AI engines, more than eleven thousand AI-engine visits in the last seven days, with ChatGPT, Perplexity, and Google AI Overviews as the top three referrers. The method runs on us before it runs on any client, which is the only proof we trust. The Starlit Homes case study at /work/starlit-homes documents the same pattern in the home builder vertical, and the dental version follows the same playbook with a different schema graph. If you want to see how this applies in adjacent compliance-aware verticals, see the lawyers hub and the custom home builders hub.
What to do next
The free audit reports which AI engines name your clinic today, which procedures are missing schema, and which questions your FAQPage should answer. We will quote below what you are paying your current agency, and we will publish the audit findings before you commit. If you would rather start with the cost breakdown, see the dental cost spoke.