Should you really create a mobile version if Google indexes the desktop site?

Does Google really index a desktop-only site for mobile?

Yes, and this is an important confirmation. When no mobile version is detected, Googlebot uses the desktop version for mobile ranking. This is not an ideal scenario, but it is technically possible.

The algorithm does not systematically discriminate against a site for lacking responsiveness. It will simply evaluate this desktop version with its mobile criteria. The result: likely penalties on Core Web Vitals, degraded user experience, and skyrocketed bounce rates.

What’s the significance of this clarification on 404 redirects?

Because some sites block or redirect mobile users to error pages. This is a fatal error called out by Mueller.

If Googlebot mobile encounters a 404 while the content exists on desktop, Google will consider that the page simply does not exist. Your content disappears from the mobile index. Worse: this creates a gap between desktop and mobile index that completely disrupts SEO.

What’s the logic behind this tolerance from Google?

Google does not want to massively exclude sites that have not yet migrated to responsive design or that operate in specific niches (ultra-technical B2B, intranets, desktop-first tools). The priority remains access to content.

However, tolerating does not mean recommending. The algorithm will penalize through other means: catastrophic mobile loading speed, disastrous interactivity, unreadable text without zoom. You remain indexed, but buried on page 5.

• Google indexes the desktop version even for mobile if no alternative exists
• Mobile redirects to 404 pages simply kill your mobile SEO
• A desktop-only site is technically indexable but suffers massive indirect penalties on mobile UX
• This tolerance is a safety net, not a permission to neglect mobile

Is this statement consistent with what we observe in the field?

Absolutely. I have audited desktop-only sites that still appear in mobile SERPs. Their positioning is disastrous, but they are technically indexed. Google is not lying about this.

The real issue is that Mueller does not quantify the impact. Saying "we still index it" without specifying at what cost in terms of ranking is a half-truth. Field data shows an average drop of 40 to 70% in organic mobile traffic for a non-responsive site compared to a mobile-friendly competitor in the same niche. [To verify]: Google does not publish any official figures on this indirect penalty.

What nuances should be added to this rule?

Google’s tolerance primarily applies to B2B niche sites or ultra-specialized content where mobile accounts for less than 10% of total traffic. If your audience is 60% mobile (like 80% of the web), this “tolerance” won’t save you.

Another nuance: Mueller discusses indexing, not performance in results. A desktop-only site will be indexed but systematically outperformed by a mobile-first competitor with equal authority. The algorithm massively favors responsive sites since the Mobile-First Index.

In what cases does this rule not provide protection at all?

If you have set up user-agent redirects sending mobile users to a subdomain m.example.com that no longer exists, you fall exactly into the trap that Mueller warns against. The mobile 404 kills your indexing.

Another critical case: sites that block Googlebot mobile via robots.txt or meta robots. There, even with a perfect desktop site, Google cannot index anything for mobile. I’ve seen sites lose 80% of their traffic due to a misconfigured robots.txt that only blocked mobile user-agents.

What should I do concretely if my site is desktop-only?

First priority: ensure that mobile users can access the content. Test with a real mobile device, not just Chrome’s responsive mode. Load all your strategic pages and verify that none redirect to a 404 or a "desktop version only" message.

Second step: analyze your server logs to identify HTTP 404 codes sent to mobile user-agents. If you find any, this is an immediate alarm signal. Fix it before Google deindexes those pages.

What mistakes should be avoided at all costs?

Never set up conditional redirects based on the mobile user-agent to non-existent pages. This is the nightmare scenario that Mueller warns against. If you redirect, make sure that the destination page exists and contains the same content.

Also, avoid blocking critical CSS/JS resources for mobile in your robots.txt. Google needs to render the complete page to assess the mobile experience. If you block rendering, you hinder proper indexing.

How can I check if my site complies with this logic?

Use Google Search Console, in the "Page Experience" section. Check for mobile usability errors: text too small, clickable elements too close, viewport not configured. These errors indicate that Google can see your site but is penalizing it.

Run a crawl with Screaming Frog simulating a mobile user-agent (iPhone, Android). Compare the HTTP codes obtained with those from the desktop crawl. Any divergence (mobile 404 vs desktop 200) is a critical red flag.

• Manually test mobile access to all strategic pages (no 404, no blocking)
• Analyze server logs for 404s returned to mobile user-agents
• Check in robots.txt that no critical (CSS/JS) resources are blocked for Googlebot mobile
• Use Google Search Console to identify mobile usability errors
• Crawl the site with a mobile user-agent and compare HTTP codes with the desktop crawl
• Plan a responsive migration if mobile traffic exceeds 30% of total traffic