Can AI assistants read accountingtoday.com?
Measured on 2026-09-19 by asking the site 7 times — once as a browser, once as each of the
6 crawlers that feed ChatGPT, Claude, Perplexity, Gemini, Meta AI, Apple Intelligence and Doubao — and comparing
what came back. The AI-training opt-out tokens that never crawl are read from robots.txt instead.
C67 / 100
1 of 6 crawlers can read this page.
More readable than 29% of the 47,821 sites measured so far.
Structured data: WebPage.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|
| ClaudeBot (Claude) | 200 |
can read it |
allowed-by-star |
| GPTBot (ChatGPT) | 402 |
error |
allowed-by-star |
| OAI-SearchBot (ChatGPT Search) | 402 |
error |
allowed-by-star |
| PerplexityBot (Perplexity) | 402 |
error |
allowed-by-star |
| Google-Extended (Gemini, AI Overviews) a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own | — |
not opted out |
allowed-by-star |
| Meta-ExternalAgent (Meta AI) | 402 |
error |
allowed-by-star |
| Amazonbot (Alexa, Rufus) | 402 |
error |
blocked |
AWS CloudFront answers for this domain. Where a crawler above is
refused while robots.txt allows it, the rule is applied by that edge, not written by the site — see
how often each edge does this.
What to change, in order
- Let in the 4 crawlers your own robots.txt already allows+4 crawlers
GPTBot, OAI-SearchBot, PerplexityBot, Meta-ExternalAgent are turned away before reading the page (answered with an HTTP error), while robots.txt permits them — so this block is not written in your site. AWS CloudFront answers for this domain. AWS WAF Bot Control has an AI-crawler category that CloudFront enforces ahead of your origin. https://docs.aws.amazon.com/waf/latest/developerguide/waf-bot-control.html Fixing it takes this domain from 1 to 5 of 6 crawlers.
- Publish llms.txt
llms.txt is missing, so an assistant has to discover the site by following links. llms.txt is the emerging convention for telling an assistant which pages actually matter.
- 1 crawler is named and refused in robots.txt — a deliberate choice
Amazonbot is blocked by a rule that names it. Nothing to fix here: this page records what is true, not what should be. It is listed so the deliberate part of the block is not confused with the accidental part above.
Get told if this changes
One email only when a measured crawler flips on accountingtoday.com, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people29%
- Readable without JavaScript100%
- robots.txt lets the crawlers in86%
- Facts in JSON-LD67%
- Content reachable, not buried68%
- Publishes a map of itself70%
- Plain structure69%
Re-run this audit live →
Full AI-visibility report for accountingtoday.com →
Sites with a similar score
Browse the whole index →
Embed this score
Put the badge on accountingtoday.com — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/accountingtoday.com"><img src="https://shop.lumnika.com/ai-readiness/accountingtoday.com/badge.svg" alt="AI readability"></a>