Traffic Dropped on Mobile but Not Desktop: Six Device-Specific Causes to Check

Most people never segment by device, which is why this one hides so well. Total traffic falls, the site looks fine on the laptop it is being checked on, and the diagnosis goes off in the direction of algorithm updates.

The segmentation takes about thirty seconds. In Search Console Performance, open the Devices tab and compare mobile against desktop across your drop period. If one moved and the other did not, you have narrowed the problem enormously before doing anything else.

Why mobile-only drops are worse than they look

Google indexes the mobile version of your site. Not primarily, not mostly. It is the version that gets indexed, and the desktop version is largely irrelevant to what ranks.

That has a consequence people underestimate. If your mobile template omits content that your desktop template shows, that content does not exist as far as ranking is concerned. You can have a 3,000-word guide that Google treats as 400 words, because the rest sits in a section your mobile layout drops.

So a mobile-only decline is often not really about mobile users at all. It is about Google reading a thinner version of your site than the one you think you published.

Check what your mobile template actually contains

This is the first real check and it resolves a good share of these cases. Use URL Inspection on an affected page, run a live test, and read the rendered HTML rather than the browser view.

What I am looking for is anything present on desktop and missing there. In practice it is usually one of a short list: body copy trimmed for mobile, FAQ sections collapsed into accordions that never load their content, tables replaced with images, related content modules removed to save space, or structured data that only renders in the desktop template.

Accordions deserve a note. Content inside an expandable section is fine if it is in the HTML and merely hidden by CSS. It is not fine if the content only loads after the user taps. That distinction is invisible in a browser and decisive for indexing.

The other device-specific causes

Cause	Measurement (how to check)	How fast it recovers
Content missing from the mobile template	Rendered HTML in URL Inspection	2 to 4 weeks after recrawl
Intrusive interstitial on entry	Load the page on a phone from a search result	2 to 4 weeks
Mobile usability failures	Core Web Vitals and mobile usability reports	Gradual, rarely dramatic
Mobile page speed collapse	PageSpeed Insights, mobile tab specifically	Gradual
Separate m-dot site out of sync	Compare the m. version against the main one	Depends on the fault
More SERP features on mobile	Search the query on a phone, count what is above you	Not a demotion at all

The interstitial row is the one that catches marketing teams. A newsletter popup, a cookie wall that covers the content, an app install prompt or a discount overlay that appears immediately on arrival can all qualify. Cookie consent required by law is treated differently, but a promotional overlay sitting on top of it is not.

The last row is not a drop in the usual sense and it is worth separating out. Mobile SERPs give far more of the first screen to features, so position three on mobile can sit well below the fold while position three on desktop is visible. If your impressions and positions held on mobile and only clicks fell, that is displacement rather than a demotion, and traffic dropped but rankings the same covers it.

What about desktop-only drops?

Less common and usually less serious, but worth knowing because the logic is different.

Since indexing is based on the mobile version, a desktop-only decline is rarely an indexing or content problem. It is more often a change in the desktop SERP layout, a shift in your audience mix, or seasonality in who is searching. B2B sites in particular see desktop traffic swing with the working week and the holiday calendar in ways mobile does not.

Before treating a desktop decline as a problem, check what share of your traffic desktop actually represents. On a consumer site running 75 percent mobile, a desktop wobble is noise.

This is not a device problem if

• Both devices fell by similar proportions. That is a site-wide cause and the device split is a distraction.
• Your mobile share of traffic barely changed. If mobile was 70 percent before and 69 after, nothing device-specific happened.
• Positions held on mobile and only clicks fell. Displacement, not a demotion.
• The decline started when you changed something unrelated to the template. Check the date against your own deploy history before blaming the device.

Fixing it, in order

1. Compare mobile against desktop in the Devices tab and confirm the split is real rather than proportional.
2. Run a live URL Inspection on two or three affected pages and read the rendered HTML.
3. List anything present on desktop and absent there, then get it into the mobile HTML.
4. Load the page on a real phone, arriving from a search result, and see what appears before the content does.
5. Check Core Web Vitals on the mobile tab, which is a different dataset from desktop and usually much worse.
6. Only then check whether an algorithm update is involved.

Steps two and three carry most of the value. Everything here recovers on recrawling rather than waiting for a reassessment cycle, which makes a mobile template fault one of the better problems to have.

Frequently asked questions

Why did my mobile traffic drop but not desktop?

Because something is different about the mobile version. Usually content missing from the mobile template, an intrusive interstitial, mobile usability failures or slow mobile performance. Google indexes the mobile version, so mobile-only faults affect what ranks.

Does Google rank desktop and mobile separately?

Indexing is based on the mobile version for both, but results can differ by device because SERP layouts differ and some features appear on one and not the other. Your desktop rankings still depend on your mobile content.

Does content hidden in an accordion get indexed?

Yes if it is in the HTML and merely hidden by CSS. No if it only loads after the user taps. Check the rendered HTML in URL Inspection, because the difference is invisible in a browser.

Can a cookie banner hurt my rankings?

A legally required consent notice is treated differently from a promotional overlay. What causes problems is an interstitial that covers the content on arrival, such as a newsletter popup, discount overlay or app install prompt.

How long does a mobile template fix take to work?

Two to four weeks, because recovery follows recrawling rather than any reassessment cycle. Requesting indexing on your most affected pages speeds it up.

Country is the other segmentation worth running at the same time, and it catches a different set of causes: traffic dropped in one country only.