Technical SEO
Covers crawlability, indexing signals, and technical accessibility — the foundation that determines whether search engines can reliably find and process the page.
AIO Mapper
Every AIO Mapper audit produces two separate scores — one for SEO visibility and one for AI readiness — showing how the page is structured for search and AI retrieval without presenting either diagnostic as a live ranking or citation result.
These are diagnostic scores, not rankings or traffic metrics. They highlight signal strength and clarity to help you prioritize improvements. Only checks applicable to the page's inferred purpose contribute to its score; supporting measurements remain visible without adding points or tasks. To compare diagnostic scores with measured citations, use the AIO tracker.
Methodology 2026-09-01-answer-forms-v3 · September 1, 2026
A score is completeness over the checks applicable to that page—not a percentile or market benchmark. Compare a page with itself only when the methodology, inferred purpose, and applicable-check set match. When that basis changes, AIO Mapper starts a new comparison baseline instead of presenting the movement as page improvement or decline.
The SEO Score measures how well your page is set up for search engines to crawl, index, and rank — covering technical health, content quality, readability, and metadata clarity.
The AI Readiness Score measures the applicable on-page and delivery signals associated with reliable retrieval and reuse. It does not observe or predict an AI system's decision to cite the page; tracked questions provide that separate, measured result.
Both scores are independent but complementary. Improving one often strengthens the other, because strong content structure and clarity serve both audiences.
The SEO Score is built from four pillars that reflect how search engines evaluate a page.
Covers crawlability, indexing signals, and technical accessibility — the foundation that determines whether search engines can reliably find and process the page.
Evaluates topical depth, relevance, and completeness relative to the queries the page is likely to serve.
Measures how clear, scannable, and easy to follow the page is — signals that affect how long users stay and how much they trust what they read.
Checks whether titles, descriptions, and snippet signals are clear and relevant so the page appears accurately in search results.
The AI Readiness Score is built from two layers, each containing components that reflect how AI systems interact with a page in practice.
Can AI systems reliably access and extract the page?
Checks whether the served HTML actually carried the page's content — the question that matters because most AI crawlers do not execute JavaScript — and whether an indexing directive withholds the page. Substantial retained text settles it, so a framework hydration payload is never mistaken for missing content; the text-to-markup rate is consulted only when there is too little text to settle the question. Platform-specific robots access is reported separately as a ceiling, and this component does not infer repeated-response stability that was not measured.
This checks whether the audit can retain the page's primary text from the delivered HTML. A readable result does not guarantee citation; an unreadable result withholds the score and identifies a delivery risk.
Longer, multi-section pages are checked for descriptive section headings. Short pages, forms, utility screens, and pages without distinct prose sections are not penalized for missing H2s, lists, or Q&A blocks.
Scores valid, applicable structured data only when it is present. Optional schema that is absent is left out rather than treated as a success or failure.
Once retrieved, can AI systems understand, trust, and reuse the content?
This counts the distinct named subjects the page carries — as an absolute count and per 1,000 words, scored against whichever of the two is weaker — then adds how many appear in the opening 200 words, whether the page's own subject recurs in the body, whether structured data or an outbound reference ties it to a record elsewhere, and whether two candidate names conflict. A page with too little body text to support a rate is reported as not scored. It does not require an early definition or penalize multiple H1 elements by itself.
This applies only when the page contains explicit question intent. It recognizes definitions, procedures, lists, references, descriptive answers, and side-by-side comparisons; a substantive matching Q&A answer or comparison table counts as direct evidence. AIO Mapper does not require every page to contain an FAQ.
This flags exact absolute claim sentences that lack nearby evidence language. It no longer assigns penalties from claim-count or numeric-density quotas, and it retains the sentence needed to verify the recommendation.
Checks qualified claim-level sources and author or publisher context. Citation requirements adapt to the page and its claims rather than imposing a universal link quota.
The AI Readiness Score combines only the measured components that apply to this page. Checks that are irrelevant to the page's purpose, or signals that require site-level evidence the audit does not have, are left out rather than scored as zero.
Weights are renormalized across the components that remain, so the denominator reflects applicable evidence instead of a universal checklist. When the audit verifies that the delivered page contains too little primary text to score safely, it withholds the score and makes that delivery issue the first action.
Renormalization cannot manufacture confidence: the least-covered required layer limits the maximum score. Optional schema is neutral when absent, and crawler permissions for model training are reported separately from search visibility.
No single supporting measurement decides the outcome on its own. The action plan includes only findings with retained evidence and a safe, verifiable next step.
The audit found strong evidence across the checks that apply to this page. This is not a prediction that an AI system will cite or reuse it.
Most applicable checks are healthy, with specific gaps still worth addressing. Use the retained evidence to decide what to change.
Several applicable checks need attention. Start with access or extractability when those checks failed, then follow the page-specific actions.
The audit found foundational problems in the checks that apply to this page. Fix any verified delivery or text-extraction issue before downstream content work.
Use bands as directional guidance. Trends across multiple audits matter more than any single snapshot.
They are designed to reduce ambiguity and surface clarity gaps — not to create anxiety.
A single audit is a moment in time. The trend across audits is the signal.
Both your SEO and AI Readiness scores will shift as you make changes. Common drivers include:
The AI Readiness Score is an on-page diagnostic. It summarizes retained evidence from the checks that apply to the audited page; it does not forecast citations. AI visibility Tracking (a Pro feature) is the observed result: it checks whether your site is cited in Google AI Mode for the questions you track over time.
Read the two together. Healthy on-page diagnostics with no observed citations mean the retained page checks do not fully explain the gap; review query fit, competing sources, authority, and distribution next. When the audit verifies an on-page defect, address its evidence-backed action and then re-audit before drawing conclusions from the score.
The goal is not a perfect score. The goal is clarity, trust, and consistent visibility across the discovery surfaces that matter to your audience.