Browse sections
What does this check look at?
Parsing robots.txt into user-agent groups, none of gptbot, claudebot, perplexitybot, oai-searchbot or google-extended is disallowed from /, AND the homepage served a crawler-shaped request with HTTP 200. An exact agent group takes precedence over the * group, the longest matching pattern wins and Allow wins ties, an empty Disallow value matches nothing, and * is treated as a wildcard. When the homepage refused the request, the verdict follows a second probe of the same URL made with a browser-shaped User-Agent: if that one returns 200 the refusal is aimed at identified crawlers, and the check fails under robots-ai-blocked; if it is refused as well, the refusal is about the scanning address rather than the site, and this check scores 2 of 6 as unverified.
What does a failure mean?
At least one AI crawler is disallowed from the site root, or the server refuses identified crawlers outright.
A site with no robots.txt at all passes this check only when the homepage was actually served, because with no file no crawler is disallowed by it. That is a deliberate reading: absence of robots.txt is a policy gap, not a block, and the gap is reported separately by robots-present. A refusal by the server is the stronger evidence and now overrides the file: robots.txt saying nothing is not permission if the request is rejected before it is read.
How do I fix it?
- Partial pass: Check in your CDN or WAF whether identified AI crawlers are admitted, and from which networks. This scan cannot settle that from here.
Why is it worth 6 points?
Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:
| Dimension | AI Crawler Access — 16% of the total score |
| Points for this check | 6 of 23 in this dimension |
| Worth at most | 4.2 of the 100 points |
Highest weight of the twelve. A page that is blocked or unreadable has no path to being cited, so it dominates the total.
Which dimension does this belong to?
AI Crawler Access — 16% of the total score, decided by 7 published rules.
If a crawler cannot read the page, nothing else on this list can matter. This is the only dimension where a failure makes the rest of the score moot.
The fix for this rule is walked through step by step in the allow ai crawlers guide.
What else is measured in this dimension?
- robots.txt is served — 2 points
- robots.txt declares a sitemap — 1 point
- Homepage returns HTTP 200 — 2 points
- Homepage is marked noindex — 2 points
- sitemap.xml is present and well-formed — 3 points
- robots.txt states a content policy — 1 point
How do I see my own result?
Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.
Run a free GEO audit on your own site →
The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.
Questions about this rule
What does this check look at?
Parsing robots.txt into user-agent groups, none of gptbot, claudebot, perplexitybot, oai-searchbot or google-extended is disallowed from /, AND the homepage served a crawler-shaped request with HTTP 200. An exact agent group takes precedence over the * group, the longest matching pattern wins and Allow wins ties, an empty Disallow value matches nothing, and * is treated as a wildcard. When the homepage refused the request, the verdict follows a second probe of the same URL made with a browser-shaped User-Agent: if that one returns 200 the refusal is aimed at identified crawlers, and the check fails under robots-ai-blocked; if it is refused as well, the refusal is about the scanning address rather than the site, and this check scores 2 of 6 as unverified.
What does failing it mean?
At least one AI crawler is disallowed from the site root, or the server refuses identified crawlers outright.
What else in this dimension should I check first?
sitemap.xml is present and well-formed: No sitemap, or a response that is not valid sitemap markup. robots.txt is served: No readable robots.txt at the domain root. Homepage returns HTTP 200: A non-200 homepage response. The access verdict itself is reported by robots-ai-allowed or robots-ai-blocked, which account for what the refusal was aimed at. robots.txt states a content policy: No Content-Signal directive in robots.txt.
Why does this dimension carry 16% of the score?
A page that is blocked or unreadable has no path to being cited, so it dominates the total.
Evidence and sources
GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024
This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.
Primary sources
- Generative Engine Optimization (KDD 2024) — the measured gains the citability weight follows
- What Generative Search Engines Like — what generative engines prefer in retrieved content
- What Gets Cited: Competitive GEO — which of two competing sources is cited first
- The rule set and its weights — every check, its weight and its pass condition