Read your results
Website checks¶
Every run of your brand tests your website for what stops AI from reading it. There are 19 website checks in all. A normal run shows 16 to 18 of them.
How the checks read your site¶
Each check reads up to 8 pages of your site as raw HTML, with no scripts run. That is the page AI crawlers read. Text that appears only after scripts run is missing for them, and for the website checks too.
Each website check gives one result:
| Result | Meaning |
|---|---|
| Pass | Nothing to fix |
| Warn | Works, but weaker than it could be |
| Fail | Missing or broken |
Each result also carries an impact: High, Medium or Low. The impact sets how much the check weighs in your Site score.
The 19 checks¶
The impact shown is the one a failing or warning row carries. A passing row counts too, at its own weight.
| Check | What it tests | Impact | Shown | The fix |
|---|---|---|---|---|
| Write a clear page title | The homepage has a title of 20 to 65 characters | High if missing, Medium if too short or long | Always | A title with your business name, what you do and your city, 40 to 60 characters |
| Write a page description | The description tag is there and at least 70 characters | Medium if missing, Low if short | Always | A 140 to 160 character description: what you do, where, and why pick you |
| Add a main heading | The homepage has exactly one main heading | Medium if none, Low if more than one | Unless scripts build the page | One H1 heading saying what you do and where |
| Add business information tags | Hidden business details machines read: name, address, phone, hours | High | Always | Have your AI add the ready-made tags before </head> |
| Add a questions-and-answers section | Questions and answers on your pages, with markup that matches the questions each page shows | High if none, Medium if the FAQ isn't marked up or its markup doesn't match the page | Always | Answer the suggested questions on a page, or paste the FAQ markup built from your page's own questions |
| Use a secure connection (https) | The site loads over HTTPS | High | Always | An SSL certificate, with every page sent to HTTPS |
| Make your site work on phones | The page is set up for phone screens | High | Always | A viewport tag in the page head |
| Make your pages load faster | The homepage answers within 1.8 seconds | High over 3.5 seconds, Medium over 1.8 | Always | Smaller images, browser caching, a faster host |
| Add a sitemap | A file at /sitemap.xml lists your pages |
Medium | Unless the site walls the file off | Publish a sitemap and name it in robots.txt |
| Let AI crawlers read your site | robots.txt lets AI search and assistant bots read the site | High if they are blocked from the whole site, Low if there is no file | Unless the site walls the file off | Remove the rule that blocks them, or add a robots.txt |
| Add an AI summary file (llms.txt) | An llms.txt file in its standard shape: a plain summary some AI tools may read. Google says it doesn't use one for Search. | Low | Unless the site walls the file off | Have your AI publish the ready-made llms.txt |
| Set one official address for each page | The page names its official address | Low | Always | A canonical link tag; most platforms add one |
| Say which language your site is in | The page states its language | Low | Always | lang="en", or your language, on the <html> tag |
| Add a link preview | Title, summary and picture for shared links | Low | Always | The og:title, og:description and og:image tags |
| Add more text to your pages | Enough words across the pages read | High under 300 words, Medium under 900 | Unless scripts build the page | Pages on what you do, who for, where, prices and common questions |
| Show your phone and email | A phone number or email in the page text | High if none, Medium if scripts hide them | Always | A phone and email as plain text in the header or footer |
| Describe your images | Most images have an alt description | Low | Only if the site has images | A short alt description on each image that matters |
| Show when your pages were updated | The site's own last-updated date is within a year | Low | Only if the site sends that date | Publish a real update with new detail |
| Make your main text readable without scripts | The page arrives with its content in the HTML | High | Only when scripts build the whole page | Turn on server-side rendering or pre-rendering |
When scripts build the whole page, Make your main text readable without scripts fails. Add a main heading and Add more text to your pages are then left out. Their results would be about text the check can't see.
A file the site walls off, such as robots.txt, is listed as unread rather than failed.
AI bots by job¶
On My website, click the Let AI crawlers read your site row in All site checks. It lists every AI bot your robots.txt speaks to. Each bot sits under the job its maker gives it:
| Job | What the bot does | Counts against you when blocked |
|---|---|---|
| Search | Builds the index AI search answers draw on | Yes |
| Assistant | Opens a page when someone asks the assistant about it | Yes |
| Training + answers | One switch for both model training and AI answers | Yes |
| Training | Collects pages to train AI models | No |
| Agent | Acts on the web for a person or a business | No, shown only |
| Older names | Old names Anthropic no longer uses, anthropic-ai and Claude-Web | No, shown only |
Each bot reads Allowed, Blocked site-wide or Blocked on some pages. The line in your file that decided it sits beside it. "Some pages" means a rule closes one of your own pages to that bot.
A rule your file gives every crawler is shown once above the list.
Blocking only the training bots passes the check. The row reads "Opted out of AI training · AI search can still find you." It is your call, and no fix is suggested.
Blocking a search or assistant bot from the whole site fails the check. So does blocking a training + answers bot.
We read your whole robots.txt, up to 500 KB. When a file is too long to read in full, the list says it may be incomplete.
The shared report sums the list in one line, such as "Search: all allowed · Training: 2 blocked".
The checks that matter most¶
My website shows 8 checks first, under Checks that matter most. They cover robots.txt, llms.txt, the business tags, the FAQ, the sitemap, the title, the description and the contact details.
The full list sits in the All site checks table on the same page, fails first. Each row links to its fix.
What they cost¶
The website checks are part of every run's fixed part, shown as Fixed part of each run. No AI model is involved, and there is nothing extra to pay per run. See the price card.
Checking a fix again between runs is a separate re-check, priced per re-check. See Confirm your changes are live.
FAQ¶
Why do I see 16 checks and my rival's report shows 18?¶
Some checks appear only when they apply. Describe your images needs images, Show when your pages were updated needs a date from the site, and a walled-off file shows as unread.
My site passes in my browser. Why does it fail here?¶
Your browser runs scripts; AI crawlers mostly don't. The checks read what arrives before any script runs.
When does a fixed check turn green?¶
On your next run. To confirm a fix sooner, ask your AI for a re-check.