Why does Search Console still show 'PC Googlebot' on recent sites when Mobile-First Index is supposed to be the standard?

What does this announcement really change for sites launched after July 2019?

This statement from Takeaki Kanaya clarifies a recurring point of friction among SEO practitioners: the gap between what Google announces and what Search Console displays. Since July 2019, Google has directly switched all new sites to Mobile-First Index, without a transitional period.

In practical terms, this means that if you launch a site today, Googlebot will immediately crawl and index the mobile version of your pages. No observation phase, no gradual migration. Mobile is your canonical version in the eyes of Google, period.

Why does Search Console still show 'PC Googlebot' in some cases?

The Search Console interface clearly suffers from display bugs that create unnecessary confusion. Recent sites, theoretically on Mobile-First since their initial indexing, sometimes show 'PC Googlebot' in the reports.

This gap between technical reality and interface display leads many SEOs to panic unnecessarily. Yet according to Kanaya, this display is a visual artifact, not an alert signal regarding your actual indexing. The issue lies within the reporting system of Search Console, not in the crawler's behavior.

How can I reliably check which Googlebot is crawling my site?

The only reliable source of truth remains server log analysis. By examining your logs, you can precisely identify which user-agent is hitting your pages: Googlebot Desktop or Googlebot Smartphone.

If your logs show a predominance of Googlebot Smartphone (with the characteristic mobile user-agent), you are indeed on Mobile-First, regardless of what the Search Console interface says. It's the ground reality that matters, not the dashboard. Therefore, log verification becomes an essential practice for any serious audit.

• All sites indexed since July 2019 automatically switch to Mobile-First Index from their first indexing
• The 'PC Googlebot' display in Search Console may be a interface bug, not a reflection of the technical reality
• Server logs are the only reliable method to confirm which Googlebot is actually crawling your pages
• No transitional period or gradual migration for new sites: mobile is immediately prioritized
• The confusion stems from a discrepancy between the actual crawler behavior and the Search Console reporting system

Is this statement consistent with field observations?

Yes and no. In principle, field observations confirm that recent sites are mostly crawled by Googlebot Smartphone. However, the reality is more nuanced than this somewhat categorical statement suggests.

We regularly observe mixed crawling on recent sites: Googlebot Smartphone predominates, but Googlebot Desktop continues to sporadically visit, especially certain resources (CSS, JS) or specific pages. Saying that it's 100% mobile since July 2019 simplifies a functioning that remains more hybrid than suggested. [To verify] on your own crawl traffic.

Is the Search Console display bug really trivial?

No, it is not. Minimizing this bug as a mere cosmetic issue underestimates its operational impact. Dozens of client sites panic each month upon seeing 'PC Googlebot' displayed even though they have optimized their mobile versions.

This bug erodes confidence in Search Console as a management tool. If the interface lies about such a fundamental point as the type of crawler, what other metrics are distorted? This uncertainty compels experienced SEOs to systematically double-check via logs, which should be an exception, not the norm.

Under what circumstances might this rule not apply strictly?

Some technical contexts create exceptions or atypical behaviors. Sites with geographical cloaking, conditional redirects based on user-agent, or exotic server configurations may disrupt expected crawl behavior.

Similarly, sites that serve a deliberately limited or blocked mobile version (via robots.txt or meta robots on mobile) may force Google to return seeking content on the desktop version. In such cases, you might indeed see dominant desktop crawling, even on a recent site. But this is then a configuration issue, not an exception to the Mobile-First rule.

What should I concretely check on a recent site?

The first essential step: analyze your server logs over at least the last 30 days. Identify the distribution of Googlebot Smartphone vs. Googlebot Desktop. If mobile accounts for less than 80% of the crawl on a site indexed after July 2019, dig deeper.

Next, audit the content parity between your desktop and mobile versions. Google indexes your mobile, so any content absent from the mobile version is invisible to the engine. Structured data, text, images, internal links: everything must be present and accessible on mobile. A lighter mobile version directly hampers your performance.

What mistakes should I avoid in light of this statement?

Never take Search Console at face value regarding the type of crawler. The classic mistake is to see 'PC Googlebot' displayed and panic, re-optimizing for desktop, while the mobile remains your absolute priority.

Another common pitfall: believing that Mobile-First Index means 'mobile-only'. Google continues to crawl the desktop version for certain checks, particularly for technical resources (JS, CSS) or cross-device consistency. Do not block Googlebot Desktop in your robots.txt, even on a 100% mobile-first site.

How to ensure compliance for a recent site that may have issues?

If your logs reveal abnormal desktop crawling, start with a mobile/desktop parity audit. Use tools like Screaming Frog in mobile vs. desktop mode to identify gaps in content, links, structured data.

Then correct any potential blocks in your mobile robots.txt, check that your mobile Core Web Vitals are in the green (LCP < 2.5s, CLS < 0.1, INP < 200ms), and ensure your responsive design does not hide critical content via poorly thought-out CSS display:none. If you find complex discrepancies between desktop and mobile versions, or if the audit reveals structural indexing issues, it may be wise to get assistance from an SEO agency specialized in these technical challenges, which can offer you a personalized action plan suitable for your context.

• Analyze server logs over at least 30 days to identify the dominant user-agent
• Check strict content parity between mobile and desktop versions (text, images, links, structured data)
• Audit mobile Core Web Vitals and correct metrics out of the green zone
• Never block Googlebot Desktop in robots.txt, even in strict Mobile-First
• Test mobile rendering with the Search Console URL inspection tool AND a mobile Screaming Frog crawl
• Document discrepancies between Search Console display and log reality to track the bug's evolution