AI agents have no map of your site
An llms.txt file is a short guide AI tools read to find your most important pages. Adoption is young, but the tools that do read it get a clean tour instead of guessing.
Site health
52/100
Why this score
Site checks69
half of the score
Speed58
a third of the score
Being found0
a fifth of the score
The fastest points are in being found. Start there and the score follows.
Can AI read you?
How easily AI tools can read and understand this site.
ChatGPTreads you
ChatGPT browsingreads you
ChatGPT searchreads you
Claudereads you
Perplexityreads you
Geminireads you
AI site map (llms.txt)missing
Machine readable identityFAQPage, BreadcrumbList
Doors open. Every AI platform we tested can read this site. Adding the missing pieces above helps them understand it, not just read it.
What the AI platforms say about you
What happens when each model is asked about this brand.
GPT
GPT has never heard of this brand
unknownClaude
Claude has never heard of this brand
unknownGrok
Grok has never heard of this brand
unknownGemini
Gemini has never heard of this brand
unknownWho AI recommends instead
The brands AI platforms suggest in this one's place.
| Brand | AI mentions | Best rank |
|---|---|---|
| Surfer SEO | 4 | #1 |
| Clearscope | 4 | #3 |
| Semrush | 3 | #1 |
| Ahrefs | 3 | #2 |
| MarketMuse | 3 | #4 |
| Frase | 2 | #2 |
| Frase.io | 1 | #2 |
| SE Ranking | 1 | #4 |
Tryprofound never appears in these answers.
Speed and stability
58
of 100 on a phone
Largest paint3.3s
Layout shift0.00
Responsiveness268ms
measured on real visits
Searches you could own
Queries near this brand that nothing points to yet.
marketing agents to winprofound's aeo guidechapter 1chapter 2promptologiefirst aeo auditbuild an aeo strategychapter 6
Everything we noticed
What stands out from this scan, worst first.
The search description on your home page gets cut off
Google shows about 160 characters. This one runs to 161, so the closing thought never reaches the reader.
The headings on your home page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The headings on your aeo-guide page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The title on your aeo-guide page is too long to fit in search results
Google cuts titles off near 60 characters. This one runs to 75, so the end disappears behind an ellipsis.
The headings on your aeo-guide/chapter-1 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The title on your aeo-guide/chapter-1 page is too long to fit in search results
Google cuts titles off near 60 characters. This one runs to 61, so the end disappears behind an ellipsis.
The headings on your aeo-guide/chapter-2 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The headings on your aeo-guide/chapter-3 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The headings on your aeo-guide/chapter-4 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The headings on your aeo-guide/chapter-5 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The headings on your aeo-guide/chapter-6 page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The title on your aeo-guide/chapter-6 page is too long to fit in search results
Google cuts titles off near 60 characters. This one runs to 64, so the end disappears behind an ellipsis.
The search description on your blog page gets cut off
Google shows about 160 characters. This one runs to 189, so the closing thought never reaches the reader.
The title on your blog/ai-shopping-journey-2025 page is too long to fit in search results
Google cuts titles off near 60 characters. This one runs to 74, so the end disappears behind an ellipsis.
The search description on your engineering page gets cut off
Google shows about 160 characters. This one runs to 177, so the closing thought never reaches the reader.
Sharing your features page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
Sharing your features/agent-analytics/crawlability page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
Sharing your features/answer-engine-insights/aeo-dashboard page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
Sharing your features/answer-engine-insights/citations page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
The search description on your features/answer-engine-insights/competitors page gets cut off
Google shows about 160 characters. This one runs to 171, so the closing thought never reaches the reader.
Sharing your features/answer-engine-insights/competitors page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
The search description on your features/answer-engine-insights/prompt-tracking page gets cut off
Google shows about 160 characters. This one runs to 206, so the closing thought never reaches the reader.
Sharing your features/answer-engine-insights/prompt-tracking page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
Sharing your features/answer-engine-insights/query-fan-out page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
Sharing your features/answer-engine-insights/sentiment page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.
The search description on your features/prompt-volumes page gets cut off
Google shows about 160 characters. This one runs to 207, so the closing thought never reaches the reader.
The headings on your features/prompt-volumes page skip a level
Headings jump straight from one size to a much smaller one, which breaks the outline for screen readers and for search engines reading the page structure.
The search description on your features/prompt-volumes/research-reports page gets cut off
Google shows about 160 characters. This one runs to 178, so the closing thought never reaches the reader.
Sharing your features/prompt-volumes/research-reports page produces a link with no picture
When someone posts this page to LinkedIn, WhatsApp, or Slack, it appears as a bare line of text. A share image is the difference between a link people click and one they scroll past.