Skip to content

Technical eligibility · Branch T.D, Platform crawlers and AI eligibility

T-12 Google generative Search eligibility must be built on core Search eligibility

P0OfficialAutomated

If Google AI visibility is the goal, normal Search crawl, index and snippet conditions must be met, and the generative AI inclusion preference must be managed deliberately.

Scope
Google Search, AI Overviews and AI Mode
Priority
Gate. A FAIL stops publish or launch.
Quality bucket
Technical eligibility
Legacy coverage
GEO-01, GEO-02

Why it matters

AI Overviews and AI Mode draw on pages that Google can already crawl, index and show as snippets. A page that fails those basics, or a site that has switched off generative inclusion without meaning to, will not appear in those answers however well it is optimised. Settling Search eligibility first stops GEO effort being wasted on pages that cannot qualify.

How to implement

  1. Open the correct property in Search Console and review the Search generative AI setting, including any inherited or overridden values.
  2. Keep the inclusion option switched on if you want visibility, and record any change in the SEO changelog.
  3. Use URL Inspection to confirm the page is indexed, and check the canonical, robots, noindex and HTTP status.
  4. Check that the main content is visible in Google's render.
  5. Review any nosnippet or snippet limits for their effect on generative use.
  6. Complete these Search eligibility checks before starting GEO optimisation.

Checklist

  • Open the correct property in Search Console.
  • Review the Settings, then Search generative AI control.
  • If visibility is the goal, keep the "Include my site's links and content..." option switched on.
  • If there is a parent and child property structure, check the inherited and overridden preferences.
  • Record setting changes in the SEO changelog.
  • Confirm with URL Inspection that the page is indexed.
  • Check the canonical, robots, noindex and HTTP status.
  • Test whether the main content is visible in Google's render.
  • If you use nosnippet or snippet limits, manage their effect on generative use deliberately.
  • Establish Search eligibility first, then do GEO optimisation.

How to audit

  • Verify the Search Console setting with a screenshot or a record.
  • Check the setting inherited from the parent property.
  • Evaluate the inclusion status together with AI Performance data.
  • Check Search Console URL Inspection.
  • Check the Google-selected canonical.
  • Review the rendered HTML and the snippet controls.

How UltimateSEO checks this automatically

Automated. Checked automatically: crawled pages are indexable and snippet-eligible (no nosnippet, no max-snippet:0); the Search Console generative AI setting is reported when the property is connected.

States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.

Sources

Part of The UltimateSEO Framework v4.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.

Check this control on your own site

The instant scan maps what it finds to this control and tells you honestly whether it could verify it.