Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Mobile-First Indexing: Why Responsive Design Keeps You Safe

Updated · 7 min read

Short answer Google indexes and ranks the phone version of your pages, and since July 5, 2024 it crawls every site with its smartphone crawler. Text, photos, titles or structured data missing from your mobile page don't count. Responsive design sends the same page to every device, so the two versions can't drift apart.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What mobile-first indexing means

Google reads your site the way a phone sees it, and ranks it on that. Desktop searchers get results built from your mobile pages too.

"Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." (Google Search Central: Mobile-first indexing best practices)

So the rule for an owner is simple: anything a phone visitor can't get to, Google doesn't count. Google's own words on a thinner mobile page: "you can expect some traffic loss" (same page).

When did Google switch, and is my site on it?

Yes, your site is on it. The move took eight years and is finished:

DateWhat changedSource
November 2016Google starts testing a mobile-first indexSearch Central Blog, 2016
July 1, 2019Every new website is indexed mobile-first by defaultSearch Central Blog, May 2019
October 2023Google calls the move complete and stops showing the indexing crawler in Search Console settingsSearch Central Blog, October 2023
July 5, 2024The last desktop-crawled sites switch to the smartphone crawlerSearch Central Blog, June 2024

The 2024 post adds the hard edge:

"If your site's content is not accessible at all with a mobile device, it will no longer be indexable." (Google Search Central Blog, June 2024)

You may still see the desktop crawler in your logs. Google says it is sometimes used for product listings and Google for Jobs (same post).

Why responsive design avoids the gaps

Google lists three ways to build a site that works on phones. Only one sends the same page to everyone:

SetupHow it worksWhat can drift apart
Responsive designSame HTML, same URL; the layout rearranges for the screenAlmost nothing: one page to keep up
Dynamic servingSame URL, but the server sends phones different HTMLText, images, titles, tags, structured data
Separate URLs (an "m." site)Phones get sent to m.example.comAll of the above, plus redirects, error pages and canonical tags

Google's guide says its long checklist applies only to the last two, because with responsive design "the content and the metadata are the same on the mobile and desktop version of the pages" (Mobile-first indexing best practices). It also names responsive as its pick, "the easiest design pattern to implement and maintain" (same page). In 2019 Google wrote that it recommends one URL for desktop and mobile "because of issues and confusion" it had seen with separate mobile URLs (Search Central Blog, May 2019).

Think of it as one price list taped to the counter versus two printed copies. Change one copy and forget the other, and customers see a different price than you meant.

A responsive site still needs one line in its code, the viewport tag (`width=device-width, initial-scale=1`). Without it, the page "loads very zoomed out" on a phone (web.dev: Responsive web design basics). Most modern themes include it.

Gaps a responsive site can still have

Responsive removes the drift between two versions. It doesn't stop you from hiding things on the one version that exists.

  • Content that loads only on a tap. Google says it "won't load content that requires user interactions (for example, swiping, clicking, or typing)" (Mobile-first indexing best practices). Reviews behind a "Load more" button, or service details that appear only after a click and fetch new content, may not be read.
  • Sections turned off for phones. Many page builders have a "hide on mobile" switch. If a hidden section is missing from what Google renders, it doesn't count.
  • Blocked files. If robots.txt (the file that tells crawlers what to skip) blocks your images or page files, Google can't see them. Google says: "Let Google crawl your resources" (same page).

Collapsing text is fine. Google says you can move content "into accordions or tabs" on mobile as long as it stays equivalent to desktop (same page). An FAQ that folds open is safe; an FAQ deleted for phones is not.

What Google compares between mobile and desktop

For sites with two versions, Google judged readiness on "parity of content (including text, images, videos, links), structured data, and other meta-data" such as titles, descriptions and robots tags (Search Central Blog, May 2019). Its troubleshooting list turns that into checks:

CheckWhat goes wrong on the phone version
Text and headingsServices or areas you serve are cut to save space
ImagesMissing, too small, low resolution, or no alt text (the image description)
Structured data (code that labels your business details for Google)Present on desktop, missing on mobile
Title and meta descriptionMissing or different
Robots meta tagA `noindex` on mobile only, so Google drops the page
Error pagesThe desktop page works; the mobile one shows an error
RedirectsEvery desktop page sends phones to the mobile home page
VideoHard to find, or far down the page

All from Google's guide (Mobile-first indexing best practices). Error pages and redirects are the classic m. site failures; Google named mobile errors, a blocked mobile site and redirects to the home page as the main problems on sites that still didn't work in 2023 (Search Central Blog, October 2023).

How to check your own site

Fifteen minutes, for your home page and each page that brings calls.

  1. Open the page on your phone and on a computer, side by side. Every service, price, photo, review and form on desktop should exist on the phone, even if it's folded into a menu or accordion.
  2. Tap nothing, then look again. Anything that only appears after a tap and loads new content is a gap risk.
  3. Run URL Inspection in Search Console. Google points to it to check "that the content is visible on the rendered page (the rendered page is how Google sees your page)" (Mobile-first indexing best practices). Search the rendered code for a sentence from each section. See Google Search Console for a small business if you haven't used it.
  4. If you have an m. site, open a few inner pages on your phone. Each one should land on its own mobile page, not the home page or an error.

If you run an m. site or dynamic serving and keep finding gaps, moving to a responsive theme ends the double upkeep. Treat it as a redesign: keep the same URLs and content, or see why traffic drops after a redesign.

Does being mobile-friendly boost rankings?

Less than most articles claim. Indexing is the big deal: missing content can't rank at all. Layout polish is smaller. Google uses Core Web Vitals (its speed and stability measures) in ranking, but says:

"Beyond Core Web Vitals, other page experience aspects don't directly help your website rank higher in search results." (Google Search Central: Understanding page experience)

The same page says Google "always seeks to show the most relevant content, even if the page experience is sub-par." A cramped phone layout costs you calls before it costs you rankings. For speed, see Core Web Vitals and website speed.

Example

Illustrative cases with invented round numbers.

A roofer with an old m. site (US dollars)

The desktop site has 12 service and city pages. On phones, every one redirects to m.example.com's home page, so Google indexes one page instead of 12. A $3,000 move to a responsive theme with the same URLs lets Google index the inner pages again.

A physiotherapy clinic hiding its prices (Canadian dollars)

The builder's "hide on mobile" switch removed the price table to shorten the phone page. URL Inspection's rendered page has no prices, so searches for "physio assessment cost" never match. The clinic puts the table in an accordion; an extra C$90 booking a week covers the hour it took.

A cleaning company with "Load more reviews"

The page shows 3 reviews; 40 more load on a tap. Google may never read the 40. The owner shows 10 on the page and links to the full list.

FAQ

Do I need a separate mobile site?

No. Google strongly recommends a mobile version of your content and prefers responsive design, which needs no second site (Mobile-first indexing best practices).

Does Google still crawl with a desktop bot?

Rarely. Since July 5, 2024 it indexes with its smartphone crawler; the desktop one is sometimes used for product listings and Google for Jobs (Search Central Blog, June 2024).

Is content in accordions or tabs indexed?

Yes. Google suggests accordions or tabs to save space on mobile, as long as the content matches desktop (Mobile-first indexing best practices).

Will switching to responsive design raise my rankings?

Not by itself. It makes sure Google sees all your content; Google still ranks the most relevant page, even with a poor experience (Understanding page experience).

Different for you?

Keep learning

NextMobile User Experience and SEO: What Google MeasuresWhich parts of mobile user experience Google really uses to rank pages, which are myths, and where a small business should spend its fixing time.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Mobile site and mobile-first indexing best practices
  2. Google Search Central Blog: Mobile-indexing-vLast-final-final.doc (June 3, 2024)
  3. Google Search Central Blog: Mobile-first indexing has landed (October 31, 2023)
  4. Google Search Central Blog: Mobile-First Indexing by default for new domains (May 28, 2019)
  5. Google Search Central Blog: Mobile-first indexing (November 4, 2016)
  6. Google Search Central: Understanding page experience in Google Search results
  7. web.dev: Responsive web design basics