Are separate mobile URLs (m.example.com) still a viable SEO option?

Why clarify about separate mobile URLs now?

This statement from John Mueller addresses a recurring concern: many SEOs believe that separate mobile URLs (like m.example.com) have become obsolete or penalized. This is false. Google treats three configurations as valid: responsive (a single URL), dynamic serving (one URL, different content based on user-agent), and separate URLs with appropriate tags.

Responsive design predominates today because it is easier to maintain and avoids markup errors. However, historical sites that have retained an m.example.com architecture are not technically at fault as long as the bidirectionality of tags is respected.

What does 'appropriate canonical and alternate tags' mean practically?

For each desktop page (www.example.com/page), you must add a rel="alternate" media="only screen and (max-width: 640px)" tag pointing to m.example.com/page. Conversely, each mobile page must have a canonical pointing to the desktop version.

This symmetry allows Google to understand that both URLs serve the same content. If only one direction is configured, the engine may ignore the annotation or index both versions separately — which dilutes signals and creates duplicates.

Why does Google recommend a single version: for whom?

The recommendation to simplify with a single URL primarily targets new sites or those migrating. Managing two distinct URLs multiplies friction points: server redirects, testing, shared crawl budget, and risks of tag errors.

For an e-commerce site with thousands of listings, maintaining two perfectly synchronized versions becomes an operational nightmare. Conversely, some legacy sites with a stable m.example.com architecture for years may benefit from keeping the existing setup if everything is functioning — especially if the CDN infrastructure relies on it.

• Separate URLs (m.example.com) remain technically supported by Google if the canonical and alternate tags are correct.
• Responsive (a single URL) simplifies maintenance and reduces the risks of markup errors.
• No penalties are imposed on sites using well-configured separate mobile URLs.
• Tag bidirectionality (desktop → mobile and mobile → desktop) is mandatory to avoid duplicates.
• Google does not force migration to a single URL, but recommends it for new projects.

Is this statement consistent with observed practices on the ground?

Yes, tests show that Google continues to correctly index and rank sites with separate URLs if the markup is clean. We even observe some major e-commerce sites maintaining this architecture without visible positioning issues.

However — and this is where it gets tricky — most m.example.com implementations have configuration errors. Missing alternate tags on some pages, incorrect canonicals, 302 redirects instead of serving mobile content, and inconsistencies in URL parameters. These errors create duplicates or hinder proper mobile-first indexing.

What nuances should be added to this official position?

Google says 'supported,' not 'recommended.' This is a crucial distinction. Supported means that the engine can technically manage this configuration — not that it is optimal for all contexts. For a new site launched today, choosing separate URLs would be a strategic error unless under very specific technical constraints.

The other nuance: Mueller talks about 'simplifying', but does not mention the impact on the crawl budget. Two versions of a site mean potentially twice as many pages to crawl. On a large site with millions of URLs, this can slow the discovery of new pages or the consideration of changes. [To be verified] on very large sites if the indexing velocity differs.

In what cases does this configuration remain relevant despite everything?

Three legitimate scenarios. First, legacy sites with CDN infrastructure where m.example.com points to geographically optimized servers different from desktop — refactoring would cost more than maintaining the existing setup.

Second, some sites have radically different user experiences between desktop and mobile (web applications like PWAs served from m.example.com with a distinct tech stack). Third, regulatory or organizational constraints in certain groups where desktop and mobile teams are siloed.

Should I migrate if my site already uses separate mobile URLs?

Not necessarily. Start with a current state audit. Use Google Search Console to check for mobile indexing errors, particularly signals like 'Page with redirect' or 'Submitted URL marked noindex.' If your metrics are stable (organic traffic, positions, indexing rate), changing the architecture carries more risks than benefits.

On the other hand, if you observe recurring duplicate content, fluctuations in indexing, or if your tech team is making deployment errors across both versions, plan a migration to responsive. It’s a heavy undertaking, but it will simplify everything afterward — mandatory 301 redirects, close monitoring for 3-6 months.

How can I check if the canonical and alternate tags are correct?

Crawl your site with Screaming Frog or Oncrawl in mobile-first mode. Export the mobile URLs (m.example.com) and ensure that 100% have a canonical pointing to the desktop version. Then, crawl the desktop version and verify that each page indeed has its alternate pointing to the mobile equivalent.

Manually test a dozen pairs of URLs using the Search Console URL inspection tool. Submit the mobile version and see which canonical Google actually retains. If it’s not the one you defined, you have a configuration problem (often from redirects interfering or conflicting canonicals).

What critical errors should be avoided with this architecture?

First error: temporary 302 redirects between desktop and mobile based on user-agent. Google follows these redirects but may index the wrong version. If you detect the device on the server side, serve the appropriate content directly, without a visible redirect.

Second error: alternate tags with incorrect media query. If you write media="handheld" instead of media="only screen and (max-width: 640px)", Google may ignore the annotation. Third error: forgetting to synchronize content. If your mobile version lacks sections present on desktop (for performance reasons), Google may consider the content different and not associate them.

• Audit the current state in Search Console before any migration decision.
• Check bidirectionality of canonical/alternate tags on a representative sample of URLs.
• Crawl both versions (desktop and mobile) to detect markup inconsistencies.
• Test actual indexing with the URL inspection tool on key pages.
• Avoid 302 redirects based on user-agent: serve the correct content directly.
• Synchronize content between the two versions to avoid material discrepancies.