Methodology

How the AI Search Readiness Audit Works

The AI Readiness Score is a weighted composite across seven dimensions. Each dimension reflects a specific signal that AI-assisted search systems use to interpret, extract and cite a page. Same inputs produce the same score.

Methodology version 1.0 · Last reviewed 2026-07-12

Score composition

Weights below sum to 100.

Discoverability
13
How cleanly the URL, metadata and technical entry points let crawlers reach and understand the page.
Entity Clarity
16
How confidently AI can identify the business, brand and category behind the page.
Extractability
17
Whether a self-contained paragraph exists that AI can quote verbatim as an answer.
Trust & Credibility
15
Named ownership, credentials, reviews with source, guarantees and firsthand evidence.
Technical Readiness
13
Structured data, canonicals, mobile readiness, render simplicity and metadata completeness.
Commercial Clarity
14
Whether the deliverable, timeline, price band, audience and next step are named directly.
Question Coverage
12
Whether the questions real buyers ask are answered directly on the page in extractable form.

What we evaluate

Intent match, entity clarity, extractability, trust signals, technical readiness, question coverage, commercial clarity and structured-data opportunities — factors the audit evaluates against publicly documented schema.org and answer-engine guidance.

What we don't do

We do not promise AI rankings, guarantee placements or rely on undisclosed 'hacks.' The audit surfaces what is unclear, missing or unstructured and provides specific edits. No platform can guarantee inclusion or recommendation.

How the label works

Above 82 is Strong Foundation. 68–81 is Needs Improvement. 54–67 is High Opportunity. 40–53 is Limited Clarity. Below 40 is Competitive Risk. Labels are calibrated to what an operator can act on this week.

Reproducibility

Every audit is deterministic. Given the same URL and inputs, the report is identical. This matters for teams comparing before/after and agencies benchmarking client work.

Grounded, not speculative

Our scoring maps to observable signals in the page and the structured metadata around it — not to guesses about model internals. Rewrites, FAQ suggestions and JSON-LD recommendations follow published schema.org guidance and answer-engine documentation.

When a signal cannot be measured (e.g. private analytics), we say so and describe the recommended pattern instead.