Google indexes and ranks pages based on their mobile version. That's mobile-first indexing, and it's how Google Search works today: Google crawls your site with its smartphone crawler and uses what it finds there for indexing and ranking. For most modern responsive sites this is invisible, because the mobile and desktop versions are the same page. For sites where mobile pages are trimmed down, load content differently, or hide things from small screens, mobile-first indexing can quietly cost rankings. This guide explains what mobile-first indexing means in practice, the problems that cause trouble, and how to check your own site.

What Mobile-First Indexing Means

Googlebot comes in two main forms: a desktop crawler and a smartphone crawler. Under mobile-first indexing, Google primarily uses the smartphone crawler, and the content it sees on mobile is what Google indexes and ranks, for both mobile and desktop searches.

The practical consequence is simple: if something isn't on your mobile page, Google may not know it exists. Content, links, structured data, and metadata that appear only on desktop don't count the way they used to.

Google's documentation says a mobile version isn't strictly required for a site to appear in search results, but it's very strongly recommended. The guide to how search engines crawl and index your website covers the broader pipeline mobile-first indexing plugs into.

Three Ways Sites Serve Mobile Pages

  • Responsive design: the same HTML at the same URL, with CSS adapting the layout to the screen. Google recommends this approach, and it avoids most mobile-first problems because both versions are the same page.
  • Dynamic serving: the same URL, but the server sends different HTML depending on the device. Parity problems are common here because two versions of the HTML must be kept in sync.
  • Separate mobile URLs: a separate mobile site, often on an m. subdomain. This setup has the most potential for problems and requires the most careful configuration.

If your site is responsive, most of what follows is a quick check. If it uses dynamic serving or separate mobile URLs, work through every section.

The Content Parity Problems That Cost Rankings

Less content on mobile

Some sites shorten mobile pages to make them faster or tidier: fewer paragraphs, removed sections, shorter product descriptions. Under mobile-first indexing, that shortened version is what Google evaluates. Google's guidance is that the mobile site should contain the same primary content as the desktop site.

Accordions, tabs, and expandable sections are fine for layout, as long as the content is in the page and equivalent to desktop. Google's concern is content that's missing, not content that's collapsed.

Content that needs interaction to load

Google's documentation states that Google won't load content that requires user interactions, such as swiping, clicking, or typing, to appear. If your mobile page only loads more content when a user taps "load more," or loads primary content only after scrolling triggers a script, Google may never see it.

Lazy loading is fine when it's implemented so content loads as it enters the viewport without a user action. Primary content should never depend on a tap to exist in the page.

Different headings, titles, and descriptions

Google recommends using the same clear, meaningful headings on mobile as on desktop, and equivalent titles and meta descriptions. Templates sometimes shorten titles or drop headings for small screens. Check with the Heading Structure Checker that the mobile outline matches.

Missing structured data

If your desktop pages carry structured data and your mobile pages don't, that markup effectively doesn't exist for Google. Google's guidance is to keep structured data the same on both versions. Validate it with the Schema & Structured Data Tester. The schema validation guide covers common errors.

Different robots directives

Use the same robots meta tags on mobile and desktop. A noindex that exists only on the mobile template removes the page from Google's index entirely, because the mobile version is what Google indexes. The Indexability Checker confirms which directives a page carries.

Blocked resources

Don't block the CSS, JavaScript, or image URLs that mobile pages need in robots.txt. If Google can't load them, it can't render the page as users see it. Test your rules with the Robots.txt Tester.

Images and video

Use the same high-quality images on mobile, with stable URLs and the same alt text as desktop. Google notes that changing image URLs can cause a temporary loss of image search traffic. For video, use supported formats, stable URLs, and matching structured data, and place videos where they're easy to find on mobile. The image SEO guide covers alt text and formats.

Mobile Page Experience

Mobile-first indexing is about which version Google indexes, but mobile users also experience your site under tighter constraints: slower connections, smaller screens, and touch input. Two areas matter most.

Performance. Core Web Vitals tend to be worse on mobile than desktop, because phones have less processing power and often slower networks. The Core Web Vitals guide explains each metric. The Page Speed Optimizer shows mobile and desktop scores side by side.

Intrusive ads and pop-ups. Google's mobile guidance points to the Better Ads Standard and warns that large ads at the top of mobile pages hurt the experience. Full-screen interstitials that cover content on arrival frustrate users on small screens.

If You Use Separate Mobile URLs

An m-dot site needs extra care. Google's documentation recommends:

  • Matching error status: if a desktop URL returns a 404, its mobile counterpart should too.
  • Avoiding fragment URLs, those with #, as mobile URLs.
  • Not redirecting many desktop pages to a single mobile page, such as the mobile homepage.
  • Verifying both versions in Search Console.
  • Keeping hreflang annotations within each version: mobile pages point to mobile alternates, desktop to desktop.
  • Using the desktop URL as the canonical, with the mobile URL marked as its alternate.
  • Making sure your server can handle the increased crawling of mobile URLs.

For many sites, the cleanest long-term fix is moving to responsive design, which removes these maintenance burdens entirely. If you do, plan it as a migration with proper redirects. The upcoming website migration SEO checklist covers that process.

How to Check Your Site

  • Inspect key URLs in Search Console. URL Inspection shows the crawler Google used and lets you view the rendered page and HTML. Confirm your main content, headings, links, and structured data are all present.
  • Compare mobile and desktop versions. On your main templates, check that text, headings, internal links, images, and structured data match.
  • Check for interaction-dependent content. Make sure nothing important requires a tap or click to load.
  • Audit mobile performance with the Page Speed Optimizer.
  • Run the SEO Audit Tool on one page from each template. It checks the viewport tag, robots directives, headings, structured data, and more.

If your site is responsive and your templates are consistent, mobile-first indexing is mostly already handled. The work is in catching the exceptions: the template that trims content on small screens, the plugin that adds a mobile-only noindex, or the section that loads its main text only after a tap.