Technical eligibility, control 1 of 20
T-01 Serve accessible, meaningful public URLs
An intended public landing page must return the appropriate successful response and meaningful accessible content. Technical eligibility is not proof that an engine has indexed it.
- Priority
- Gate. A FAIL stops publish or launch.
- Hard gate
- Yes. A FAIL stops publication, whatever the score.
- Change class
- AUTO_WITH_TEST: A candidate requiring relevant tests.
- Quality bucket
- Technical eligibility
Why it matters
A page that crawlers cannot reach, or that returns an error or an empty shell, cannot be indexed or used in answers, however good the content is meant to be. Visitors can also be turned away by blocks they never see. Google's technical requirements and JavaScript guidance exist because crawlers must be able to see the real main content.
Evidence to review
- Status response, fetched body, rendered sample and engine inspection timestamp where authorised.
How to implement
- Inventory routes from the repository, sitemap, crawl, analytics and known external entry points.
- Check HTTP status, soft-404 patterns, access barriers and critical content.
- Use live URL tests and engine inspection when available; keep those observations distinct.
How UltimateSEO checks this
Automated. A check in the scan sets PASS or FAIL for this control, and reports UNKNOWN or BLOCKED when its input is missing.
The check looks at: HTTP status of every crawled URL, soft-404 heuristics, redirect chains longer than two hops and the presence of real main content.
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.