Skip to content

AI Crawlability audit

The AI Crawlability audit checks whether AI bots (GPTBot, ClaudeBot, PerplexityBot, and others) can access and render your website — a prerequisite for being cited in AI responses.

Click AI Crawlability audit under Tools in the sidebar.

AI Crawlability audit page with Pages tab and AI Readiness Score
AI Crawlability audit page with Pages tab and AI Readiness Score

Configure which URLs to include in each audit run:

  1. Discover pages — opens a dialog to load URLs from your sitemap or run automatic discovery
  2. Manage pages — view and remove active audit pages in a separate dialog (keeps the main view compact)
  3. Manual add — in the discover dialog, enter a URL, optionally Check URL for HTTP 200, or confirm the URL is correct when your CDN blocks our server

Run an audit and review results:

An overall score (0–100) summarising how well your site is configured for AI crawlers. Category scores cover bot access, structured data, content, technical setup, renderability, and discoverability.

Each audited page shows its individual score and final URL after redirects.

Rule-based, prioritized fixes from failing and warning checks — not generated by AI.

llms.txt draft — generate a starter llms.txt from your brand settings and configured audit pages. The draft only lists pages in your audit configuration; add more under Manage pages if needed, then regenerate. Copy or download and publish at /llms.txt on your domain.

Schema guidance — copyable JSON-LD snippets (Organization, WebPage, FAQPage) based on structured-data gaps from your latest audit.

When Vertex AI is configured, a short executive narrative summarizes audit results for stakeholders. Scores and recommendations remain deterministic — the summary does not invent new issues.

Previous audit runs so you can track improvements after fixing issues.

CategoryExamples
AI bot accessrobots.txt rules for GPTBot, ClaudeBot, PerplexityBot
RenderabilityJavaScript rendering, content visible without JS, semantic HTML landmarks
Structured dataSchema.org markup, JSON-LD
ContentTitle length (10–70), meta description (25–160), single H1, heading hierarchy, image alt text, visible text, author/date signals
TechnicalHTTP status, redirect chains, canonical tags
Discoverabilityllms.txt presence, sitemap, robots.txt