Should you really wait for Google to switch your site to mobile-first indexing?

Why are not all sites yet using mobile-first indexing?

Google began the gradual rollout of mobile-first indexing several years ago, but contrary to popular belief, the migration is not automatic for the entire web. Some sites remain indexed on their desktop version, and it is Google that decides on a case-by-case basis when it is appropriate to switch.

As long as a site has not been migrated, Google's bots prioritize the crawling of the desktop version. This results in a significantly higher volume of desktop Googlebot crawls compared to mobile in the server logs. This imbalance is not a bug; it simply reflects the indexing mode still active for that site.

How can I tell if my site is ready for the switch?

The key question is not when Google will migrate your site, but to check if your mobile version is equivalent to the desktop. Google will only switch a site if it believes that the mobile version offers a complete and indexable experience.

In practical terms, this means: same visible textual content, same structured tags (title, meta, Hn), same internal linking, same images with their alt attributes. If your mobile site hides entire sections, truncates text, or excessively simplifies navigation, Google will wait for you to correct these discrepancies before migrating.

What happens if Google switches a poorly prepared site?

If Google decides to switch a site to mobile-first while the mobile version is underwhelming, the consequences can be severe: loss of rankings for keywords indexed through content missing from mobile, disappearance of orphan pages on the mobile side, dilution of internal PageRank if the mobile internal linking is incomplete.

Google typically sends a message in Search Console to warn of the impending migration, but this notice is often short. It is better to anticipate by regularly auditing the desktop/mobile parity, especially for e-commerce or editorial sites with historically lighter mobile versions.

• Mobile-first indexing is not automatic: Google migrates sites on a case-by-case basis, depending on desktop/mobile parity criteria.
• A non-migrated site will see more desktop crawl: this is normal as long as indexing remains based on the desktop version.
• Preparation is essential: ensure that the mobile site offers the same content, structure, and linking as the desktop.
• Search Console alerts of migration: monitor notifications to anticipate the switch and correct any remaining blocking points.
• A poorly prepared migration can degrade rankings: absence of mobile content = loss of visibility on related queries.

Is this gradual approach consistent with what we observe in the field?

Yes, completely. In recent audits, we still find sites with a desktop/mobile crawl ratio of 80/20, or even more skewed. These sites receive a message in Search Console indicating that they are "not yet ready" for mobile-first, often due to content hidden in accordions, poorly implemented lazy loading, or desktop canonicals pointing to themselves instead of to the mobile version.

Google has clearly slowed the pace of migration after noticing massive ranking regressions on sites that transitioned too early. The current caution is the result of past errors, and it's a good thing for SEOs: it gives us time to correct inconsistencies.

What are the gray areas in this statement?

Google does not specify which technical criteria actually trigger migration. We know that content parity is required, but what about mobile Core Web Vitals? A good mobile score on PageSpeed Insights? [To be checked]: no official threshold has been communicated, and we observe migrations for sites with poor mobile performance.

Another ambiguity: the issue of JavaScript on mobile. If your mobile site relies on complex JS rendering and content appears only after hydration, will Google always wait for the full rendering before validating parity? In some tests, the answer is no, which can lead to migrations with "invisible" mobile content for Googlebot.

In what cases does this rule not apply?

Sites with pure responsive design (one URL, the same HTML for desktop and mobile) are theoretically already ready for mobile-first. But beware: even in responsive design, if CSS blocks are hidden only on mobile (display:none), Google may consider this content as absent and postpone migration.

For sites with separate mobile/desktop URLs (m.site.com), the situation is more complex. Google must confirm that the canonicals and alternates are properly cross-referenced, that the content is strictly equivalent, and that the internal linking does not create orphans on mobile. This is often where the issues arise, causing sites to remain stuck in desktop indexing for months.

How can I concretely check if my site is ready for migration?

The first step: compare the source HTML of your key pages between desktop and mobile. Not the visual rendering, the raw code. Use a user-agent switcher or tools like Screaming Frog in mobile mode to crawl your site as Googlebot Smartphone would.

Check that the title tags, meta descriptions, Hn tags, and the main textual content are strictly identical. Track hidden content in CSS (display:none, visibility:hidden) that may be absent on mobile. Analyze the internal linking: a link present on desktop must also be present on mobile, otherwise you create potential orphans.

What errors should be avoided before switching to mobile-first?

The classic mistake: lightening the mobile version for performance reasons by removing blocks of text, images, or links. Google will index this reduced content, and your positions will follow. If you need to optimize mobile performance, do it through well-implemented lazy loading (with preload of critical images) and compression, not by truncating information.

Another pitfall: mobile pop-ups and interstitials. If they hide essential content upon loading, Google may consider this content inaccessible. Use discreet formats (banners, slide-ins) or trigger your interstitials after scrolling, never on first display.

What should I do if Google has already migrated my site and I notice losses?

The first action: identify the pages with traffic loss via Search Console (Performance tab, filter by page). Compare the HTML mobile of these pages with their desktop equivalent before migration (via Archive.org if needed). Look for missing content, altered Hn tags, lost internal links.

If you identify discrepancies, correct them immediately on the mobile side and force a recrawl via Search Console (URL Inspection > Request indexing). Google takes a few days to weeks to reevaluate the page, but rankings will recover if parity is restored.

• Crawl your site with a mobile user-agent (Screaming Frog, Botify, OnCrawl) to detect content discrepancies.
• Compare the source HTML of key pages between desktop and mobile, not just the visual rendering.
• Ensure the mobile internal linking is complete and does not create orphans.
• Analyze server logs to measure the Googlebot desktop/mobile ratio and anticipate migration.
• Test mobile rendering via the URL Inspection tool in Search Console to validate what Google actually sees.
• Monitor messages in Search Console regarding preparation for mobile-first indexing.