Is it true that all sites indexed after July 2019 default to Mobile-First Indexing?

What is Mobile-First Indexing and why is this date crucial?

Mobile-First Indexing (MFI) means that Google uses the mobile version of a site to index and rank pages, even for desktop users. Before this switch, the index relied on the desktop version — which caused issues when mobile content was truncated or different.

Google gradually rolled out MFI starting in 2018. By mid-2019, most sites had migrated. This statement sets a threshold: any new site discovered after July 2019 goes directly into MFI, with no transitional phase. No initial desktop crawl, no waiting — mobile becomes the default mode.

Why does Search Console sometimes show an incorrect status?

The Google Search Console interface may indicate that the site is being crawled by desktop Googlebot when, in fact, the mobile agent is visiting the pages. Google describes this as a display bug in the tool — actual indexing is unaffected, only the GSC notification is incorrect.

Specifically, a site launched after the cutoff date may receive a reassuring message "Your site is being crawled in desktop" while logs show Googlebot smartphone everywhere. This divergence creates confusion: SEOs reflexively check GSC, but the tool sometimes misrepresents this critical parameter.

How can you detect the actual indexing mode of your site?

The reliable method remains server log analysis. Look for Googlebot user-agents: if you see Googlebot smartphone in majority and little or no Googlebot desktop, the site is in MFI. The absence of a desktop bot on a recent site confirms that Google is only crawling the mobile version.

Another indicator: inspect a URL in GSC and check the declared user-agent for the last crawl. But beware, this data can also be delayed or contradictory with the logs. In case of doubt, logs are the source of truth — GSC is a dashboard, not a real-time crawl mirror.

• Sites created after July 2019: default mobile indexing, with no prior desktop phase.
• GSC Bug: the interface might display an incorrect desktop status — never blindly trust the notification.
• Server Logs: the only reliable method to confirm the user-agent actually used by Google.
• Residual Desktop Crawl: may persist for specific tasks (indexing assets, tests), but main indexing is mobile.
• Practical Consequence: any MFI diagnosis must cross-reference GSC and logs — one tool alone is not sufficient.

Is this statement consistent with real-world observations?

Yes, overall. The recently launched sites I’ve audited show a clear dominance of Googlebot smartphone crawling, often exclusively. Logs confirm: zero desktop visits or sporadic ones not related to HTML content indexing.

But caution — the July 2019 date is not an absolute cutoff. Some expired domains that were relaunched, or sites migrated with complicated redirects, sometimes experienced a mixed crawl phase for a few weeks. Google seems hesitant when a domain's history is ambiguous. [To verify]: we lack official data on the treatment of recycled domains or complex DNS migrations.

Is the GSC bug really trivial or does it hide a deeper issue?

Labeling this a mere "display bug" minimizes the impact. For an SEO auditing a client site, seeing "desktop Googlebot" in GSC immediately raises an alarm: mobile content truncated? missing structured data in mobile? The bug leads to misleading diagnostics and wastes time.

More worryingly: if GSC lies about this point, what else may it be inaccurate about? Trust in the tool erodes. Google should have fixed this bug a long time ago — its persistence suggests either a lack of priority or a complex backend architecture that makes the correction non-trivial. Frankly, for such a central tool as GSC, this is borderline unacceptable.

In which cases might a recent site escape the default MFI?

Theoretically none, according to Google. Practically? A few edge cases emerge. Sites in total noindex at launch, then opened to indexing later, may experience initial desktop crawl if the noindex was lifted gradually or partially. [To verify]: no official documentation specifically addresses this scenario.

Sites behind strict authentication or complex paywalls may also exhibit atypical crawl patterns — Google may attempt a desktop crawl to check consistency between versions. But in these cases, the final indexing remains mobile. The desktop bot, when it appears, serves auxiliary verification purposes, not the main index.

How can you concretely check your site's indexing mode?

First step: analyze your server logs over a period of 7 to 14 days. Filter Googlebot user-agents and count smartphone vs desktop occurrences. If the smartphone accounts for more than 90% of hits on HTML URLs, you are confirmed in MFI.

Second step: use the URL inspection tool in GSC, but with caution. Check the declared user-agent for the last crawl of a representative page. If GSC says "desktop" but your logs show "smartphone", you are facing the bug — trust the logs, not the interface.

What priority adjustments should be made if the site is in MFI?

Ensure that the mobile content is strictly identical to the desktop — text, title/meta tags, structured data, images with alt attributes. Any divergence hits visibility hard. Well-designed responsive sites have no issues; it's the separated mobile versions (m.example.com) or stripped-down mobile themes that struggle.

Check that Googlebot smartphone has access to all resources: CSS, JS, images. An overly restrictive robots.txt or a misconfigured user-agent blocking can block the mobile bot while the desktop passed. Test with Google's mobile-friendly test tool and GSC’s robots.txt tester.

What to do if GSC shows a status inconsistent with the logs?

Ignore the GSC display and work based on the actual logs. Document the divergence internally to prevent the team from panicking or launching unnecessary changes. If the bug persists and creates confusion, report it via the GSC forum or Twitter @googlesearchc — but don’t hold your breath for a quick fix.

In the meantime, focus on what matters: optimizing the mobile version. That's the one that counts for indexing. Any SEO technical audit must now prioritize mobile — the desktop version is just a user comfort for a shrinking minority of visitors.

• Extract and analyze server logs over 7-14 days to identify the dominant Googlebot user-agent.
• Verify that content, structured data, and tags are identical between mobile and desktop.
• Test resource accessibility (CSS/JS) for Googlebot smartphone via GSC and robots.txt tester.
• Cross-reference GSC data (URL inspection) with actual logs to detect inconsistencies.
• Document any GSC display bug internally and work based on logs, not the interface.
• Prioritize mobile optimization in all SEO audits — this is the version indexed by default.