Crawler access
HTTP availability, redirects, robots.txt, AI crawler rules, and page directives.
AI agent readiness & technical GEO audit
Audit crawler access, technical discoverability, content clarity, structured data, and other signals that help AI search systems find and interpret your public pages.
A deterministic test of whether known AI and search crawler user agents can access the submitted URL.
Reads robots.txt, page robots metadata, response headers, sitemap declarations, and path-specific rules.
A crawler cannot retrieve content that the site intentionally or accidentally blocks.
Allowed means the tested rules permit retrieval; blocked or partial points to the exact matching evidence. It does not guarantee indexing or citation.
Use it after changing robots.txt to verify that OAI-SearchBot is allowed while private paths remain blocked.
Submit a public domain or page URL to inspect crawler access controls.
What we check
HTTP availability, redirects, robots.txt, AI crawler rules, and page directives.
Sitemaps, canonicals, indexability, internal links, and bounded URL samples.
Raw main content, headings, direct answers, meaningful links, and semantic structure.
Valid JSON-LD, entity properties, value formats, and visible-content consistency.
Brand names, descriptions, entity home, identifiers, and essential trust pages.
How it works
Technical readiness can improve eligibility for crawling and interpretation. It does not guarantee that any AI service will mention, recommend, rank, or cite your website.
Read the scoring methodologyCommon questions
No. Scores summarize observed technical or editorial signals only.
No. It performs read-only public requests and gives reviewable guidance.
No. It is experimental and optional; core crawlability, content, and structured data come first.
No. Do not submit authenticated or sensitive URLs. Private and reserved network targets are blocked.