Technical eligibility, control 12 of 20
T-12 Manage Google generative Search eligibility explicitly
Google generative Search uses Search foundations and a documented Search Console inclusion control. An inclusion choice does not guarantee appearance.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- APPROVAL_REQUIRED: Required exact authority must be valid before the consequential action.
- Quality bucket
- Technical eligibility
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.
Evidence to review
- Property identity, effective inclusion setting, inherited/overridden state and technical page evidence.
How to implement
- Read the effective property setting and parent inheritance before proposing changes.
- Verify ordinary indexability, canonicalisation and preview directives.
- Record approved search-visibility choices separately from Google-Extended preferences.
- Do not silently opt a business into broader content use.
How UltimateSEO checks this
Partly automated. The scan records page signals, but a passing signal is kept as information: contextual or account evidence is still needed to establish the control.
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.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.