What is Mobile-First Indexing?

Mobile-first indexing means Google primarily uses the mobile version of a page when crawling, rendering, and evaluating it for rankings. The desktop version is secondary. If your mobile and desktop pages differ in any meaningful way, what Google sees and ranks is the mobile version.

This is not a penalty system. It is simply how Google's crawl infrastructure now works. Googlebot fetches pages using a smartphone user agent by default. The page it retrieves, renders, and stores in its index is the mobile version. Desktop content that does not exist on mobile does not exist as far as Google is concerned.

What is the history of mobile-first indexing?

Google began testing mobile-first indexing in 2017. The rollout was gradual: sites were moved over in batches based on their mobile readiness. By 2019, all new sites were placed into mobile-first indexing by default. Google completed the full rollout, covering all remaining sites, in 2024.

If your site was built or significantly updated after 2019, it has always been mobile-first indexed. If it predates that, it was migrated at some point during the rollout. Google Search Console notifies site owners when a property is moved to mobile-first indexing. You can confirm which user agent crawled any given page using the URL Inspection tool.

What does mobile-first indexing mean in practice?

Three things follow directly from Google using your mobile page as the source of truth.

Content that only appears on desktop is invisible to Google. If your desktop layout shows a detailed product description that collapses to a single paragraph on mobile, Google indexes the single paragraph. The desktop version's additional content contributes nothing to the ranking of that page.

Metadata is taken from the mobile version. Title tags, H1s, meta descriptions, and canonical tags are all read from the mobile page. If your mobile and desktop pages have different title tags, Google uses the mobile title tag. If they have conflicting canonical directives, Google uses the mobile canonical.

Mobile page speed matters more. Core Web Vitals are measured on mobile by default in the Chrome User Experience Report. INP, LCP, and CLS scores reported in Search Console and PageSpeed Insights reflect mobile performance unless otherwise specified. A page that loads well on desktop but poorly on mobile is performing poorly by Google's primary measure.

What are the common mobile-first indexing problems?

Most sites running on responsive design handle mobile-first indexing without issues. Problems arise when there is a meaningful difference between what the mobile and desktop versions deliver.

Content hidden on mobile that is not rendered. Some designs collapse long sections into accordions or tabs on mobile. If those collapsed sections rely on JavaScript to expand, and Google's crawler does not execute that JavaScript fully, the content does not exist in the index. Google does execute JavaScript, but it is not instant and not guaranteed. Content that needs to be in the index should be in the HTML, not loaded conditionally by client-side scripts. See what is JavaScript SEO for a detailed breakdown of how Google handles JS rendering.

Different metadata on mobile and desktop. A common legacy pattern from the pre-responsive era: a separate mobile site (m.dot) with different titles and descriptions optimised for shorter mobile screens. If those titles differ from the desktop equivalents, Google indexes the mobile versions. Audit your mobile metadata carefully if you are running a separate mobile site.

Images that only load on desktop. Responsive image implementations that hide large images on mobile using CSS display: none may mean those images are not indexed. Google can see content hidden with CSS, but selectively loading images only on desktop via JavaScript means the mobile version genuinely lacks them.

Videos that do not work on mobile. Flash video is the historical example, but the pattern continues: video players that fail on mobile, autoplay restrictions that prevent rendering, or embeds served only in desktop breakpoints. Video content Google cannot access on mobile is not indexed.

Lazy-loaded content that does not render in Google's mobile crawler. Lazy loading images and content below the fold is a legitimate performance technique, but it requires correct implementation. Use the loading="lazy" attribute on <img> tags rather than JavaScript-based lazy loaders that may not trigger without user scroll events. Google's crawler does not scroll the way a user does.

Mobile page loads significantly more slowly than desktop. A common pattern with older sites: the desktop version is served from a fast CDN with optimised assets, while the mobile version relies on a different stack or serves unoptimised images. Core Web Vitals data will reflect this divergence, and rankings will be suppressed accordingly.

Canonical tags that conflict between mobile and desktop. On a responsive site this is rarely an issue. On a separate mobile site (m.dot architecture), the canonical configuration requires care: mobile pages should carry a canonical pointing to their desktop equivalent, and desktop pages should carry an alternate link pointing to their mobile version. Mistakes here can cause Google to index the wrong version or neither.

How do you check mobile-first indexing compliance?

Google Search Console URL Inspection. Inspect any URL and look at the Crawl section. It will show which Googlebot user agent last crawled the page: Googlebot Smartphone or Googlebot Desktop. A correctly mobile-first indexed site shows Googlebot Smartphone for all pages. If you see Googlebot Desktop for a page, that page has not been crawled under mobile-first indexing yet.

Chrome DevTools mobile emulation. Open DevTools, switch to the device toolbar (Ctrl+Shift+M on Windows, Cmd+Shift+M on Mac), and load your pages at 375px or 390px width. This is not a perfect simulation of Google's crawler, but it is the fastest way to visually compare what your mobile version delivers versus your desktop version. Look specifically for missing sections, hidden content blocks, and navigation differences.

Compare mobile and desktop HTML. The most reliable approach is to fetch the page twice: once with a desktop user agent and once with a mobile user agent, and diff the HTML. If the mobile HTML is missing content that appears in the desktop HTML, that content is not in Google's index.

Responsive design vs separate mobile site. A responsive design serves the same HTML to all devices and uses CSS to adapt the layout. This is the simplest approach and eliminates most mobile-first indexing risks, since the content is identical regardless of which user agent fetches it. A separate mobile site (m.dot) requires careful canonical and alternate link configuration, consistent metadata, and parity of content between versions. Google still supports m.dot sites, but responsive is simpler to maintain and less prone to configuration errors.

If you are running a separate mobile site, the canonical tag implementation is critical. See what is a canonical tag for the correct setup.

How does this interact with Core Web Vitals?

Core Web Vitals are Google's page experience signals: LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift). These are measured in the Chrome User Experience Report using real user data, and the data Google uses for ranking is the mobile data by default.

A site with excellent desktop Core Web Vitals and poor mobile Core Web Vitals is a site with poor Core Web Vitals as far as Google's ranking systems are concerned. Page experience scores in Search Console's Core Web Vitals report are split by mobile and desktop; always audit the mobile column first.

The implications for technical SEO are concrete: mobile image optimisation, reducing render-blocking resources on mobile, and avoiding large layout shifts on smaller screens are not optional refinements. They are direct inputs to a ranking factor that Google evaluates using mobile data.

For a complete view of how page indexability interacts with mobile-first crawling, and how to confirm which of your pages Google can and cannot access, see what is page indexability.

---

Crawly crawls your site using a configurable user agent, making it straightforward to check what your pages deliver to Googlebot's mobile crawler. Run a crawl with the Googlebot Smartphone user agent, compare the results against a desktop crawl, and any pages with missing content, conflicting metadata, or indexability differences will surface immediately. Download Crawly and run both crawls today.