Mobile-First Indexing

Mobile-first indexing means Google predominantly uses the mobile version of your website for crawling, indexing, and ranking. Since the majority of Google searches now happen on mobile devices, Google evaluates your site based on what mobile users experience — not what desktop users see.

What Changed With Mobile-First Indexing

Before Mobile-First (Pre-2018)

Google primarily crawled the desktop version of websites. The mobile version was used for mobile-specific ranking adjustments, but desktop content determined the baseline ranking.

The Transition (2018–2023)

Google gradually switched sites to mobile-first indexing. By late 2023, all sites were on mobile-first indexing.

Now (2024 Onwards)

There is no "desktop-first" indexing anymore. Google crawls and indexes your mobile version. What appears on your mobile site is what Google sees for ranking purposes.

Why This Matters for SEO

Content Parity

If your mobile site shows less content than your desktop site, Google only sees the mobile content. Common content parity issues:

• Tabs and accordions — content hidden behind expandable elements on mobile. Google may still index this, but prioritises visible content.
• Simplified mobile pages — some sites serve stripped-down mobile versions with less text, fewer images, and fewer features.
• Missing structured data — schema markup present on desktop but absent on mobile.
• Different navigation — mobile hamburger menus with fewer links than desktop navigation.

Internal Link Parity

Internal links on your mobile site must match or mirror your desktop links. If the mobile version has fewer internal links:

• Authority distribution is reduced
• Some pages may become harder for Google to discover
• Topical clustering signals are weakened

Mobile Performance

Google evaluates Core Web Vitals primarily from mobile users. Your mobile page speed, responsiveness, and visual stability directly affect rankings.

Mobile Configuration Types

Responsive Design (Recommended)

One URL, one set of HTML, adapts to screen size via CSS:

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

Advantages:

• Single URL for all devices — no duplicate content issues
• Same content and links on all versions
• Easier to maintain
• Google's recommended approach

Dynamic Serving

Same URL but different HTML served based on user agent:

Drawbacks:

• Requires Vary: User-Agent header
• Complex to maintain
• Risk of serving wrong version
• Must ensure content parity across versions

Separate Mobile Site (m.example.com)

A completely separate mobile website:

Drawbacks:

• Duplicate content risk
• Requires rel="canonical" and rel="alternate" tags
• Double maintenance burden
• Link equity split between desktop and mobile URLs
• Not recommended — migrate to responsive design

Mobile-First Optimisation Checklist

Content

• Same content visible on mobile as on desktop
• Same headings (H1–H6) present on mobile
• Same structured data on mobile as desktop
• Images and videos present on mobile (with proper alt text and titles)
• Expandable content (tabs, accordions) is crawlable and indexable

Navigation & Links

• Mobile navigation includes all important internal links
• Footer links present on mobile
• Breadcrumb navigation functional on mobile
• No broken links specific to mobile version

Performance

• LCP under 2.5 seconds on mobile networks
• INP under 200ms on mobile devices
• CLS under 0.1 (critical on mobile due to smaller screens)
• Images optimised for mobile viewport widths
• Touch targets at least 48px × 48px

Viewport & Rendering

• Viewport meta tag correctly configured
• No horizontal scrolling
• Text readable without zooming (minimum 16px font size)
• Content fits within the viewport width
• No intrusive interstitials (popups) on mobile

Testing Mobile-First Readiness

Google Search Console — Mobile Usability

The Mobile Usability report identifies:

• Clickable elements too close together
• Content wider than screen
• Text too small to read
• Viewport not set

Google PageSpeed Insights

Test your pages on PageSpeed Insights with the "Mobile" tab selected. This simulates mobile conditions and identifies:

• Mobile-specific performance issues
• Core Web Vitals on mobile
• Opportunities for mobile optimisation

Chrome DevTools Device Emulation

1. Open Chrome DevTools (F12)
2. Click the device toggle icon
3. Select a mobile device (e.g., iPhone 14, Pixel 7)
4. Browse your site and check for layout issues

Google Rich Results Test

Verify that structured data present on your desktop site also appears on the mobile version.

South African Mobile Context

Mobile optimisation is especially critical for South African audiences:

• Mobile-dominant market — the majority of South African internet access is via mobile devices
• Varied device quality — many users are on mid-range or budget devices with limited processing power
• Data cost sensitivity — smaller, optimised pages reduce data consumption, which is a genuine user concern
• Network variability — 3G and slow 4G connections are common outside major urban centres
• Touch interaction — design for touch first, not mouse clicks

Key Takeaways

• Google uses the mobile version of your site for indexing and ranking — there is no opt-out.
• Content, links, and structured data must be the same on mobile as on desktop.
• Responsive design is the recommended configuration.
• Mobile performance (speed, responsiveness, stability) directly impacts rankings through Core Web Vitals.
• South African websites must prioritise mobile given the mobile-dominant user base.

Tools & Resources (Coming Soon)

• Mobile Usability Checker (Coming soon)
• Page Speed Checker (Coming soon)
• Responsive Design Tester (Coming soon)

Related SEO Documentation

• Core Web Vitals Explained
• Site Speed Optimisation
• What Is Technical SEO?
• Image Optimisation for SEO
• How Search Engines Work