Mobile SEO Best Practices: What Google Actually Cares About

We had a client whose desktop site looked beautiful and loaded fast. Their mobile site, though, used a hamburger menu that covered content, had buttons so small they needed surgical precision to tap, and loaded a 4MB hero image that took 8 seconds on a mobile connection. Organic traffic was declining for months. Once we fixed the mobile experience, traffic reversed course within 6 weeks.

Since Google switched to mobile-first indexing, the mobile version of your site is what Google primarily uses for crawling, indexing, and ranking. If your mobile site is a degraded version of your desktop site — less content, worse performance, broken layouts — that's what Google judges you on.

What Mobile-First Indexing Actually Means

Google's crawler (Googlebot) primarily uses the mobile user agent to crawl your site. The content, structured data, and metadata on your mobile pages are what Google sees and uses for ranking decisions. If content is visible on desktop but hidden on mobile (behind accordions, tabs, or simply not loaded), Google might not count it.

This doesn't mean you need a separate mobile site. Responsive design — where the same HTML adapts to different screen sizes — is Google's recommended approach and what works best for most sites.

Speed on Mobile Is Non-Negotiable

Mobile users are typically on slower connections than desktop users. Even with 5G expanding, many mobile users browse on 4G or spotty WiFi. Your site needs to perform well on those connections.

Target LCP under 2.5 seconds on mobile. This is harder than desktop because mobile processors are slower and connections have higher latency. The hero image or main content block needs to load fast. Compress images, preload critical resources, and avoid render-blocking JavaScript.

Test on real devices, not just Chrome DevTools. The mobile simulation in browser dev tools doesn't perfectly replicate real mobile performance. Test on an actual phone over a cellular connection periodically. You'll often discover issues that emulation misses.

Minimize third-party scripts. That chat widget, analytics tracker, social proof notification, and retargeting pixel each add network requests and JavaScript execution time. On a desktop with a wired connection, the impact is small. On a phone over 4G, each one adds noticeable delay. Audit every third-party script and ask: is this worth the performance cost?

Touch-Friendly Design

Tap targets need to be at least 48x48 pixels. This is Google's guideline, and it's tested in their mobile usability reports. Links that are too close together or too small cause frustration and accidental taps.

Space between interactive elements. A vertical list of links with 2px between them is impossible to navigate accurately with a thumb. Add at least 8px of spacing between tappable elements.

No hover-dependent interactions. Dropdown menus that open on hover don't work on touchscreens. Any interaction that requires hovering needs a tap-based alternative.

Content Parity Between Mobile and Desktop

Don't hide content on mobile to "simplify" the experience. If your desktop page has a detailed FAQ section but your mobile page collapses it into an accordion that's closed by default, Google can still read it — but historically, content in collapsed sections has been given less weight. If the content is important enough for desktop, show it on mobile too.

Images and videos should be present on both versions. If your mobile site strips out infographics or video embeds, Google sees a page with less content than the desktop version.

Structured data (schema markup) should be identical on mobile and desktop. If you add Product schema to your desktop template but not your mobile template, Google's mobile-first crawler won't see it.

Mobile-Specific Technical Checks

Viewport meta tag: Every page needs <meta name="viewport" content="width=device-width, initial-scale=1">. Without it, mobile browsers render the page as if it were a desktop page, forcing users to zoom and scroll horizontally.

No horizontal scrolling. Content that extends beyond the viewport width is a mobile usability error. Tables, images, and code blocks are common culprits. Use responsive tables, set max-width on images, and add overflow-x: auto on code blocks.

Font size legibility. Body text should be at least 16px on mobile. Smaller text forces pinch-to-zoom, which is a negative signal for mobile usability. Line height of 1.5-1.6 improves readability on small screens.

No intrusive interstitials. Full-screen popups that block mobile content when a user arrives from search are a negative ranking signal. Google specifically penalizes pages where an interstitial covers the main content before the user can see it. Newsletter signup modals, cookie notices that require scrolling to dismiss, and app install banners that cover the page all fall into this category.

Testing Your Mobile SEO

Google's PageSpeed Insights: Run your key pages and focus on the mobile results. The mobile score is almost always lower than desktop — that's normal. Focus on the Core Web Vitals metrics more than the overall score.

Search Console Mobile Usability report: Shows pages with mobile usability errors (small tap targets, content wider than screen, text too small). Fix these errors — they directly affect your mobile rankings.

Manual testing: Open your site on your phone. Can you navigate easily? Can you read the text without zooming? Do buttons and links work on the first tap? Does the page load in a reasonable time? Sometimes the most effective test is the simplest one.

Mobile SEO isn't a separate discipline from SEO — it is SEO. With mobile-first indexing, your mobile site is your primary site in Google's eyes. Every optimization you make should work on mobile first, then scale up to desktop. If you have to choose between a beautiful desktop experience and a fast, functional mobile experience, choose mobile every time.