Technical eligibility · Branch T.C, Render, mobile, performance and security
T-05 JavaScript rendering must be reliable
Critical titles, metadata, text and links must render reliably. Where possible they should be supported by the initial HTML, SSR or SSG.
- Scope
- All public content
- Priority
- Gate. A FAIL stops publish or launch.
- Quality bucket
- Technical eligibility
- Legacy coverage
- SEO-38
Why it matters
If key content or links only appear after fragile scripts run, users on slow or failing devices may see an empty page. Crawlers may also miss the title, text or links entirely. Content that search engines and AI answer engines cannot see cannot be indexed, summarised or cited.
How to implement
- Move critical text, titles, metadata and links into the initial HTML where possible.
- Consider server-side rendering, static generation or a hybrid approach.
- Check the rendered DOM for key pages with URL Inspection.
- Run the page with JavaScript disabled and review crawler screenshots.
- Set up monitoring for JavaScript console and network errors.
Checklist
- Serve critical text and links in the initial HTML where possible.
- Consider SSR, SSG or hybrid rendering.
- Verify the rendered DOM with URL Inspection.
- Set up monitoring for JavaScript console and network errors.
How to audit
- Run disable-JavaScript, rendered DOM and crawler screenshot tests.
How UltimateSEO checks this automatically
Partly automated. The crawler compares visible text with script weight and noscript fallbacks to infer JavaScript dependency; a rendered-versus-raw comparison by a person confirms the state. The crawl gives a signal; a person decides the final state with business evidence.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
- [G12] JavaScript SEO basics
Part of The UltimateSEO Framework v4.1, revised 2026-10-07. Evidence states, control states and the publish gate are explained on the hub.