AI search readiness check

What readiness means here

This check covers four observable conditions: the page is reachable for AI search crawlers, its main text is present in the returned HTML, the organization and product facts are stated in visible content, and any structured data matches those facts. Readiness is not a citation, a ranking or a mention. Nothing here predicts whether an assistant will name your product.

The checklist the audit runs

Each item is measured from the fetched HTML, robots.txt, sitemap and one request per crawler user agent.

• robots.txt is reachable and its rules are read per crawler and per path.
• The entry page answers OAI-SearchBot, Claude-SearchBot and PerplexityBot with a readable status.
• The main content is present with scripts removed, so a non-JavaScript crawler still sees it.
• Organization or Product declarations parse and carry a name and URL that match the page.
• About, Contact and question-and-answer content exist as public pages or sections.
• Canonical and noindex declarations do not conflict with the pages you want public.
• Open Graph and language alternates describe the same URLs the canonical points to.

A robots.txt that states intent per crawler

A single wildcard rule is not a policy. Name the search crawlers you support and keep training crawlers separate, so a later change in one does not silently change the other.

# Search crawlers you want to support
User-agent: OAI-SearchBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

# Training crawlers, separate decision
User-agent: GPTBot
Disallow: /

One organization record, kept factual

Structured data should repeat what the page already says, not introduce claims. The audit checks that the declaration parses, uses a recognizable context and type, and matches visible information such as the name and URL.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your product name",
  "url": "https://your-domain.com/",
  "email": "support@your-domain.com"
}
</script>

llms.txt is optional, and we say so

An llms.txt file can summarize public pages for systems that choose to read it. No major search or assistant system requires it, and publishing one does not cause inclusion or citation. The audit reports whether the file exists and whether it is well formed, and marks it optional.

What public HTML cannot verify

A successful fetch does not prove a crawler indexed or cited the page. A robots.txt allowance does not prove a firewall lets the same request through, which is why the audit also sends a real request per crawler user agent and reports the status it received. Observed AI mentions and citations require a data source that SiteFix.app has not connected, so the report states that they are not measured.