Only Desktop

Element Code: OR-012

What "Only Desktop" actually means

This check flags a URL that earns organic search traffic from desktop devices while getting essentially nothing from mobile. Not "a bit less on mobile," which is normal for some B2B or tooling queries. I mean a clean zero, or a rounding error, against a healthy desktop line in Search Console. That asymmetry is rarely a coincidence, and it is almost never a good sign.

Google switched every site over to mobile-first indexing back in 2023, per its own crawling documentation. What that means in practice: the Googlebot Smartphone user agent is the version that decides what your page contains, how it ranks, and whether it deserves to show at all. If the mobile rendering of a page is broken, blocked, stripped of content, or unreachable, then the version Google actually judges is the weak one. Desktop traffic can limp along on legacy signals for a while, but the trend line only points one direction.

Why a mobile-blind page is a ranking problem

Search Console splits performance by device, and that split is your smoke detector. When desktop and mobile diverge this hard, one of a short list of things is usually true, and each one hurts rankings on both devices over time, not just phones.

• The mobile page renders differently. A separate m-dot URL, a device-sniffing template, or a JavaScript bundle that fails on mobile can serve Google a thinner page than desktop users see.
• Content is hidden or absent on mobile. If the main copy lives inside a tab, an accordion that never loads, or a component that only mounts on wide viewports, Googlebot Smartphone may never index it.
• A viewport or usability failure. Missing viewport meta tag, tap targets too close, content wider than the screen. Google can still index the page but treats the mobile experience as poor.
• The page is genuinely a desktop-only query. Rare, but real. Some tooling, spreadsheet, or enterprise-software queries skew heavily to desktop. This is the one benign explanation, and you confirm it before you relax.

How to diagnose it

Do not guess. Walk the page the way Google does and the cause shows itself fast.

1. Confirm the gap in Search Console. Open Performance, filter to the URL, add the Device breakdown. Verify it is truly zero mobile clicks and impressions, not just low. Impressions matter more than clicks here: zero mobile impressions means Google is not even ranking the mobile page.
2. Run the URL Inspection tool. Inspect the live URL, then view the rendered HTML and screenshot from the crawled (mobile) version. If the content you expect is missing from that render, you found your problem.
3. Crawl with Screaming Frog as Googlebot Smartphone. Set the user agent to Googlebot Smartphone, enable JavaScript rendering, and compare the rendered word count and links against a desktop crawl of the same URLs. A large delta is the tell.
4. Check the viewport and resources. Confirm a <meta name="viewport"> tag exists and that no CSS or JS the mobile layout depends on is blocked by robots.txt.
5. Read the server logs. Filter for the Googlebot Smartphone user agent. If it is hitting a redirect, a 4xx, or a stripped template that desktop never sees, the logs will show it plainly.

Detection tools at a glance

How to fix it

The fix follows the cause. Match yours:

• Content hidden on mobile: ensure the primary copy is in the initial HTML or renders on mobile without user interaction. Tabs and accordions are fine for Google as long as the content is present in the DOM, but a component that only mounts above a certain breakpoint is not.
• Blocked resources: remove robots.txt rules that block the CSS and JS the mobile layout needs. Google has to render the page to judge it.
• Broken responsive layout: add the viewport meta tag, fix content that overflows the screen, and space out tap targets.
• Separate m-dot site: confirm the mobile URLs carry the same content, structured data, and internal links as desktop. Parity is the whole game with separate mobile URLs.
• Legitimately desktop-skewed query: document it, note the intent, and stop treating it as a bug. Then move on.

DO vs DON'T

What "good" looks like

A healthy page shows mobile impressions and clicks that roughly track its query intent, not a suspicious flatline. The mobile render, seen through URL Inspection, contains the same headings, body copy, links, and structured data as desktop. Nothing the layout needs is blocked in robots.txt. When you crawl the URL as Googlebot Smartphone in Screaming Frog, the word count lands within spitting distance of the desktop crawl. That is the target: one page, two crawlers, the same content.

FAQ