Mobile-first indexing

Since 2019, Google uses the mobile version of your site as the canonical version for indexing and ranking. If your mobile experience is worse than your desktop, you have a problem, and most sites do. This page walks through what mobile-first indexing actually means, what breaks most often, how to audit your site, and the pre-ship checklist for any change that might affect mobile rendering.

The mindset shift

If you're over 35, you probably still design for desktop first and then "make sure mobile works." Reverse the mental model. Design for mobile first. Desktop is a nice-to-have. Google treats mobile as the source of truth.

Any content that only exists on desktop, effectively doesn't exist for search. That's the rule.

What mobile-first indexing means, precisely

Google crawls your site using a smartphone user agent (Googlebot Smartphone). It evaluates content, structure, schema, internal links, and signals based on what the mobile version shows. Any content hidden or absent on mobile gets weighted accordingly.

What can break

Responsive vs separate mobile site vs dynamic serving

Go responsive. One HTML, one codebase, one source of truth. The historical reasons people built separate mobile sites no longer apply.

How to audit mobile-first issues

  1. Search Console Mobile Usability report. Highlights tap targets too close, text too small, content wider than screen.
  2. URL Inspection, Test live URL, Rendered HTML. Shows exactly what Googlebot Smartphone sees. Compare to your desktop view.
  3. Mobile-Friendly Test. Individual-URL check.
  4. Chrome DevTools device emulation. Open DevTools, toggle device toolbar, view source. Compare source between desktop and mobile.

The pre-ship checklist

The biggest mistake

Building a fantastic desktop experience and treating mobile as an afterthought. Your desktop masterpiece is invisible to Google if the mobile version doesn't match. Test mobile first, ship mobile first, fix mobile first.

What to do with this

Open your top-ranking page in Chrome. Toggle device emulation. Scroll through as a mobile user. Now open Search Console's URL Inspection, paste the same URL, and compare the rendered HTML. Any differences between what you see in DevTools and what Google sees are bugs worth fixing.

Next: HTTPS and SSL, the encryption layer that's non-negotiable in 2026.