Technical eligibility · Branch T.C, Render, mobile, performance and security
T-07 Mobile-first parity must be maintained
The mobile version must not have less critical content, metadata, structured data or links than the desktop version.
- Scope
- All public content
- Priority
- Gate. A FAIL stops publish or launch.
- Quality bucket
- Technical eligibility
- Legacy coverage
- SEO-37
Why it matters
Google indexes the mobile version of a page, so anything missing from mobile is effectively missing from search. Mobile visitors also lose content and links that desktop users can see. Gaps in structured data or metadata on mobile can weaken how the page is understood and presented.
How to implement
- Move to a responsive design where possible.
- Compare mobile and desktop content and add anything missing on mobile.
- Make sure the title, meta tags and structured data match across both versions.
- Make sure important links work the same way on mobile as on desktop.
- Diff the mobile rendered DOM against desktop after each release.
Checklist
- Prefer responsive design.
- Check mobile and desktop content parity.
- Make sure the title, meta tags, structured data and important links keep the same function.
How to audit
- Diff the mobile rendered DOM against the desktop version.
How UltimateSEO checks this automatically
Automated. Checked automatically: viewport meta tag, text size and tap-target heuristics on crawled pages; full desktop-versus-mobile content parity is confirmed by a person where the heuristics raise a doubt.
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.