Technical eligibility, control 7 of 20
T-07 Preserve mobile content and function parity
Mobile users and mobile indexing must not receive an accidentally diminished version of important content, links or metadata.
- 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
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.
Evidence to review
- Mobile/desktop render comparison and completion of key user tasks.
How to implement
- Compare mobile and desktop facts, images, structured data and primary actions.
- Check accessible tabbed content; equivalent presentation need not look identical.
- Test viewport overflow, touch controls, consent overlays and media loading.
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: 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.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.