Mobile SEO Guide: Optimise for the Index Google Actually Uses

May 10, 20258 min read

Google switched to mobile-first indexing in 2023, meaning Google's crawlers primarily visit and evaluate the mobile version of your site. Your desktop site is secondary. If your mobile experience is degraded — missing content, slow loading, tiny tap targets — your rankings reflect that, on desktop and mobile alike.

What Mobile-First Indexing Means in Practice

Google uses a smartphone Googlebot to crawl your pages. It renders your site as Chrome on Android would. The content it sees determines how and where you rank.

Implications:

If your mobile site hides content behind tabs or accordions, Google may give it less weight
If your mobile page loads slowly, your Core Web Vitals scores suffer
If your mobile site has different content than desktop, mobile content is what Google indexes

1. Ensure Content Parity

The most common mobile indexing issue: content that exists on desktop but not on mobile.

Check for Hidden Content

Content hidden behind tabs, accordions, or "Show More" elements used to be partially discounted. Google has improved at reading it, but full-page content is safer.

To audit:

Open Chrome DevTools → toggle device toolbar (Ctrl+Shift+M)
Select a mobile viewport (375px width)
Compare the visible content to your desktop version

Key things to check:

Headings (all H1–H4 present on mobile)
Body text (not truncated)
Images and their alt text
Structured data (same on mobile and desktop)

Responsive vs Separate Mobile Site

Responsive design (single URL, CSS adapts layout) is Google's recommended approach. It eliminates content parity issues and requires only one sitemap.

Separate mobile site (m.subdomain.com) is still supported but requires careful rel=canonical and rel=alternate implementation. Most issues Google sees with mobile-first indexing come from m-dot sites with outdated or missing content.

2. Mobile Core Web Vitals

Core Web Vitals scores differ between mobile and desktop. Mobile is typically worse due to:

Slower processors
Variable network connections (3G/4G vs Wi-Fi)
Different rendering behaviour

PageSpeed Insights separates mobile and desktop scores. Optimise for mobile scores — they're what affect rankings.

Metric	Mobile target	Common mobile causes
LCP	≤ 2.5 s	Large hero images not optimised for mobile, slow server
INP	≤ 200 ms	Heavy JavaScript, third-party scripts
CLS	≤ 0.1	Images without dimensions, ads without reserved height

Mobile-Specific Speed Issues

Hero images sized for desktop

A 2400px-wide hero image served to a 375px mobile screen wastes 10× the bandwidth.

<picture>
  <source media="(max-width: 640px)" srcset="/hero-640.webp" />
  <source media="(max-width: 1024px)" srcset="/hero-1024.webp" />
  <img src="/hero-1600.webp" alt="Hero" width="1600" height="600" priority />
</picture>

Render-blocking scripts

Mobile processors are 3–5× slower than desktop. A 200ms blocking script on desktop becomes 800ms on mobile.

Defer everything:

<script src="non-critical.js" defer></script>

3. Mobile Usability

Google Search Console reports mobile usability issues directly. Common ones:

Tap Targets Too Small

Links and buttons must be at least 48 × 48 CSS pixels with 8px spacing between them. Tiny links on mobile are a usability and ranking issue.

/* Ensure minimum tap target size */
.nav-link {
  min-height: 48px;
  min-width: 48px;
  display: flex;
  align-items: center;
}

Text Too Small to Read

Body text should be at least 16px on mobile. Text under 12px triggers a GSC usability warning.

body {
  font-size: 16px; /* minimum */
  line-height: 1.6;
}

Viewport Not Set Correctly

Without the viewport meta tag, mobile browsers zoom out and render your site at desktop width:

<meta name="viewport" content="width=device-width, initial-scale=1" />

This must be in the <head> of every page.

Intrusive Interstitials

Pop-ups that cover the main content on mobile trigger a Google penalty. Specifically prohibited:

Full-screen pop-ups that appear immediately or within the first few seconds
Overlays that must be dismissed before accessing content
Above-the-fold content pushed below by a large banner

Permitted exceptions: cookie consent dialogs, age verification, login walls for paywalled content.

4. Mobile Navigation and UX

Good mobile UX reduces bounce rate and increases engagement signals:

Navigation

Hamburger menu is standard and expected on mobile
Main navigation items should be tappable (not hover-triggered)
Limit top-level navigation to 5–7 items
Include a visible search if your site has significant content

Reading Experience

Line length: 45–75 characters per line (about 300–500px width)
Paragraph spacing: margin-bottom: 1.25em or more between paragraphs
Avoid justified text on mobile (creates uneven word spacing)
Use overflow-x: hidden on the body to prevent horizontal scrolling

Forms on Mobile

Use appropriate input types: type="email", type="tel", type="number"
This triggers the right keyboard on iOS and Android
Labels above inputs (not placeholder text only)
Large submit buttons (full-width on mobile)

5. Testing Mobile SEO

Google's Mobile-Friendly Test

Enter any URL to check if Google can render it correctly on mobile. Flags:

Viewport configuration issues
Content wider than the screen
Text too small to read
Touch elements too close together

GSC Mobile Usability Report

Google Search Console → Experience → Mobile Usability

Shows which pages have usability errors affecting real Googlebot crawls. Fix these first — they're real problems, not lab simulations.

Manual Testing

Don't rely on tools alone. Test on a real device:

iPhone SE (small screen: 375px)
Android mid-range (common among your audience)
Test on 4G, not just Wi-Fi

Mobile SEO Checklist

AI-Powered SEO Strategies: How to Stay Ahead in 2026