Should you really redirect mobile users to the homepage when the page isn't available in responsive format?

Why does Google emphasize this seemingly obvious point?

The situation in question pertains to dual configuration sites: one desktop version (www.site.com) and a separate mobile version (m.site.com). When a mobile user lands on a desktop URL that has no mobile equivalent, some sites automatically redirect to the mobile homepage.

This reflex, which seems logical, creates a sharp disruption in the user journey. The user is searching for a specific product, clicks on a result, and ends up on the homepage. They have to restart their navigation from scratch. Google considers this experience problematic enough to officially advise against it.

The recommended alternative is to serve the desktop version as is to mobile users. Certainly, the ergonomics won't be optimal — small text, unsuitable navigation, manual zoom possible — but the user gains access to the content they were seeking.

What happens on the crawl and indexing side?

Googlebot mobile follows redirects like a real user. If every specific desktop URL redirects to the mobile homepage, the bot detects a structural inconsistency: dozens or hundreds of URLs all point to the same destination.

This pattern resembles a technical flaw or, worse, an attempt to hide content. The engine may then devalue the mobile site or ignore certain rel="alternate" annotations. Consistency between desktop and mobile versions becomes opaque.

In what technical context does this recommendation still apply?

Let's be frank: M-dot sites (m.site.com) are becoming obsolete. Responsive design has replaced this dual architecture for years. However, Google continues to publish guidelines on the topic because thousands of legacy sites are still operating on this model.

If you manage a recent site, this recommendation probably doesn't apply to you. However, if you're inheriting an old e-commerce site or a media portal launched before 2015, you may encounter this configuration. Automatic redirects to the mobile homepage are often hard-coded in .htaccess or in middleware.

• M-dot Architecture: two distinct sites, two structures, manual management of URL equivalences
• Default Redirects: when the mobile URL doesn’t exist, automatic redirect to m.site.com
• Negative UX Signal: the user loses the sought content, immediate bounce rate
• Google's Alternative: display the non-responsive desktop version instead of redirecting
• Edge Case: if the desktop page is completely unusable on mobile (Flash, heavy PDFs), redirecting to an explanatory page is still preferable to a blank screen

Does this statement really reflect observed on-ground practices?

Yes, and it is even a rule that Google has applied with consistency for years. Audits of M-dot sites consistently show that massive redirects to the mobile homepage degrade performance in Search Console: declining click-through rates, unindexed mobile pages, mismatched annotation errors.

What is more subtle is that Google doesn't directly penalize these redirects. The engine simply observes a user experience disruption that can be measured: low time spent, immediate returns to SERPs, lack of interaction. These behavioral signals are enough to demote the site without any manual filter intervening.

What nuances should be applied in real cases?

Google's recommendation assumes that the desktop version remains functionally usable on mobile. If your desktop page contains Flash, incompatible dropdown menus, or loads 8 MB of resources, displaying this version to a 4G user is worse than a redirect.

In these edge cases, it’s better to create a mobile interstitial page explaining that the content isn't available in mobile format and offering a link to the desktop version. This transparent approach is better than a harsh landing on the homepage. [To verify]: Google has never published quantified data on the actual impact of these redirects vs. desktop display on mobile ranking.

In what cases does this rule absolutely not apply?

If your site is in responsive design (one URL, CSS/JS adaptation according to viewport), this issue simply doesn't exist. The URL is the same regardless of the device, meaning no possible redirection.

Similarly, for Dynamic Serving sites (same URL, different HTML content depending on User-Agent): it's the server that decides what to display, with no redirects on the client side. Google's recommendation strictly concerns M-dot architectures with distinct URLs.

What should I do if my site is still in M-dot architecture?

First step: audit existing redirects. Take 50 random desktop URLs, test them with a mobile User-Agent (Chrome DevTools, responsive mode). If more than 10% redirect to the mobile homepage, you have a problem.

Next, modify the redirect logic. The rule should be: if a mobile equivalent exists, redirect to it; otherwise, serve the desktop version as is. Technically, this involves maintaining an up-to-date desktop URL ↔ mobile URL mapping or completely disabling the default redirect.

What critical mistakes should be avoided during correction?

Do not implement a complex conditional redirect that tests for the existence of the mobile page in real-time. This adds server latency and can create timeouts. It’s better to generate a static match file and consult it in memory.

Avoid simply removing all redirects without warning: if mobile URLs exist and function, removing them disrupts the experience of users who have bookmarked m.site.com. The clean solution is a full migration to responsive, not a fix of .htaccess rules.

How can I check if the configuration is correct after correction?

Use the Search Console, mobile Coverage section. Google explicitly reports problematic mobile redirects and desktop pages served to mobile. If you see warnings like "Incorrect Redirect" or "Page not available on mobile", that’s where it is.

Also test with a mobile crawler (Screaming Frog configured as Googlebot Smartphone). Verify that desktop URLs without a mobile equivalent return a 200 code (not 302 or 301) when crawled with a mobile User-Agent. The HTML content must be that of the desktop version, possibly with a viewport meta tag to improve rendering.

• Audit current mobile redirects on a representative sample of URLs
• Disable default redirects to the mobile homepage if no equivalent exists
• Maintain an accurate mapping of desktop ↔ mobile matches
• Check HTTP codes returned for mobile User-Agent (200 expected, not 301/302)
• Monitor Search Console for redirect errors reported by Google
• Plan a migration to responsive design if the M-dot site becomes unmanageable