Responsive design solved the wrong half of the problem.
A site that reflows to fit a phone screen looks correct in a browser window dragged narrow. That is not the same as working for somebody outdoors, on mobile data, one-handed, with a cracked screen in daylight, who needs your phone number in the next ten seconds.
Mobile SEO best practices start where responsive design finishes. The layout adapting is table stakes. What matters is what gets sent, what gets hidden, and whether the thing can actually be used.
Mobile SEO Best Practices Beyond Responsive Design
Mobile-first indexing, and what it really means
Your pages are indexed primarily on their mobile version. Not the desktop version, not an average of the two.
The consequence catches people out: if your mobile site shows less content than your desktop site, the reduced version is what gets assessed. Content you removed for a cleaner phone experience is content search engines may never see.
This is the parity problem, and it is the most common serious mobile SEO failure precisely because nothing surfaces it. The desktop site looks complete, the mobile site looks tidy, and nobody compares them.
The four parities to check
- Content parity. Does the mobile version contain the same text? Collapsed accordions are fine, since the content is present in the markup. Content genuinely removed for mobile is not.
- Structured data parity. Does your markup appear on both versions? It is frequently attached to desktop templates and quietly missing from mobile ones.
- Metadata parity. Titles and descriptions should match across versions.
- Link parity. Mobile navigation is often simplified to the point where internal links disappear, which changes how pages are discovered and how relationships between them are understood.
Check by fetching your page with a mobile user agent and comparing what comes back against the desktop version.
Speed, on a real device
Test on an actual mid-range phone on mobile data, not a desktop browser window made narrow. The narrow window still has your office broadband and your desktop processor behind it, which hides both problems you have.
Images are almost always the largest issue. Serve them at display dimensions in modern formats, use responsive sources so a phone does not download a desktop-sized hero, and lazy-load anything below the fold except your main image.
JavaScript is the most expensive payload per byte on mobile, because parsing and execution cost is felt directly on a slower processor.
Where performance and environmental impact both apply, treat them as the same lever: reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured.
Usability things people forget
- Tap targets. Buttons and links need enough space around them that a thumb can hit them reliably. Adjacent links in a text list are a recurring failure.
- Text size. Readable without zooming, in daylight, by somebody who left their glasses at home.
- Layout stability. Elements that jump as images and fonts load cause mis-taps, which is the most infuriating thing a mobile page can do.
- Interstitials. Popups covering content immediately on arrival are penalised and are also the fastest way to lose somebody who has just arrived.
- Forms. Correct input types so the right keyboard appears, autofill support, and no field asking for information you do not need. Every field is harder on a phone than on a desktop.
Accessibility overlaps almost entirely
Sufficient contrast helps somebody with low vision and also somebody reading in bright sunlight. Generous tap targets help somebody with a tremor and also somebody on a bus.
Work towards WCAG 2.1 Level AA. The W3C’s guidance on mobile accessibility covers where the two subjects meet, which is most places.
What to check first
Fetch your key pages with a mobile user agent and compare the content against desktop. Test on a real mid-range device on mobile data. Then measure Core Web Vitals under stated conditions and fix images before anything else.
Nobody can guarantee rankings from this work. What it does is remove the reasons a page would be assessed on less content than it actually has, which is a specific and fixable problem.
Our search engine optimisation work checks parity as standard, since it is invisible from either version alone.