Mobile SEO: How to Optimise for Mobile-First Indexing (2026)

Key Takeaways

Google's mobile-first indexing has been fully rolled out since 2023 — it uses your mobile version as the primary basis for ranking and indexing, regardless of where users browse
Mobile optimisation is not just about responsive design; it includes page speed, font sizes, tap target spacing, and content parity between mobile and desktop
Core Web Vitals are measured on mobile by default in Google Search Console's CrWX data, making mobile performance a direct ranking factor
Small businesses with slow or awkward mobile experiences are consistently outranked by competitors with better mobile UX, even on identical content

More than 60% of UK web traffic now comes from mobile devices, according to Statcounter data for 2025. That figure is even higher for local searches: BrightLocal's Local Consumer Review Survey found that 78% of local business searches on mobile result in an offline visit or contact within 24 hours.

Despite this, mobile optimisation remains one of the most neglected areas in small business SEO. Business owners often review their websites on desktop, miss the mobile experience entirely, and wonder why conversion rates are poor or why rankings aren't improving despite good content.

Google's mobile-first indexing changes the stakes further. Since Google began using the mobile version of your site as its primary indexing and ranking input (fully enforced from late 2023), a poor mobile experience isn't just a user experience problem — it directly affects how Google evaluates and ranks your content, on every device.

This guide covers what mobile-first indexing means in practice, the specific technical and UX factors that matter most, and how to diagnose and fix the most common mobile SEO problems. For the broader technical context, our technical SEO explainer is a good companion read. For a full site health check that includes mobile signals alongside on-page and technical factors, our SEO audit checklist gives you the complete picture. For Core Web Vitals specifically — which are measured on mobile — see our Core Web Vitals guide.

What Mobile-First Indexing Actually Means

Mobile-first indexing doesn't mean Google only crawls mobile pages, or that desktop rankings are based on mobile performance in isolation. It means that when Google's crawler (Googlebot) visits your site, it uses a smartphone user-agent and evaluates the mobile version of your content as the primary signal for indexing and ranking.

The Key Implication: Content Parity

If your desktop site has more content, more structured data, more internal links, or more metadata than your mobile site, Google won't see that additional content. It evaluates what Googlebot's mobile crawler sees.

The most common content parity problems:

Content hidden in tabs or accordions. Some mobile designs hide content in expandable sections to save screen space. Google can crawl this content, but it historically weighted visible content more heavily. Since Google's 2024 clarification, hidden-but-accessible content is treated equivalently — but only if the HTML is present in the mobile DOM, not loaded lazily via JavaScript with failures on mobile browsers.

Images not served on mobile. Some older responsive implementations loaded different markup for mobile that simply omitted large images. If those images contain text context Google would otherwise index, that's a content parity problem.

Structured data missing on mobile. If your desktop template includes JSON-LD schema and your mobile template doesn't, Google won't see your schema. Verify schema presence on both versions.

Checking Your Mobile Indexing Status

In Google Search Console, go to Settings > About Google Search Console and check which Googlebot user-agent is listed as your primary crawler. It should say "Smartphone." If it doesn't, your site is on an older configuration that may not have fully transitioned.

You can also test any individual URL using the URL Inspection tool in GSC. Clicking "Test Live URL" shows what Googlebot actually renders when it crawls that page — you can see the rendered HTML and any mobile-specific rendering issues.

Core Mobile SEO Factors

Responsive Design vs Separate Mobile Site

The two main approaches to mobile delivery are:

Responsive design — one URL, one HTML document, CSS adapts layout to screen size. This is Google's recommended approach.
Separate mobile site — m.yourdomain.com or similar, with separate HTML served to mobile users. Requires careful canonical and alternate tag implementation to avoid indexing problems.

If you're on a separate mobile site, the additional complexity (keeping both sites in sync, maintaining canonical/alternate tags, updating both when content changes) creates significantly more risk of indexing errors. Migrating to a responsive design is the right long-term approach.

For almost all small business sites built in the last five years on WordPress, Shopify, Squarespace, or similar, responsive design is the default. The question isn't whether it's responsive — it's whether the responsive implementation is good.

Viewport Configuration

Your site's HTML <head> must contain the viewport meta tag:

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

Without this tag, mobile browsers render the page at desktop width and then scale it down — resulting in tiny, unreadable text and requiring users to pinch-to-zoom. Google's mobile-friendly test flags missing viewport meta tags as a critical error.

Font Sizes and Readability

Google's mobile usability guidelines specify that text should be legible without zooming. The practical standard is a minimum 16px font size for body text on mobile. Go smaller than 14px and you're likely to see "Text too small to read" errors in Google Search Console.

Check your CSS: if you're using relative units (em, rem) based on a root font size, verify the effective rendered size on a 375px viewport (the width of an iPhone SE — the narrowest common screen size). A root font size of 16px with body text at 1em is correct. A root font size of 12px with 1em body text produces 12px text — a fail.

Tap Target Spacing

Buttons, links, and form elements need adequate spacing to be tappable without accidentally hitting adjacent elements. Google's guideline is a minimum tap target size of 48x48 CSS pixels, with at least 8px of spacing between adjacent targets.

The most common violation: navigation menus where links are too close together on mobile, or footer links listed in a tight column. This triggers "Clickable elements too close together" errors in GSC Mobile Usability.

AMP: No Longer a Ranking Requirement

It's worth clarifying that AMP (Accelerated Mobile Pages) is no longer a ranking requirement or a prerequisite for Top Stories eligibility. Google removed that requirement in 2021. If your site currently uses AMP, it continues to work, but migrating away from it to a well-optimised responsive design is perfectly safe from an SEO perspective and often results in better page experience scores due to fewer constraints on JavaScript and design. AMP made sense as a speed workaround in 2016-2020; for most small business sites in 2026, a properly optimised responsive site performs at least as well without the complexity.

Intrusive Interstitials

Since Google's Intrusive Interstitials update (January 2017, reinforced in subsequent updates), popups and overlays that cover main content on mobile are a ranking signal. Specifically penalised:

Popups that appear immediately on page load and cover the entire viewport
Standalone interstitials that must be dismissed before viewing content
Layouts where the above-the-fold content is entirely an ad/popup, with content below

Permitted (not penalised):

Cookie consent banners (legally required in the UK under PECR/UK GDPR)
Login dialogs where the content genuinely requires authentication
Banners that use a "reasonable amount of screen space" and don't block the main content

If you run popups for email capture or promotional offers, ensure they don't fire immediately on mobile page load. A 30-second delay, exit-intent trigger, or limiting to desktop users only keeps you compliant.

Mobile Page Speed

Page speed on mobile is a separate — and usually worse — story than desktop performance. Mobile devices have slower processors and rely on cellular connections that introduce variable latency. Google uses mobile performance data for Core Web Vitals, and the threshold for "Good" performance is measured against real-world mobile users, not lab conditions.

LCP on Mobile

Largest Contentful Paint (LCP) under 2.5 seconds is the target. On mobile, the most common LCP element is a hero image. Common fixes:

Use modern image formats. WebP images are typically 25-35% smaller than equivalent JPEGs. AVIF is smaller still but has slightly lower browser support. Most CMS platforms now support automatic WebP conversion.

Add the loading="eager" and fetchpriority="high" attributes to your hero image. By default, browsers may defer loading off-screen images. Your hero image is above the fold and should be treated as highest priority.

Preload critical resources. If your LCP element is a CSS background image or a font, a <link rel="preload"> hint tells the browser to fetch it early in the loading process.

Avoid render-blocking scripts above the fold. Third-party scripts (chat widgets, analytics, tag managers) loaded synchronously in <head> delay rendering. Move to async or defer, or load them after the initial paint.

CLS on Mobile

Cumulative Layout Shift is often worse on mobile because:

Images without defined width/height attributes cause layout recalculation when they load
Web fonts can cause FOUT (Flash of Unstyled Text) or FOIT (Flash of Invisible Text) as they load, causing text to reflow
Injected banners (cookie consent, promotional bars) that push content down after initial render

The fix for images: always include width and height attributes on <img> tags. This lets the browser reserve space before the image loads, preventing layout shift.

For fonts: use font-display: swap in your @font-face declarations to ensure text is immediately visible using a fallback font, then swaps to the web font when loaded. This eliminates FOIT.

Mobile UX Factors Beyond Technical SEO

Mobile optimisation isn't purely technical. For retail businesses and service businesses, the conversion path on mobile deserves as much attention as ranking signals.

Click-to-Call Prominence

For retail businesses and local services, mobile visitors who find your site through local search often want to call you immediately. Your phone number should be:

Visible above the fold on mobile (don't make users scroll to find contact info)
Formatted as a tel: link so tapping it dials immediately: <a href="tel:+441234567890">01234 567890</a>
Repeated in the header or a sticky footer element

Mobile Form Usability

If your site has a contact form or quote request form, test it on a real mobile device — not just in Chrome's device emulator. Check:

Input fields are large enough to tap accurately
The correct keyboard type is triggered (numeric keyboard for phone numbers, email keyboard for email fields — set with the type attribute)
The form submits correctly on mobile without JavaScript errors
Success/error messages are visible after submission

Navigation Simplicity

Hamburger menus are near-universal on mobile, but their implementation quality varies enormously. Test that:

The hamburger icon is clearly visible and tappable (at least 44x44px)
The menu opens quickly without animation lag
Sub-menus (if any) are navigable without accidentally triggering parent items
Closing the menu works reliably (tap outside, close button, or back gesture)

What Poor Mobile SEO Costs in Practice

In 2024 we audited a Yorkshire-based B2B services firm whose site scored 31/100 on mobile PageSpeed. Their primary service pages were ranking on page two to three for target keywords. Desktop PageSpeed was 74 — a gap common in sites where development was done on desktop and never properly tested on mobile. After a mobile-focused technical sprint — hero image WebP conversion, deferred third-party scripts, corrected font sizes, and fixed tap target spacing across the navigation — mobile PageSpeed improved to 67 and the CrWX data in Search Console shifted from "Poor" to "Needs Improvement" within six weeks. Three of the five target service pages moved to page one within three months, and monthly form submissions from organic traffic increased by 41%. The changes were entirely technical — no new content, no new links. Just fixing what the mobile crawler was already seeing.

Diagnosing Your Mobile SEO: Tools and Checks

Google Search Console > Experience > Mobile Usability — Lists specific pages with mobile usability errors and the error type. This is your primary diagnostic source. For a complete framework around running this as part of a broader audit, see our SEO audit checklist.

Google Search Console > Experience > Core Web Vitals — Shows field data (real user data) split by mobile and desktop. Mobile is what affects rankings.

Google's Mobile-Friendly Test — search.google.com/test/mobile-friendly — Tests an individual URL and reports whether Google considers it mobile-friendly. Also shows a rendered screenshot of how Googlebot sees the mobile version.

Chrome DevTools device emulation — Reasonable for checking layout at various screen widths, but does not replicate real device performance. For performance testing, use a real device or tools like WebPageTest with a mobile device profile.

RnkRocket's automated site audit — Surfaces mobile usability errors, Core Web Vitals issues, and content parity problems as part of the standard site health check, without requiring manual tool configuration.

FAQ

Does mobile-first indexing mean my desktop site is irrelevant?

No. Google still crawls and indexes desktop content — mobile-first means mobile is primary, not exclusive. However, if your mobile and desktop sites have different content, different metadata, or different structured data, the mobile version is what Google uses for ranking decisions. Keep content parity between both versions.

My site is "mobile responsive" — does that mean mobile SEO is fine?

Not necessarily. A responsive design is a good foundation, but many responsive sites still have mobile performance problems (slow LCP from unoptimised images), usability issues (text too small, tap targets too close), or content parity gaps. "Responsive" just means the layout adapts — it doesn't guarantee a good mobile experience.

How do I check if Google is using my mobile site for indexing?

In Google Search Console, use the URL Inspection tool on your homepage. The "Page indexing" section will show the last Googlebot crawl user-agent. It should say "Googlebot Smartphone." If it says "Googlebot Desktop," your site is on an older indexing configuration — check your GSC settings.

What about Progressive Web Apps (PWAs) — do they help SEO?

PWAs can improve SEO indirectly through better page speed, offline capability, and improved engagement metrics — but they are not a direct ranking factor. A PWA that loads faster and has better Core Web Vitals scores will benefit from those improvements in rankings. However, implementing a PWA solely for SEO purposes is not warranted for most small businesses. The SEO benefits come from the underlying technical quality (fast load, stable layout, responsive design), not from the PWA classification itself. If your site already delivers good Core Web Vitals and mobile UX, the incremental SEO value of adding service worker / manifest infrastructure is marginal.

Mobile-first indexing means Google uses the mobile version of your website as the primary input for all ranking and indexing decisions, regardless of what device a searcher uses. This has been fully enforced for all UK websites since late 2023. For small businesses, the practical implication is that any gap between your mobile and desktop experience — in content, metadata, structured data, or page speed — directly affects how Google ranks your pages. The three most common fixable mobile SEO failures are: (1) content hidden in mobile accordions that Google cannot access; (2) hero images without WebP optimisation causing Largest Contentful Paint failures above 2.5 seconds; and (3) tap targets too small or too close together, triggering mobile usability errors in Google Search Console. All three can be diagnosed using free tools and fixed without a full site rebuild. Mobile performance is measured on real user devices via CrWX data in Search Console — this field data, not lab tests, determines whether your site qualifies for "Good" Core Web Vitals status.

Mobile SEO: How to Optimise Your Site for Mobile-First Indexing