Mobile SEO: Designing for Mobile-First Index

Google has been on a mobile-first index since 2019. What continues to surprise teams is how often their mobile experience is silently different from their desktop experience — different content, different meta, different schema. This guide is the audit we run to find and close those gaps.

What mobile-first actually means

Google crawls your pages with a mobile user-agent. It indexes the mobile HTML. When ranking, it primarily uses the mobile content. If something is missing on mobile, it does not exist in Google’s view of your site — even if it is gorgeous on desktop.

The parity audit

The fastest way to find mobile gaps is to compare the rendered DOM at three viewports:

1. Desktop (1280×800)
2. Tablet (768×1024)
3. Mobile (375×667)

For each page, diff the rendered HTML. Any element present only at desktop widths is missing in Google’s index. Common offenders:

• Tabbed content hidden by default on mobile.
• Accordions that hide long-form copy.
• “Read more” links that load additional content only on click.
• Lazy-loaded images that never get observed.
• Schema markup loaded conditionally.

The mobile viewport

Every page needs:

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

Do not:

• Disable user scaling: user-scalable=no is an accessibility failure.
• Hard-code widths: width=1024 breaks responsive layouts.
• Use maximum-scale=1: prevents users with low vision from zooming.

Tap targets

Apple and Google agree: 48×48 CSS pixels is the minimum. Spacing between targets at least 8 pixels. Run a Lighthouse audit; the tap-targets check is one of the most actionable.

Fonts and layout shift

The CLS hit from web fonts is one of the most under-discussed mobile-SEO issues. Mitigations:

• font-display: optional for decorative fonts, swap for body text.
• Preload the font file.
• Match fallback metrics with size-adjust.
• Reserve space with explicit height on text containers.

Images and media

• Responsive <img srcset> with AVIF + WebP fallback.
• Above-the-fold hero: fetchpriority="high".
• Below-the-fold: loading="lazy".
• decoding="async" for non-blocking decode.

AMP in 2026

AMP is no longer required for Top Stories eligibility. Most publishers have moved off it. Skip AMP unless you have a hard business reason.

Mobile Core Web Vitals

The same CWV rules apply — but mobile is where the variance lives. LCP on a slow 4G connection is the leading-edge ranking signal for mobile. Aim for LCP under 2.5s at the 75th percentile of real-user data, not lab data.

Interstitials

Intrusive interstitials on mobile hurt rankings. Google’s “intrusive interstitials” penalty applies to:

• Standalone interstitials that the user must dismiss before accessing content.
• Layouts where the top of the page looks like a standalone interstitial.

Acceptable: cookie banners, age verification, reasonable paywalls (with robots.txt discipline).

Wrap-up

Mobile-first is not a separate discipline. It is the only discipline. Audit every page as if desktop did not exist — because in Google’s eyes, it barely does.