Mobile-first indexing

Long definition

For most of the web's history, Google indexed the desktop version of a page and treated mobile as a secondary, lighter rendering. By the mid-2010s, mobile traffic had overtaken desktop globally, and Google announced in 2016 that the index would flip — mobile would become the primary source. The rollout was gradual: opt-in 2018, default for new sites in July 2019, all sites covered by 2023 per Google's official documentation.

What this changes in practice:

• Googlebot identifies as a smartphone user agent when crawling. Your mobile version is what gets parsed, rendered, and indexed.
• Content parity matters. If your desktop page has 2,000 words and your mobile version hides half behind "read more" tabs that aren't expanded by default, Google sees the visible mobile content. Hidden-but-loaded content still counts; not-loaded content doesn't.
• Structured data parity matters. Schema markup must be present in the mobile version. Common bug: structured data injected only on desktop layouts or breakpoints.
• Internal links matter. A "main navigation" that's full on desktop but collapsed to a hamburger on mobile is still crawled, but only if the links are in the rendered HTML. Lazy-loaded menus are a common gotcha.
• Images and lazy-loading matter. Mobile pages with aggressive lazy-loading need proper loading="lazy" and intersection observers, not "load on click" — Googlebot doesn't click.

The fix for most sites is responsive design with a single URL and layout that adapts. Separate m.example.com mobile sites still work but require strict parity, alternate/canonical pairing, and Vary headers — most teams have moved off them.

Search Console's URL Inspection tool shows which user agent indexed your URL — "Smartphone Googlebot" is the modern default. The old "Mobile usability" report was retired in December 2023 because mobile-first is now baseline; mobile usability checks moved into Lighthouse and Chrome DevTools.

Common misconceptions

• "Mobile-first means desktop doesn't matter." Desktop traffic still ranks and converts. Mobile-first is about which version Google reads to build the index, not about which audience matters. Both should work.
• "Hidden content under tabs and accordions is invisible to Google." Not since the mobile-first rollout — Google indexes content in collapsed elements as long as it's in the rendered HTML. The exception is content not loaded at all until interaction.
• "My responsive site is automatically fine." Responsive design is the easiest path, but bugs creep in: breakpoint-specific schema, conditional rendering, mobile-only intrusive interstitials. Audit with the Mobile-Friendly Test and Lighthouse.
• "AMP is required for mobile-first indexing." Never was. AMP is a separate (and largely deprecated) framework. Mobile-first indexing applies to whatever HTML your mobile rendering serves.