Indexability and crawlability
Whether crawlers can find and index the pages: robots rules, sitemaps, canonicals.
What it tells you
Part of AI readability. These checks ask whether crawlers can reach every page, fetch it, and tell which address is the real one.
Checks
Page is not a redirect
This URL is a redirect rather than a destination. Usually intended, and worth checking only if the URL was meant to serve content.
Read the documentation ›No redirect loop
The redirects loop, so the page never resolves.
Read the documentation ›No redirect chain
Reaching this page takes more than one redirect. It resolves, but each hop wastes crawl budget and adds latency.
Read the documentation ›No meta-refresh redirect
The page redirects with a meta refresh. Google recommends against it, and it is handled less predictably than an HTTP redirect.
Read the documentation ›Canonical URL is valid
The canonical points at a URL that errors, so indexing is aimed at a page that does not exist.
Read the documentation ›Canonical does not point to a redirect
The canonical points at a redirect rather than a final URL, which leaves the intended target ambiguous.
Read the documentation ›No recursive canonical
The canonical chain loops back on itself, so no target can be resolved.
Read the documentation ›No canonical chain
The canonical points to a page that itself points somewhere else. Chains are not followed reliably, so the wrong URL can end up indexed.
Read the documentation ›Page reachable
The URL returns 404 or 410. No content, metadata or metrics could be collected.
The origin refused our crawler (401, 403, 429 or similar). Whatever blocks us blocks the AI crawlers arriving the same way.
Read the documentation ›Sitemap present and valid
No sitemap.xml was found. Crawlers must then discover every page by following links, which reliably misses pages that are linked from few places.
sitemap.xml exists but is malformed, so a crawler cannot read it. The effect is the same as having no sitemap.
Read the documentation ›Page is indexable
The page tells search engines not to index it. It will not appear in results or in anything built on them.
Read the documentation ›Page fetched by the crawler
The page could not be fetched at all, DNS, TLS, timeout or a network error. A page that does not answer is not indexed.
Read the documentation ›Page rendered with JavaScript
Our crawler could not load this page with a headless browser, so the metrics come from a JavaScript-free fetch. This describes the audit run, not necessarily a fault on the page.
Read the documentation ›Unknown paths return a real 404
The origin answers HTTP 200 for paths that do not exist, instead of 404. Crawlers cannot tell a real page from a missing one, so crawl budget is spent on duplicates of the same shell and Search Console reports those URLs as soft 404 errors.
Read the documentation ›Seen in the app on: Technical Audit
See how the brand's site does on these checks.Related guides
- How the audit score is built
One score out of 100 for the brand's site: how well AI models can reach and read it, and how sound it is, with AI readability counting most.
- AI readability and site health
AI readability is whether AI models can reach and understand the brand's pages; site health is how fast, safe and sound they are.
Still stuck? Contact support ›