AI Search Ready
All systems operational Free · no sign-up
How it works

An honest read of how AI sees your site.

A free, plain-English audit of the technical and structural signals AI assistants use to reach, read, and decide whether to cite your content. We don't ask ChatGPT what it thinks of you — we check whether the foundations are in place so it can cite you when it answers.

The pipeline

Five phases, one report.

Every audit moves through the same five phases. You'll see them as they happen in the progress view. Most audits finish in two to five minutes.

01 · Discover Sitemap & URL clustering We fetch your sitemap, group URLs by template, and stratify-sample up to 50 pages so the audit reflects your whole site.
02 · Permissions robots.txt & llms.txt We read robots.txt against 11 named AI crawlers. Sitemap presence. llms.txt presence. Indexability and canonicals.
03 · CDN Bot policy fingerprint We fetch the homepage as each AI bot UA, compare to Chrome, and fingerprint Cloudflare, Akamai, AWS WAF, Fastly, Vercel, Netlify.
04 · Content Raw + rendered DOM We fetch each sampled page twice — plain HTTP and headless Chrome — and diff them to see how much depends on JavaScript.
05 · Score Translate to plain English We score against three rollups, rank by impact, and write the findings in language a non-technical reader can forward.
The framework

Three questions every audit answers.

We boil everything we check into three rollups. Each one becomes a 0–100 score with the specific findings that moved it. The questions are the same every time. The answers, mostly, are not.

01

Can AI find your site?

We check robots.txt rules against the 11 named AI crawlers — GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended, and the rest. We fetch your sitemap, look for an llms.txt, and — the part most audits miss — fingerprint whether your CDN is quietly turning AI bots away while robots.txt waves them in.

The CDN-vs-robots gap is the most damaging issue we look for. We fetch the homepage with each AI bot user-agent, compare against a baseline Chrome request, and flag mismatches. We won't pretend a 503 means "all bots allowed."

  • robots.txt per bot
  • Sitemap discovery
  • llms.txt presence
  • CDN baseline fetch
  • Bot-vs-Chrome delta
  • CDN vendor fingerprint
  • Indexability (noindex)
  • hreflang alternates
02

Can AI understand what's there?

Headings, summaries, question-style sections, structured data, and a raw-vs-rendered diff. We fetch each sampled page twice — once as a plain HTTP request, once as a headless browser — and tell you how much of your content is actually visible before JavaScript runs.

This is the section that matters most for sites built on heavy client-side frameworks. AI bots don't always run JavaScript. If half your content depends on it, half your content is invisible.

  • Single H1 per page
  • Summary-style intro
  • Question-style headings
  • List density
  • Paragraph length
  • JSON-LD types
  • Open Graph & Twitter Card
  • Raw vs rendered diff
03

Will AI cite you as a source?

Trust signals AI assistants lean on when choosing whom to quote: verifiable author markup with sameAs links, freshness signals, outbound vs internal link ratio, HTTPS posture, image alt coverage, and the editorial shape of your most-quotable paragraph.

A site can be technically open to every AI crawler and still go uncited, because nothing on the page anchors a confident citation. This is where most failures cluster.

  • HTTPS + HSTS
  • Mixed-content check
  • Author + sameAs markup
  • Sitemap lastmod
  • Visible "updated on"
  • Outbound vs internal ratio
  • Descriptive anchor text
  • Image alt coverage
What we check

The full audit, in detail.

Every audit runs dozens of distinct checks, grouped into the categories below. Reports link each finding back to its source document — official AI-provider docs, web standards, or established practice.

AI crawler access robots.txt rules per named AI crawler. Sitemap and llms.txt presence. Indexability and canonical declarations.
CDN bot blocking Fetches the homepage with each AI bot UA and compares against a baseline Chrome fetch. Fingerprints Cloudflare, AWS WAF, Akamai, Fastly, Sucuri, Vercel, Netlify. Flags mismatches between robots.txt policy and CDN behaviour.
Content structure Single H1 per page. Summary-style intros. Question-style headings. List density. Paragraph length. The cues AI uses to identify quotable answers.
Structured data JSON-LD types — Article, FAQPage, Product, Organization. Open Graph and Twitter Card. Author markup with verifiable sameAs.
Extractability Trafilatura main-content extraction. Raw vs rendered HTML diff to estimate JavaScript dependency. Pages that look fine to a human but appear empty to a bot get flagged.
Canonical & indexation Canonical tags. noindex / nofollow directives. Hreflang alternates and consistency.
Freshness signals Sitemap lastmod, schema dateModified, visible "updated on" dates — and whether they agree.
Trust signals HTTPS. HSTS. Mixed-content detection. Outbound vs internal link ratio on the homepage.
Internal linking Anchor text quality — descriptive phrases vs generic ("click here", "read more") on internal links.
Media accessibility Alt-text coverage on images. Descriptive filenames. The same signals AI uses to caption and reason about visuals.
Privacy

What we keep, and don't.

The audit is anonymous. We don't collect your email, sign you up for anything, or share audit data with third parties. The privacy policy has the full text.

Anonymous by default No email, no sign-up. Each report lives at a UUID-based URL anyone with the link can view. No public directory of audits.
Rate limiting We record the IP that requested the audit so we can enforce three audits per IP per day. That's the only personal data we hold against an audit.
Sampled content We store the rendered HTML of pages we sampled so the report can stay reproducible. Plain web content, nothing private.

Run it on your site.