How AI reads Aspen Dental
Aspen Dental earns a 27 out of 100 on AEO readiness — placing it at level 2 of AI agent compatibility. The practice network's homepage delivers some readable content, but a missing sitemap, absent AI crawler directives, and a near-zero identity layer mean most answer engines cannot reliably surface or cite the brand.
What AI sees
An AI agent visiting Aspen Dental today lands on a dental services homepage with navigable text but no machine-readable inventory of the site.
Without a valid sitemap, an agent has no structured index of Aspen Dental's hundreds of clinic location pages, service descriptions, or patient resources. The homepage yields readable headings and paragraph text covering dental services — cleanings, orthodontics, implants — but structured data coverage sits at only 20/100, meaning price ranges, service types, and provider credentials carry no schema.org markup. Content structure scores the highest at 50, so basic HTML hierarchy exists, yet robots.txt contains no Content-Signal directives to declare how the practice wants its content used for AI training or answer summarization. The net effect: an agent can read fragments but cannot assemble a reliable, citable profile of the brand.



Where it loses points
Identity and authentication signals score a flat zero — leaving AI agents with no verified mechanism to confirm that information originates from Aspen Dental itself.
How to fix it
Three targeted changes would move the needle fastest for Aspen Dental's AI agent discoverability.
Publish a sitemap.xml
Give AI crawlers and answer engines a structured URL inventory of every clinic location page and service offering.
sitemap.xml returns HTTP 404, so agents have no map to the hundreds of location and service pages the brand maintains across the country.
Generate /sitemap.xml listing all location and service pages with lastmod dates, serve it as application/xml, and add a Sitemap: directive at the top of robots.txt so every crawler finds it on first contact.
Add AI crawler rules to robots.txt
Declare explicit per-agent directives so GPTBot, ClaudeBot, and PerplexityBot know exactly which paths to index and cite.
robots.txt contains no user-agent blocks for any AI crawler, so each agent falls back to guessing — often conservatively — which paths to follow.
Add individual User-agent blocks for GPTBot, ClaudeBot, PerplexityBot, and Applebot-Extended each followed by Allow: / for the paths you want cited; this single file edit directly lifts the agent_discovery score from its current 35.
Publish an MCP Server Card
Expose a machine-readable capability declaration so agent platforms can auto-discover Aspen Dental's digital touchpoints.
No server card exists at /.well-known/mcp/server-card.json, which contributes to agent_interfaces sitting at only 18/100 — the second-lowest category score.
Serve a JSON document at /.well-known/mcp/server-card.json with serverInfo, a transport endpoint, and a capabilities block; this is the fastest path to appearing in agent-native discovery registries used by tools like ChatGPT plugins and Claude integrations.
Common questions
Why does Aspen Dental score zero on identity and authentication?
Does a missing sitemap really affect how AI answer engines respond about Aspen Dental?
What is the single fastest improvement Aspen Dental can make to its AEO score?
Is your own site ready for AI?
Run the same five-category analysis on any URL. Free, no account needed to start.
Check your own website free

