Track the device that drives your revenue, not both out of reflex. Pull your Google Search Console device split, see whether mobile or desktop sends the clicks that convert, make that your primary tracked device, and keep the other as a comparison column. The reason mobile vs desktop rankings diverge is the part most people get wrong: Google uses one index, but it builds two different result pages at serve time. So "position 3" on mobile and "position 3" on desktop can be completely different real estate.
This post explains why one index still produces two SERPs, why the same position can sit above the fold on desktop and below it on mobile, and the decision rule for which device to actually track.
Are mobile and desktop rankings different? Yes, and here's why
Mobile and desktop rankings are routinely different for the same keyword. Run the query on both and you'll often see a 1-3 position gap, sometimes wider. The cause isn't two separate indexes. Under mobile-first indexing, Google crawls and stores the mobile version of your pages as the canonical source for everyone. As Google's mobile-first indexing documentation puts it, "Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking." One index, one set of stored documents.
The divergence happens at serve time. When someone searches, Google assembles a result page for that specific request and applies device-aware signals on top of the shared index:
- Performance signals scored per device. Core Web Vitals are measured in the field as real-user data through the Chrome User Experience Report, which captures actual devices and network conditions. A page that loads fast on a wired desktop can score poorly on a mid-range Android phone over patchy 4G, and that gap feeds into ranking on each device.
- SERP features stacked differently. Mobile result pages lean harder on local packs, AI Overviews, "People also ask" accordions, and visual carousels because of the narrow viewport. Desktop spreads the same elements across more horizontal and vertical space.
- Layout and interaction. A thumb scrolling a six-inch screen behaves nothing like a mouse on a 27-inch monitor, and Google's interface adapts to that.
Google's own guide to its ranking systems lists page experience and relevance systems that all run against the same index, not a separate mobile one. For the full mental model of how positions are measured and stored, the pillar on how to track keyword rankings in India covers it end to end.
Does mobile-first indexing mean one set of rankings? No
This is the confusion worth killing. Mobile-first indexing decides which version of your content Google reads to understand your page. It is not a promise of one ranking number.
Two separate facts get blurred:
- One index. Google stores the mobile rendering of your page as the canonical document, which is why the same documentation warns that "only the content shown on the mobile site is used for indexing."
- Two SERPs. Google still generates a distinct result page for each device class at query time.
So you can lose content that lives only on your desktop layout, and still rank in two visibly different positions depending on the searcher's device. Mobile-first indexing changed what gets crawled. It did nothing to merge the result pages. The sibling guide on mobile-first indexing in India walks through the content-parity checks that protect you here.
Why a "good" mobile position can still be invisible
Here's the consequence that actually costs traffic. Position alone is misleading on mobile because of how features stack vertically.
Picture ranking #3 for "best running shoes":
| Element above your link | Desktop | Mobile |
|---|---|---|
| AI Overview | Compact, collapsible | Full-width, expands on tap |
| Shopping / image carousel | Inline, narrow strip | Full-width block |
| "People also ask" | Often below the fold | Often above your #3 link |
| Ads | Top stack | Top stack, taller |
On desktop, #3 frequently sits in view without scrolling. On mobile, those same features are full-width and stacked, so your #3 organic link can land two or three thumb-swipes down the page. Identical position, completely different visibility. This is exactly why tracking the raw number without context misleads you. See how SERP features change what a position is worth, and why a single snapshot misreads movement in why Google rankings fluctuate.
It also answers a question every SEO eventually asks: why does my site rank higher on desktop than mobile? Usually it's a mix of weaker mobile Core Web Vitals, heavier feature stacking on the mobile SERP, or content collapsed behind tabs on the mobile layout.
Which device should you track? Check your own data first
Don't pick on instinct. Pick on revenue. The rule is three steps:
- Open Google Search Console and split Performance by device. You get clicks, impressions, and average position for mobile, desktop, and tablet separately. This is the number that matters because it's your actual audience, not an industry average.
- Cross-reference with where money is made. If 78% of converting sessions come from mobile, mobile is your primary. A B2B SaaS selling to people at their desks may find desktop drives the deals despite mobile having more raw traffic. Traffic share and revenue share are not the same thing; weight toward revenue.
- Track the majority-revenue device as primary, the other as a diff. You still watch both, but one is the number you report and act on, and the other is a comparison column that flags when the gap widens.
A worked example. A D2C skincare brand pulls its split: 82% mobile clicks, 71% of revenue from mobile. Mobile is unambiguously primary. They track all money keywords on mobile, keep desktop as a secondary diff, and only investigate when a keyword shows desktop far ahead of mobile, which usually points to a mobile performance or layout problem worth fixing. Connecting your property through Search Console turns this split into a two-click report instead of a guess.
Setting up device-specific tracking without doubling your costs
Tracking both devices for every keyword is the reflex, and it's wasteful. Each tracked device is a separate query, so monitoring 2,000 keywords on both devices is effectively 4,000 checks. Most of that second set tells you nothing you'll act on.
A leaner setup:
- Primary device on every keyword. Whatever your GSC split named as the revenue driver.
- Secondary device only on your top money terms. The 20-50 keywords where a device gap would actually change a decision. This keeps the diff useful without paying to track every long-tail term twice.
- Pair device with location. Mobile searches skew local, so device and geography interact. The same keyword on mobile in Pune versus Chennai can differ as much as mobile versus desktop, which is why rank tracking by city belongs in the same setup, and why local pack tracking matters most on mobile.
- Set a sane frequency. Device splits don't swing hour to hour, so weekly is plenty for most keywords; the daily vs weekly rank tracking tradeoff is about volatility, not device.
If you're still deciding how broad to go, how many keywords you should track keeps the list disciplined.
Don't panic at a device gap, diagnose it
A persistent gap between devices is signal, not noise. When mobile trails desktop on a keyword that matters, walk the likely causes in order:
- Mobile Core Web Vitals. Test the page in PageSpeed Insights on the mobile profile. A slow Largest Contentful Paint or layout shift on mobile drags the mobile ranking specifically. Google's guidance is a Cumulative Layout Shift of 0.1 or less for at least 75% of visits; mobile pages with late-loading ads and images miss that bar far more often than desktop.
- Feature crowding. Your position may be fine; the SERP just buries it under more features on mobile. That's a content-format fight (earn the AI Overview citation, the image pack, the local pack), not a position fight.
- Collapsed mobile content. If key content sits behind accordions or tabs on mobile, it may carry less weight. Mobile-first indexing reads that mobile version, so what's hidden there is what Google sees.
- Real volatility. Sometimes it's an algorithm wobble hitting one device's SERP first. Before acting, confirm it's sustained rather than a blip.
The short version
The same query renders two different result pages because Google draws from one index but serves with device-specific signals. So rank is always a per-device fact. Stop tracking both reflexively. Check your Search Console device split, track the device that pays as primary, keep the other as a diff on your money terms, and judge positions by what's actually above them on that device's SERP, not by the number alone. You can check any keyword's rank for free right now, and DeployFlare's rank tracking handles device, city, and language splits automatically, billed in INR from ₹499/month rather than in USD.