AI Readiness Review · v2026.10

AI ReadinessEverything we check when we ask: can an AI engine find this site, understand it, trust it, and quote it?

AI readiness is whether an AI answer engine can find a site, understand it, trust it, and quote it accurately. This review is the full checklist we run: 59 weighted checks across crawl access, AI crawler policy, machine-readable surfaces, structured data, entity and About-page depth, content extractability, trust, off-site corroboration and measurement — plus a dedicated audit of the About page, the check most audits still miss. Score your own site below; nothing leaves your browser.

  • 59 checks
  • 9 weighted categories
  • +10 bonus track
  • Updated

01 · The principle

We do not recommend building a separate website for LLMs.

No shadow markdown clones, no hidden text “for the AI”, no page no human would want to read. Those create an easily gameable surface, and no major AI vendor has asked for them. Google, OpenAI and Anthropic have consistently pointed at the same thing: readable, well-structured, trustworthy pages that already serve humans.

AI visibility is not a separate internet. Google AI Overviews, AI Mode, ChatGPT Search, Perplexity, Copilot and Claude read the same web your customers read. What changes is the mechanics of being read: which crawlers you admit, whether your facts are typed rather than implied, whether a page can be lifted cleanly into an answer, and whether the entity behind the page is legible and corroborated.

The strongest AI visibility asset is usually a page that would pass an editor’s review in 2015: comprehensive, specific, well organized, current, and clearly owned by a named, credible entity.

Gen AI impressions · Google Search Console

On one enterprise brand’s site, the About page drew 5× the AI impressions of the homepage.

About page5×Homepage1×Landing pageslower
Why: AI answers are largely entity answers. The About page is the densest concentration of entity facts on a domain — founding date, leadership, history, scale — stated in prose a human wrote, with dates and names.

02 · How it is scored

59 checks, 9 weighted categories, one index out of 100.

Tick what already passes. Your score updates live, and every open item keeps the smallest correct fix attached so the output is a work queue rather than a verdict.

Verdict bands

90–100
AI-ready leader. Defensible. Optimize for citation quality and coverage.
75–89
Ready. Strong substrate; remaining gaps are usually content depth or entity clarity.
55–74
Mostly ready. Machines can read you, but they cannot confidently attribute facts to you.
35–54
At risk. You are being crawled without being understood. Citation share will lag competitors with worse content.
0–34
Not ready. Fix foundations before spending anything on content or links.

Priority labels

P0
Blocks AI visibility outright
P1
High-leverage, do this quarter
P2
Polish and defense
P3
Optional / emerging

The score is an index, not a grade. It tells you where the next hour of work buys the most visibility — not how good your marketing is.

03 · The checklist

Tick what already passes.

0/100 Not ready

Your answers stay in this browser only. Nothing is uploaded. When you are done, copy the fix list or download the JSON — both carry the open items grouped by priority with the smallest correct fix for each.

Foundations

15 points · 8 checks

0 of 8 passing0.0 / 15 pts

The substrate every model and crawler depends on. Nothing downstream survives a failure here.

F1P01.9 pts

Page returns 200 over HTTPS at a stable final URL

Check
Status code, redirect chain length, final URL, TLS validity and expiry.
Pass
Single 200, no more than one permanent redirect, valid cert, no mixed content on the primary template.
Why
A redirect chain is a lossy path. Each hop is a chance for a crawler to record a different URL than the one you cite.
Fix
Collapse to one canonical host (apex or www, pick one), 301 everything else, renew certs on a schedule.
F2P01.9 pts

Stable URLs

Check
Sampled URL set against the last 90 days of 404s, redirect maps, and CMS slug changes.
Pass
Previously published URLs still resolve, or permanently redirect to a genuine equivalent.
Why
URLs are public contracts. Breaking them invalidates citations, bookmarks, and agent caches — an AI answer that cites a dead URL is an answer you lost.
Fix
Never recycle a slug; add redirects at publish time, not at audit time.
F3P01.9 pts

Indexable core pages

Check
noindex directives, meta robots, X-Robots-Tag, accidental Disallow overlap, JS-only rendering of primary content.
Pass
Homepage, About, services/products, and primary category pages are indexable and contain their main content in the initial HTML.
Why
If the text arrives only after client-side hydration, some crawlers see an empty shell.
Fix
Server-render or pre-render core templates; keep primary copy in HTML.
F4P11.9 pts

Semantic document structure

Check
lang attribute, exactly one H1, a main element, heading order, landmark elements.
Pass
Valid lang, one H1 matching page intent, no skipped heading levels in the body, main present.
Why
Structure is how an extraction pipeline decides what is a section, a summary, or a footnote.
Fix
Template-level corrections, not per-page patching.
F5P11.9 pts

Title and meta description quality

Check
Uniqueness across the sampled set, length, presence of the entity name, absence of boilerplate duplication.
Pass
Unique titles, entity + topic + qualifier, 50–60 characters; descriptions 140–160 characters that state the value plainly.
Why
Titles and descriptions are the cheapest summary an engine can quote.
Fix
Generate from a template with real per-page variables.
F6P11.9 pts

Canonical discipline

Check
Self-referencing canonicals, canonical vs. hreflang vs. sitemap agreement, parameter handling.
Pass
Every indexable page self-canonicalizes; no canonical points to a redirect or a 404; paginated series handled deliberately.
Why
Conflicting canonicals split the entity’s evidence across duplicate URLs.
Fix
Fix at the template level; audit faceted and parameterized URLs separately.
F7P11.9 pts

Crawl performance and Core Web Vitals

Check
TTFB, LCP, CLS, INP on mobile templates, render-blocking assets.
Pass
LCP under 2.5s, CLS under 0.1, INP under 200ms on the primary templates.
Why
Primarily a human-experience and crawl-budget tax, and AI crawlers are not generous with slow origins.
Fix
Image compression, font strategy, defer non-critical JS.
F8P21.9 pts

Sitemap accuracy

Check
Sitemap presence, freshness of lastmod, inclusion of only 200-status canonical URLs, index structure at scale.
Pass
Valid XML, only canonical 200s, lastmod reflects real content change.
Why
A sitemap full of redirects teaches a crawler to trust you less.
Fix
Generate from published content; exclude noindex and redirected URLs.

Crawl & AI policy

10 points · 6 checks

0 of 6 passing0.0 / 10 pts

Who is allowed in, and what you are telling them about usage.

R1P01.7 pts

robots.txt exists and is syntactically valid

Check
Fetchability, no wildcard catastrophe, no accidental site-wide block, correct directive syntax.
Pass
Returns 200 text/plain, explicit User-agent groups, no Disallow: / outside intentional staging.
Why
A broken robots file is the most common cause of “we get no AI traffic”.
Fix
One file, reviewed in version control, not edited live from memory.
R2P11.7 pts

Named AI crawler policy is explicit

Check
User-agent entries for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, CCBot, Bytespider, Meta-ExternalAgent, Amazonbot — and whether the resulting policy matches business intent.
Pass
A deliberate allow/deny per agent, documented, with the business rationale attached.
Why
Omission is not neutrality. Different crawlers treat silence differently, and you cannot answer “are we visible to ChatGPT” while leaving it ambiguous.
Fix
Write the policy down, put it in robots.txt, review when vendors change user agents.
Note
Search/answer crawlers and training crawlers are different decisions. Blocking training is legitimate; blocking answer engines is usually self-harm.
R3P11.7 pts

Sitemaps referenced from robots.txt

Check
Sitemap: directive, absolute URLs, index coverage.
Pass
Declared, absolute, resolves to a valid sitemap.
Fix
One line.
R4P2emerging convention1.7 pts

Content-Signal directives

Check
Presence of Content-Signal: declarations for search, ingest, and train.
Pass
Present and intentional where the organization has a position on AI training.
Why
It makes your usage position machine-readable instead of implied.
Note
Emerging convention (IETF AI Preferences / IAB proposal), not a ratified standard. Treat as a defensive nice-to-have.
R5P21.7 pts

No accidental blocking of answer engines via WAF or CDN

Check
403/418/202 responses to AI user agents, bot-management rules, geo-blocking, JS challenges.
Pass
Target crawlers receive 200 with real content.
Why
Enterprise WAF defaults routinely block AI crawlers, and the site owner never sees an error because humans are unaffected.
Fix
Allowlist verified crawler ranges, or exempt the content paths.
R6P21.7 pts

Crawl-budget hygiene

Check
Parameter sprawl, infinite calendar/filter spaces, thin duplicate pages, orphan pages.
Pass
No unbounded crawl traps; important pages within three clicks of the homepage.
Fix
Canonicalize, noindex thin variants, link your money pages from navigation.

Machine-readable surfaces

15 points · 6 checks

0 of 6 passing0.0 / 15 pts

Conventions that let an engine pull your content as source instead of scraping your layout.

M1P1emerging convention2.5 pts

/llms.txt

Check
Presence at the root, valid markdown, curated (not dumped), links resolving, a one-line description of the entity at the top.
Pass
A short, human-maintained index of the pages that matter, each with a one-line summary and a live URL; discoverable via <link rel="alternate" type="text/markdown">.
Why
A curated map instead of a crawl guess. llms.txt v2 makes it discoverable by link relation rather than path guessing — the real improvement.
Fix
Generate from your top 20–50 URLs; keep it current; never ship a 404 or a wall of links with no descriptions.
Note
A convention, not a standard.
M2P2emerging convention2.5 pts

/llms-full.txt

Check
Presence, size, whether it duplicates pages or genuinely concatenates key content.
Pass
For small sites and documentation sets, a single concatenated file of the core corpus.
Why
One fetch beats twenty. Costly and low-value for large sites — we often recommend against it there.
Fix
Build from the same source of truth as M1.
M3P22.5 pts

Per-page markdown source endpoints

Check
page.md, a .md suffix on canonical URLs, or Accept: text/markdown content negotiation.
Pass
At least the key evergreen pages expose clean markdown.
Why
Agents pull source instead of parsing HTML; you control the exact text they see.
Fix
Add a build step that emits markdown alongside HTML.
M4P22.5 pts

Feeds and typed endpoints

Check
RSS/Atom for content sites, JSON endpoints for structured data (products, locations, people).
Pass
Feed exists, validates, includes full or near-full content, updates on publish.
Fix
Most CMSs have this; turn it on and keep it un-truncated.
M5P22.5 pts

HTTP Link header discovery

Check
Link: headers advertising llms.txt, sitemap, api-catalog, RSS.
Pass
Present on HTML responses with correct rel values.
Why
An agent that never parses your HTML can still find everything.
Note
Not controllable on some hosted platforms (notably Shopify Standard). Use HTML <link> tags in <head> instead and record the platform limitation.
M6P22.5 pts

HTML <link> / <a> machine discovery

Check
rel="alternate", rel="sitemap", rel="author", rel="mcp" where applicable.
Pass
Machine resources are linked from the document, not just documented in a blog post.
Fix
Add to the head template once.

Structured data & entity markup

15 points · 6 checks

0 of 6 passing0.0 / 15 pts

Typed facts. This is where “the model guessed” becomes “the model knew”.

S1P12.5 pts

Valid JSON-LD present

Check
application/ld+json blocks, parse validity, schema.org type correctness, absence of conflicting duplicates.
Pass
Parses cleanly, no placeholder values, one coherent graph per page.
Fix
Validate in CI, not by hand.
S2P12.5 pts

Organization markup on the site root

Check
Organization or Corporation with name, url, logo, description, foundingDate, founder, sameAs, address, contactPoint.
Pass
Every field true and current; sameAs points to real, live profiles.
Why
The machine-readable version of your About page, and the anchor for entity resolution.
Fix
One canonical block on the homepage and About page.
S3P22.5 pts

Person markup for leadership and authors

Check
Person entities with name, jobTitle, worksFor, sameAs, and links to author archive pages.
Pass
Real bios exist and are linked; markup matches the visible text.
Why
E-E-A-T and AI answers both reward named, findable expertise.
Fix
Author pages with real bios, then markup.
S4P22.5 pts

Page-type markup matches the page

Check
AboutPage, Article/BlogPosting, Product, Service, FAQPage, BreadcrumbList, WebSite with SearchAction.
Pass
The type describes what the page actually is; no FAQPage markup on a page with no visible FAQ.
Why
Mismatch is a trust signal in the wrong direction.
Fix
Map templates to types, apply at the template.
S5P22.5 pts

Dates in markup

Check
datePublished, dateModified, and visible dates agreeing.
Pass
Dates are real, updated when content materially changes, never auto-bumped for freshness theater.
Why
Freshness that is faked is detectable and costs credibility.
Fix
Wire to the CMS edit timestamp, and actually edit.
S6P22.5 pts

Entity consistency across the site

Check
Legal name, trading name, address, phone, founding year, and leadership names identical across About, Contact, footer, schema, and social profiles.
Pass
One version of the truth everywhere.
Why
Inconsistent entity facts are the main cause of a model describing you incorrectly or not at all.
Fix
A single canonical brand-facts block in the CMS, reused.

Entity & About page

15 points · 11 checks

0 of 11 passing0.0 / 15 pts

The section the rest of the industry under-weights. If the About page is your highest-impression page in AI answers, it deserves a real audit, not a “does it exist” checkbox. We score it on depth, specificity, structure, and corroboration.

E1P01.4 pts

An About page exists at a stable, linked URL

Check
/about (or /about-us, /company) returns 200, is reachable from the primary navigation and footer, and is not buried in a dropdown three levels deep.
Pass
One canonical About URL, linked sitewide, indexed, in the sitemap.
Why
It is the page an engine reaches for when asked who you are. Make it findable.
Fix
Create it, link it, canonicalize it, then stop renaming it.
E2P11.4 pts

Company history with real chronology

Check
Founding year and story, key milestones with dates, origin of the name or product, evolutions, pivots, acquisitions, offices.
Pass
A dated timeline with at least 5–8 substantive milestones, each with a year and a specific event.
Why
Exactly the fact pattern a model needs to answer “how long has this company existed”, “what do they do now”, “how did they get here”. Undated claims are unusable.
Fix
Interview the founders, pull the incorporation date, write the timeline. The highest-leverage content task in the entire review.
E3P11.4 pts

Specific, verifiable facts rather than adjectives

Check
Counts of employees, customers, locations, years in operation, product lines, certifications, awards, named markets.
Pass
Numbers and names, each either public or explicitly labeled as company-reported.
Why
“Leading provider” is unquotable. “Founded in 2009, 140 employees, operations in 6 countries” is quotable.
Fix
Replace every superlative with a fact. Where a fact is unverified, label it.
E4P11.4 pts

Named leadership with real bios

Check
Founders and executives with full names, roles, tenure, prior background, and links to LinkedIn or personal sites.
Pass
Each leader has a paragraph, not a job title; bios are consistent with Person markup and press mentions.
Why
People are the fastest entity-resolution shortcut a model has. Faceless companies get vague answers.
Fix
Write real bios; add Person schema; link author pages.
E5P11.4 pts

Clear statement of what the company does, in plain language

Check
A short, quotable definition near the top — what you sell, to whom, and the outcome.
Pass
One to three sentences that could be lifted verbatim into an answer without losing meaning. No jargon that needs the rest of the page to decode.
Why
The single most-cited sentence on most About pages.
Fix
Write it first, before the history.
E6P21.4 pts

Who you serve and how you are different

Check
Named customer segments, industries, geographies, and a defensible articulation of difference.
Pass
Specific segments and a differentiator that is a claim about method or scope, not “quality” or “passion”.
Fix
One section each.
E7P21.4 pts

Credentials, compliance and proof

Check
Certifications, registrations, licenses, memberships, awards (with awarding body and year), security/compliance posture.
Pass
Verifiable, dated, linked where possible.
Why
Trust facts that models weigh and buyers check.
Fix
List them plainly; do not bury them in a badge carousel.
E8P21.4 pts

Structure that survives extraction

Check
Descriptive H2/H3s, short paragraphs, a scannable timeline, a leadership grid, an at-a-glance fact block.
Pass
An engine could reconstruct the company summary from headings alone.
Why
Heading-based chunking is how modern extraction works.
Fix
Add an “At a glance” block — founded, headquarters, leadership, employees, markets, products.
E9P21.4 pts

Media and human quality

Check
Real photography, office and team images, a designed layout, readable typography, mobile behavior.
Pass
A page a human would actually read and trust, not a wall of text.
Why
The page serves humans first and is legible to machines as a side effect. Pages built awkwardly “for AI” fail both tests.
Fix
Invest in design here. This page is a sales asset too.
E10P21.4 pts

Marked up and corroborated

Check
AboutPage + Organization JSON-LD on the page, foundingDate, founder, sameAs, and cross-checks against Wikipedia/Wikidata, LinkedIn, Crunchbase, press, and industry directories.
Pass
Markup matches visible content; at least three independent third-party sources state the same founding year, leadership, and description.
Why
Corroboration turns a self-description into an established entity.
Fix
Fix inconsistencies off-site first, then markup.
E11P31.4 pts

Kept current

Check
Last meaningful edit date, whether leadership and headcount are stale, whether recent milestones are missing.
Pass
Reviewed at least twice a year; updated within a month of a material change.
Why
A 2019 About page actively teaches models that you are smaller and older than you are.
Fix
Put it on the content calendar as a recurring task, not a one-off project.

About page red flags we mark down

  • A vision statement and three stock photos, no dates, no names.
  • “Our team” with no names, or names with no roles.
  • An About page that is really a sales landing page with a paragraph of history.
  • Founding year that disagrees with LinkedIn, Crunchbase, or the footer.
  • Leadership that changed two years ago and is still listed.
  • A separate hidden “about page for LLMs” — the anti-pattern, not the fix.

Minimum viable About page

  1. One-paragraph definition. What we do, for whom, since when.
  2. At-a-glance block. Founded, HQ, employees, markets, products, leadership.
  3. Founding story. 300–600 words with real specifics.
  4. Timeline. 6–10 dated milestones.
  5. Leadership. 4–6 bios at 100–200 words each.
  6. What we do / who we serve. Two short sections.
  7. Credentials and awards. With awarding body and year.
  8. Contact and locations. Consistent with the footer and Contact page.
  9. AboutPage + Organization + Person JSON-LD. Matching the visible text.

Length is not the goal; specificity is. A tight 1,200-word page with dates and names beats a 4,000-word page of adjectives.

Content extractability

12 points · 8 checks

0 of 8 passing0.0 / 12 pts

Being readable is not the same as being quotable. These are the properties that make a passage lift cleanly into an answer.

C1P11.5 pts

Answer-first structure

Check
Does each key section lead with a direct answer before elaboration?
Pass
The first 40–60 words after a heading resolve the question the heading implies.
Why
Extraction favors self-contained, front-loaded passages.
Fix
Rewrite intros as answers; move context below.
C2P11.5 pts

Self-contained passages

Check
Whether paragraphs make sense without the surrounding page (pronouns resolved, entity named, units given).
Pass
A passage can be quoted alone and still be correct.
Fix
Name the company and the subject in the first sentence of key sections.
C3P11.5 pts

Specificity and statistics

Check
Numbers, dates, named examples, methodology, sources.
Pass
Claims carry a number, a date, or a citation; statistics name their source.
Why
Specificity is what makes a page worth citing over a competitor’s.
Fix
Add one concrete data point per major section.
C4P21.5 pts

Definitions and terminology

Check
Does the page define the terms it uses, in the way the market searches them?
Pass
A definitional sentence for each key concept, in plain language.
Why
Definitional passages get lifted into “what is X” answers constantly.
Fix
Add a short glossary or inline definitions.
C5P21.5 pts

Freshness with real updates

Check
Visible dates, dateModified, and whether the content actually changed.
Pass
Updated on a cadence tied to the subject’s rate of change, with substantive edits.
Fix
A content refresh calendar per cluster.
C6P21.5 pts

Authorship and expertise

Check
Bylines, author bios, credentials, reviewer attribution on sensitive topics.
Pass
A named human with a real bio and relevant background.
Why
E-E-A-T and AI answer quality both lean on provenance.
Fix
Real author pages, linked from every article.
C7P21.5 pts

Internal linking to entity pages

Check
Whether commercial and editorial pages link to About, leadership, methodology, and contact.
Pass
The entity pages are in the link graph, not orphaned.
Why
Linking is how a crawler learns which pages define the brand.
Fix
Contextual links from key pages plus sitewide footer.
C8P31.5 pts

Multimodal clarity

Check
Image alt text, descriptive filenames, captions, transcript availability, table structure.
Pass
Alt text describes content; tables have headers; video has transcripts.
Fix
Template-level alt enforcement; transcripts on media pages.

Trust & security

8 points · 6 checks

0 of 6 passing0.0 / 8 pts

Boring, cheap, and used by both crawlers and procurement teams.

T1P11.3 pts

HTTPS everywhere with HSTS

Pass
No mixed content; Strict-Transport-Security with a sensible max-age.
T2P21.3 pts

Content-Security-Policy present

Pass
A real policy, not unsafe-inline everywhere.
T3P21.3 pts

X-Content-Type-Options: nosniff

Pass
Header present on all responses.
T4P21.3 pts

Referrer-Policy and Permissions-Policy

Pass
Both headers present with deliberate values.
T5P31.3 pts

/.well-known/security.txt

Pass
Contact and expiry present.
Why
Signals a maintained security posture.
T6P3emerging convention1.3 pts

TDM reservation

Pass
A deliberate position on text and data mining, expressed in a tdm-reservation header, meta tag, or /.well-known/tdmrep.json.
Note
Its force is legal, not technical — decide with counsel, not with the SEO.

Off-site corroboration

5 points · 4 checks

0 of 4 passing0.0 / 5 pts

Models do not only read your site. They read what others say about you.

O1P21.3 pts

Full-depth brand mention inventory

Check
Up to 100 organic results for the brand across pages 1–10 of the SERP, excluding your own domain, classified by control: editable (official/claimable profiles), influenceable (community, UGC, reviews), independent (editorial, press, directories).
Why
You cannot fix a fact you have not inventoried, and page one hides most of the story.
O2P21.3 pts

Profile consistency

Check
LinkedIn, Crunchbase, Wikipedia/Wikidata (if eligible), industry directories, review platforms — founding year, HQ, leadership, description.
Pass
Identical facts across all claimable profiles.
O3P21.3 pts

Entity anchors

Check
At least three independent sources that describe the company in comparable terms.
Why
Corroboration is what makes an entity resolvable rather than merely present.
O4P31.3 pts

Earned coverage with quotable facts

Check
Press, podcasts, and interviews that contain specific, citable claims about the company.

Measurement

5 points · 4 checks

0 of 4 passing0.0 / 5 pts

If you cannot see it, you cannot defend the budget.

X1P11.3 pts

Google Search Console Gen AI visibility

Check
The Gen AI / AI Mode reporting, top cited pages and queries, and whether impressions concentrate on unexpected pages (About pages, comparison pages, docs).
Why
The only first-party view of AI-surface impressions at scale. The About-page outlier pattern was found exactly this way.
X2P11.3 pts

Prompt-level citation probes

Check
A fixed prompt set run across ChatGPT, Perplexity, Grok, Claude and Google AI, recording whether the brand is mentioned, cited, and described accurately.
Pass
A repeatable panel with a stable prompt list, tiered by intent — direct competitor comparisons, category authority, use case, and category awareness — run on a schedule.
X3P21.3 pts

Competitor citation share

Check
The same prompts, scored for which competitors appear and which sources they cite.
X4P21.3 pts

Answer accuracy audit

Check
Whether the model’s description of the company is correct — size, founding year, products, leadership.
Why
Being cited incorrectly is worse than being omitted. It also tells you exactly which entity fact is broken.

Advanced discovery

bonus · up to +10 · 11 surfaces · never a failure

0 of 11 shipped+0 pts

Emerging, mostly optional, and worth shipping only where the effort is small and the surface is genuinely public. Draft or emerging conventions — not requirements. Scored as upside, never as a failure.

MCP server card

/.well-known/mcp/server-card.json, plus a public, read-only MCP endpoint where your data is worth querying.

API catalog

/.well-known/api-catalog

A2A agent card

/.well-known/agent-card.json, if you expose delegated agent behavior.

Agent Skills discovery

A well-known URI listing short, scoped instructions. Draft, cheap.

NLWeb

An /ask-style conversational endpoint advertised via rel="nlweb".

WebMCP

In-page tools via document.modelContext. Browser-native, experimental.

Agentic Resource Discovery

/.well-known/ai-catalog.json

DNS-AID

SVCB/HTTPS records under _agents. with DNSSEC.

Schemamap

/schemamap.xml indexing one JSON-LD endpoint per resource.

Universal Commerce Protocol

/.well-known/ucp for stores that want agent-assisted checkout.

OKF bundle

The corpus as typed markdown for one-fetch ingestion.

Your AI Readiness score

0 / 100

Not ready — Fix foundations before spending anything on content or links.
Index score: 0/100. Open P0 blockers: F1, F2, F3, R1, E1.

The score is an index, not a grade: it tells you where the next hour of work buys the most visibility.

04 · Platform-specific gotchas

Where the platform quietly undoes the work.

Shopify

  • Store pages are store-level records, not theme assets — a theme switch or admin cleanup can silently delete agent pages. Verify every agent-readable URL returns 200 after any theme change.
  • Dot-prefixed /.well-known/* paths generally 404 regardless of redirect configuration; use /pages/<handle> surfaces instead.
  • Custom HTTP headers are not controllable on Standard; use HTML <link> tags.
  • Edge cache can serve stale content for minutes to hours after a change — verify without cache-busting before declaring a page live.

WordPress

  • SEO plugin canonical/sitemap conflicts.
  • noindex left on from staging.
  • Page builders injecting content outside the main content element.
  • WAF rules returning 403 to non-browser user agents.

Webflow & hosted builders

  • Limited header control — lean on HTML discovery links and structured data.
  • Confirm custom code survives template updates.

05 · How we run the review

Eight steps, evidence at every one.

  1. Normalize. The target to its canonical origin and page path.
  2. Probe. The live site: status, headers, TLS, semantics, JSON-LD, robots, sitemap, llms.txt, llms-full.txt, feeds, well-known endpoints.
  3. Pull the live reference checklist. Agent-readiness, plus SEO, well-known and security categories — so the review reflects current guidance, not remembered rules.
  4. Read the machine-readable files. Rather than judging their existence. An llms.txt full of dead links is worse than none.
  5. Crawl. For stability, redirects, canonicals, orphans, and duplicate templates.
  6. Audit the entity layer. About page against E1–E11, structured data against S1–S6, off-site consistency against O1–O3.
  7. Probe the answer engines. With a fixed, tiered prompt set; record mention, citation, and accuracy.
  8. Score, rank by leverage, hand back a punch list. Smallest correct fix first, with owners and effort estimates.

Deliverables

  • Weighted score with blockers named.
  • Evidence per item: URL, header, or file content — not opinions.
  • A prioritized fix list split into this week, this quarter, defensive.
  • An About-page scorecard with the specific missing facts listed.
  • A before/after prompt panel so the next run has a baseline.

06 · The 30 / 60 / 90

Access and truth first. Depth last.

Days 0–30

Access and truth

  • Fix fetchability and canonicalization.
  • Write and publish the AI crawler policy.
  • Get sitemaps right.
  • Audit the About page against E1–E11; commission the missing history, dates, and bios.
  • Publish Organization markup.
  • Run the first prompt panel for a baseline.

Days 30–60

Structure and surfaces

  • Ship the About page rewrite with AboutPage + Person markup.
  • Publish a curated llms.txt.
  • Fix answer-first structure on the top 20 revenue pages.
  • Add author pages and bylines.
  • Standardize entity facts across all claimable profiles.

Days 60–90

Depth and defense

  • Expand content that earns citation: definitions, comparisons, methodology, original data.
  • Add per-page markdown where the build supports it.
  • Add security headers and security.txt.
  • Re-run the prompt panel; compare against baseline.
  • Add advanced discovery surfaces only where cheap and real.

Questions

AI readiness, answered.

What is AI readiness?

AI readiness is a measure of whether an AI answer engine can find a site, understand it, trust it, and quote it accurately. It covers five things: crawl access for AI user agents, typed facts in structured data, a legible entity behind the brand, passages that lift cleanly into an answer, and third-party corroboration. A site that ranks well on Google can still be AI-unready if its facts are implied rather than stated, or if its crawlers are blocked.

How is the AI Readiness score calculated?

Fifty-nine checks across nine weighted categories: Foundations (15), Crawl and AI policy (10), Machine-readable surfaces (15), Structured data and entity markup (15), Entity and About page (15), Content extractability (12), Trust and security (8), Off-site corroboration (5), and Measurement (5). Each check is worth an equal share of its category weight, so the total is out of 100. An optional advanced-discovery track adds up to 10 bonus points. The score is an index that shows where the next hour of work buys the most visibility, not a grade.

Why does the About page matter so much for AI visibility?

AI answers are largely entity answers. When a model needs to describe who a company is, how long it has operated, who runs it, and whether it is durable, the About page is the densest concentration of those facts on the domain — stated in prose with dates, names, and specifics. On one enterprise brand site the About page drew five times the Gen AI impressions of the homepage in Google Search Console. A tight 1,200-word About page with a dated timeline and named leadership beats a 4,000-word page of adjectives.

Should I build a separate website or hidden pages for LLMs?

No. AEO Engine does not recommend shadow markdown clones, hidden text written for AI, or LLM-only pages. No major AI vendor has asked for them, they fragment the entity, and they are trivially gameable. The strongest AI visibility asset is usually a page that would pass an editor review: comprehensive, specific, well-organized, current, and clearly owned by a named, credible entity. Machine-readable files like llms.txt are a convenience index, not a substitute for a readable page.

What is the fastest fix for a low AI Readiness score?

Fix access first. A single 200 at a stable HTTPS URL, an explicit AI crawler policy in robots.txt, and core pages that render their main content in the initial HTML clear the P0 blockers that cap every other gain. Then add Organization and AboutPage markup with true foundingDate, founder, and sameAs values, and rewrite the About page with a dated timeline and named leadership. Those three moves usually move a score further than any content expansion.

Does AI readiness replace SEO?

No. AI readiness sits on top of technical SEO. Crawlability, canonical discipline, titles, internal linking and Core Web Vitals are the same substrate. What changes is the emphasis: typed facts over implied ones, entity depth over keyword coverage, self-contained quotable passages over long narrative intros, and off-site corroboration over link volume alone. Sites with solid SEO fundamentals typically start this review with most of the Foundations category already passing.

How often should the review be re-run?

Re-run quarterly, and again after any platform migration, theme change, WAF or bot-management change, or major content restructure. AI vendors change crawler user agents and answer surfaces frequently, so a policy written a year ago may not match current behaviour. Keep the prompt-level citation panel on a fixed schedule so each run compares against a baseline rather than a memory.

The short version

Be findable. Be typed. Be specific. Be attributable. Be corroborated.

Then make the About page the best page on the site, because it is the page that answers “who are you” — to a buyer and to a model at the same time.

This document is a living checklist; the review is re-run as vendors change crawler behaviour and answer surfaces. 6 About-page red flags and 9 minimum-viable About requirements are scored inside category E.