Should you prioritize user agent or viewport detection for your separate mobile versions?

What is the reason behind Google's distinction between user agent and viewport?

Detection via user agent relies on analyzing the string sent by the browser or bot during the HTTP request. It is a server-side method: the site identifies the device (mobile, desktop, bot) before even sending the HTML. Google accepts this without issue for serving separate versions — typically m.site.com versus www.site.com.

On the other hand, detection by viewport is based on the actual dimensions of the screen through CSS and JavaScript. The server sends the same HTML, but the display adapts dynamically. This is the logic of responsive design. Google prefers this approach because it better covers edge cases: tablets, foldables, resized windows, modified or spoofed user agents.

Does this mean that the user agent is obsolete for SEO?

No. Martin Splitt clearly states: the user agent is sufficient for Google. If your legacy infrastructure relies on separate mobile URLs detected by user agent, you are not penalized. Googlebot mobile identifies correctly, the server redirects or serves the right version, and everything works.

The issue is not strictly SEO; it is UX. A user switching devices, moving from portrait to landscape, or using a browser with an atypical user agent risks landing on the wrong version. The viewport, on the other hand, adjusts in real-time. This is why Google promotes this method “in general” — not for its algorithm, but for your users.

In what context does this statement remain relevant today?

It mainly concerns legacy sites that still maintain separate mobile versions rather than a unified responsive design. These architectures still exist — major media outlets, legacy e-commerce, complex platforms where a complete redesign is not budgeted.

If you are in this situation, Google reassures you: continuing with the user agent will not break your mobile-first indexing. But it also reminds you that it is a compromise solution, not the optimum. The real target remains responsive or adaptive designs based on viewport.

• User agent: sufficient for Googlebot, but rigid in the face of user edge cases.
• Viewport: more flexible, better UX, generally recommended by Google.
• Separate architecture: still acceptable for SEO, but less robust than a unified responsive design.
• The choice depends on your existing infrastructure and your capacity for redesign.
• Google does not penalize the user agent; it simply indicates a more sustainable path.

Is this statement consistent with on-the-ground practices?

Yes, absolutely. We still see legacy news or e-commerce sites serving m.domain.com via user agent, and they rank without issues. Googlebot mobile identifies correctly, the server makes a 302 redirect or serves the right version directly, with no indexing issues observed.

What Martin Splitt does not explicitly state is that configuration errors remain frequent. Variants include forgetting the cross alternate/canonical tags, using a 301 redirect instead of a 302, or user agent detection that misses modern bots or tablets. In these cases, the viewport would have bypassed the problem — a single HTML, one set of canonicals.

What nuances should be added to this recommendation?

Google says “in general,” and that’s where it gets tricky. There are contexts where serving radically different HTML between mobile and desktop remains relevant — for instance, a mobile app that displays less content for performance reasons or specific touch usage.

In those cases, server-side user agent detection allows for precise control. The viewport assumes that the same DOM is visually adapted. If your mobile loads 50% fewer features, the viewport is not enough — the device must be accurately detected before sending the HTML. [To be verified]: Google has never detailed if a significant content delta between versions is accepted in mobile-first.

In what cases does this rule not apply?

If you are using a unified responsive design (one URL, one HTML, CSS adaptation), the user agent vs viewport question does not even arise — you are already on the path recommended by Google for years.

If you are serving dynamic server-side content (SSR with Next.js, Nuxt, etc.) and detecting viewport via CSS media queries, likewise: you are in the optimal case. Splitt's statement targets historical separate architectures, not modern stacks that are already responsive by default.

What practical steps should you take if you are still using the user agent?

First, ensure that your detection works for Googlebot mobile (user agent containing “Mobile”, “Android”, “iPhone”). Test with the URL Inspection tool in Search Console — mobile mode. If the correct version displays, you are covered for strict SEO.

Next, test with real devices: tablets, foldables, less common browsers. If some end up on the desktop version when they should see the mobile one, that’s where the viewport would have avoided the pitfall. In this case, assess the cost of migrating to a unified responsive design versus the current UX risk.

What errors should you avoid with separate mobile versions?

Never make a permanent 301 redirect between desktop and mobile. Use a 302 (or 307 if you want to be picky about HTTP method). Google must understand that both versions exist in parallel, not that one replaces the other.

Another classic trap: forgetting the cross rel="alternate" and rel="canonical" tags. The desktop page must point to the mobile one with <link rel="alternate" media="only screen and (max-width: 640px)" href="https:\/\/m.site.com\/page">, and the mobile must canonicalize back to the desktop with <link rel="canonical" href="https:\/\/www.site.com\/page">. Without this, Google may duplicate indexing or choose the wrong version.

How can you tell if a migration to viewport is necessary?

Analyze your mobile bounce rates and user journeys. If you notice users manually switching to the desktop version (link at the bottom of the page “View full site”), it’s a signal that the user agent detection is missing its target.

Also, look at your server logs: how many requests with a mobile user agent still end up on the desktop version (or vice versa)? If the volume is marginal, sticking with the user agent remains defensible. If it represents 5-10% of traffic, migration becomes worthwhile.

• Test user agent detection with the URL Inspection tool in Search Console in mobile mode.
• Check the presence and symmetry of rel="alternate" and rel="canonical" tags on all page pairs.
• Use 302 (temporary) redirects between versions, never 301.
• Audit server logs to identify instances of failing user agent detection.
• Evaluate the cost of a responsive redesign versus the current UX risk on atypical devices.
• If budget or technical complexity makes migration difficult, consider partnering with a specialized SEO agency to secure each step.
  The user agent remains technically valid for serving separate mobile versions to Google, but viewport detection offers superior robustness and user experience. If you maintain a separate architecture, focus on perfectly configuring cross tags and 302 redirects. If you consider a redesign, unified responsive design is the goal — but this transition requires sharp expertise to avoid traffic drops. In this case, relying on an experienced SEO agency ensures that every technical detail is mastered, from managing canonicals to tracking URL migrations.