aio-readiness 1.0.0

AIO Readiness Check v1.0.0

Status

• Version: 1.0.0
• Check identifier: aio-readiness
• Input contract: [email protected]
• Output contract: [email protected]
• Scope: page

Abstract

The AIO Readiness check evaluates observable page-level readiness for Google AI Overviews and AI Mode. It checks whether the scanned page appears eligible for Google Search crawling and snippets, whether preview controls permit useful text, whether visible content is clear, whether structured data matches visible content, whether source and trust signals are present, and whether static page evidence suggests basic page-experience risks.

This check does not predict or promise inclusion in AI Overviews, AI Mode, or any other Google Search feature.

Motivation

Google Search generative AI features rely on normal Google Search eligibility, snippet permissions, helpful visible content, and Google's ranking and quality systems. Site owners can block or limit appearance with standard controls such as noindex, nosnippet, max-snippet, data-nosnippet, X-Robots-Tag, and robots.txt.

A page can be technically ready and still not be selected. This check therefore focuses on concrete readiness and blocker evidence that a site owner can inspect and fix.

Normative Model

The check models AIO readiness as six independent validation steps:

Step weights are normalized decimals and sum to 1.0.

Applicability

The check applies to public HTML pages that are intended to be discoverable in Google Search and potentially appear as supporting links in Google AI Overviews or AI Mode.

Applicable pages include:

• Homepages and landing pages.
• Product, service, feature, pricing, and comparison pages.
• Blog posts, guides, docs, reports, help articles, and FAQs.
• Public pages with advice, recommendations, factual claims, or explainers.

The check is lower-signal for login-only pages, dashboards, checkout pages, internal tools, binary assets, API responses, redirects, and pages intentionally excluded from Google Search.

Pass Criteria

The check passes when the weighted score is at least 90/100.

A passing page normally has:

• A 2xx HTTP status.
• Googlebot access to the scanned path.
• No applicable noindex directive.
• Snippet controls that allow useful previews.
• Meaningful visible text in the scanned HTML.
• Clear title, h1, description, and opening copy aligned around the page topic.
• Structured data that matches visible content when structured data is present.
• Visible authorship, publisher, freshness, source, contact, and policy signals where relevant.
• Basic mobile/page-experience signals such as a viewport meta tag and no obvious intrusive interstitial-like UI.

Warning Criteria

The check warns when the weighted score is from 50 through 89.

Warnings include:

• Canonical URL is missing or points away from the scanned page.
• max-snippet is present with a low nonzero value.
• Some important content is inside data-nosnippet elements.
• Visible content is thin or weakly aligned with title, h1, and description.
• Structured data exists but some key values are not visible on the page.
• Structured data is missing on a page type where normal Google Search structured data would likely clarify the content.
• Authorship, publisher, dates, source links, contact/about links, or policy links are missing where relevant.
• Static page evidence suggests mobile, layout stability, visible-text, large-HTML, or intrusive UI risks.

Failure Criteria

The check fails when the weighted score is below 50.

Failures include:

• Non-2xx HTTP status for the scanned page.
• robots.txt blocks Googlebot for the scanned path.
• Applicable noindex directive in meta robots or X-Robots-Tag.
• nosnippet or max-snippet:0 prevents Search snippets for a page intended for AIO visibility.
• No meaningful visible/indexable content is present.
• Structured data materially conflicts with visible page content.

Evidence Model

The result emits:

• Final URL, HTML byte count, and visible word count.
• Step-level score and weight.
• HTTP status, canonical URL, meta robots directives, X-Robots-Tag, and noindex evidence.
• Path-specific Googlebot robots evaluation, matched user-agent groups, matched rules, and winning rule.
• Google-Extended policy evidence as non-scored informational context.
• Snippet controls from meta robots, X-Robots-Tag, max-snippet, nosnippet, and data-nosnippet.
• Title, h1 values, description, heading count, topic overlap, and answer-opening diagnostics.
• JSON-LD count, JSON-LD types, checked schema fields, and visible-content mismatches.
• Authorship, publisher, dates, source links, about/contact links, and policy links.
• Viewport, visible word count, HTML byte size, image dimension gaps, and possible modal/interstitial-like elements.

Evidence must not include full HTML, credentials, cookies, authorization headers, or private data.

Validation And Scoring Steps

1. Parse the scanned HTML and extract visible text while ignoring script, style, SVG, and noscript content.
2. Fetch /robots.txt from the scanned origin and evaluate Googlebot against the scanned URL path using RFC 9309-oriented rule matching.
3. Evaluate HTTP status, Googlebot access, noindex, canonical signals, and visible indexable text.
4. Evaluate snippet and preview controls from meta robots, X-Robots-Tag, max-snippet, nosnippet, and data-nosnippet.
5. Evaluate visible content clarity using title, h1 count, description, visible word count, topic overlap, heading structure, and answer-first openings.
6. Evaluate structured data consistency when JSON-LD exists. Missing JSON-LD is a warning only when the page type appears likely to benefit from normal Google Search structured data.
7. Evaluate source and trust signals using visible and structured authorship, publisher, dates, source links, about/contact links, and policy links.
8. Evaluate lightweight page-experience proxy evidence from the scanned HTML.
9. Compute the weighted 0-100 score using the published step weights. Pass is >=90, warning is 50-89, and fail is <50.

Standard Behavior

The check uses Google-specific Search controls for AIO readiness:

• Googlebot access affects the scored Google Search eligibility step.
• Google-Extended is reported only as a Gemini/Vertex AI product-policy signal and is not scored as an AI Overview blocker.
• noindex blocks Google Search eligibility when applicable.
• nosnippet and max-snippet:0 are treated as severe preview blockers for pages intended to appear in Google AI features.
• Low nonzero max-snippet values are treated as warning-level restrictions.
• data-nosnippet is detected as a boolean attribute on span, div, and section elements.
• Structured data is evaluated as normal Google Search clarity and consistency, not as special AI Overview markup.

Robots evaluation follows RFC 9309-oriented behavior:

• User-agent groups are parsed from /robots.txt.
• Relevant groups are matched case-insensitively by crawler product token.
• Matching groups with the most specific user-agent token are evaluated.
• Path rules are evaluated against the scanned URL path and query.
• Allow and Disallow path patterns support * and $.
• The most specific matching rule wins; tied Allow rules win over Disallow.
• Empty or absent matching rules allow crawling for the evaluated path.

Non-Standard And Real-World Behavior

AI Overview source selection is proprietary and can differ from ordinary organic ranking. Query type, freshness, source diversity, and Google's quality systems affect whether AI Overviews appear and which supporting links are selected.

The check treats answer-first sections, source links, visible dates, and normal structured data as readiness signals because they improve clarity and accountability for users and search systems. They are not special AI Overview requirements.

Non-Goals And Limitations

This check does not:

• Promise inclusion, ranking, citations, traffic, impressions, or clicks from AI Overviews or AI Mode.
• Test live Google SERPs or actual AI Overview activation.
• Score ChatGPT, Perplexity, Claude, Bing Copilot, or non-Google AI engines.
• Require llms.txt, Markdown alternates, RSL, AI-only files, or special AI schema.
• Treat Google-Extended as a Google Search or AI Overview crawler control.
• Replace full structured-data validation.
• Replace full Core Web Vitals, PageSpeed, or field-data analysis.
• Depend on other checks' outputs.
• Execute arbitrary client-side JavaScript to recover hidden content.

Google Search and AI features change over time. A page can pass this check and still not be selected. A page can also be selected despite imperfect readiness signals if it has uniquely useful, authoritative content.

References

• developers.google.com/search/docs/fundamentals/ai-optimization-guide
• developers.google.com/search/docs/appearance/ai-features
• developers.google.com/search/docs/essentials/technical
• developers.google.com/search/docs/crawling-indexing/robots-meta-tag
• developers.google.com/search/docs/appearance/structured-data/sd-policies
• developers.google.com/search/docs/appearance/page-experience
• developers.google.com/crawling/docs/robots-txt/robots-txt-spec
• developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers
• www.rfc-editor.org/rfc/rfc9309.html

aio-readiness v1.0.0 Changelog

• Defines the initial AIO readiness contract for Google AI Overviews and AI Mode supporting-link readiness.
• Scores Google Search eligibility, snippet and preview eligibility, visible content clarity, structured-data consistency, source and trust signals, and page-experience proxy evidence.
• Treats Googlebot access, noindex, and snippet controls as the primary observable AIO eligibility blockers.
• Reports Google-Extended as non-scored Gemini/Vertex AI product-policy evidence rather than an AI Overview crawler blocker.
• Treats missing JSON-LD as conditional guidance instead of a hard AIO failure; structured data is evaluated for consistency with visible content when present.