usdigitalmarketingindex.com SEO
How can desktop and mobile organic rankings be compared without mixing device effects?
Updated November 15, 2026
By holding everything else constant: the same queries, the same country, the same dates, and the same definition of position, with the two devices placed side by side for each query. A blended figure such as “average position on mobile is 12 and on desktop is 9” compares two different sets of searches. People search for different things on phones, in different places, and the results pages are laid out differently. The difference between those two averages reflects the mix of queries at least as much as where the site ranks. A fair comparison asks a narrower question: for this query, in this country, over this period, what was the position on each device? Then it summarizes over a fixed list of queries present on both.
Device labels and available metrics
Search Console’s performance report records device as a dimension and lets two devices be compared. Its help describes the function: “Compare: Evaluate two devices, countries, Search types, or Search appearances side by side” (Search Console help on advanced filtering and comparison). It also allows several filters at once, giving the example of a country and a device together.
| Element | What is available |
|---|---|
| Device categories | Desktop, mobile, tablet |
| Metrics | Clicks, impressions, click-through rate, average position |
| Combination | Device can be combined with query, page, country, and date |
| Comparison | Two devices side by side, with a difference column |
Decide how to treat tablets. Either report them separately or leave them out. Folding them into one of the others changes that category’s numbers.
Third-party rank trackers offer a different measurement: a position observed for a chosen query from a simulated device and location at a moment in time. That is a sample of one search, where Search Console’s figure is an average over real searches. State which is being used. The two should not be mixed in one table.
Query mix differences
The set of queries a site appears for differs by device.
| Difference | Effect on a blended average |
|---|---|
| Different queries | Device averages are computed over different lists |
| Different volumes for the same query | A query with most impressions on mobile dominates the mobile average and barely affects desktop |
| Local and "near me" queries | Concentrated on one device, with their own results layout |
| Long, research-style queries | Distributed differently |
| Branded queries | Share differs by device, and they rank near the top |
| Country mix | Device share varies by country, so an unfiltered comparison also mixes countries |
Control it in this order:
- Filter to one country.
- Fix the date range, identical for both devices.
- Build a query list present on both devices with enough impressions on each to be meaningful.
- Compare per query.
- Summarize over that list only, and say how many queries it contains.
Queries that appear on one device only are a finding of their own. List them separately instead of letting them tilt an average.
Position interpretation
Position has a specific meaning in Search Console, and it is not identical across devices.
From Search Console’s help on these metrics:
- The definition of position reads: “A relative ranking of the position of your link on Google, where 1 is the topmost position”.
- The value reported is “the topmost position occupied by a link to your property or page in search results, averaged across all queries in which your property appeared”.
- “Position value is the average position for all searches.”
The help page gives an example of how the same position number can correspond to different places on screen. For an image result, it says a given position could mean the second or third row on desktop, visible without scrolling, and the sixth row on mobile, visible only with scrolling (Search Console help on impressions, position, and clicks).
So:
| Caution | Reason |
|---|---|
| Equal positions are not equal visibility | Layout differs: what occupies the screen above a given position is not the same on a phone and a monitor |
| Position counts elements, not pixels | Features above the result occupy positions or space differently by device |
| An average hides distribution | Position 5 on every search and positions 1 and 9 alternating both average 5 |
| Low impression counts make averages unstable | A handful of searches can move the figure |
| Click-through rate at a position differs by device | Compare CTR within a device, or with the layout noted |
Read position alongside impressions and clicks, never alone.
Reporting examples
An illustrative device-segmented query report. The figures are invented to show the layout and are not observations of any site.
Filters: country United Kingdom; dates, one fixed 28-day period; search type web.
| Query | Desktop impressions | Desktop avg position | Mobile impressions | Mobile avg position | Difference in position |
|---|---|---|---|---|---|
| boiler service cost | 1,200 | 4.1 | 3,900 | 6.8 | Mobile 2.7 lower |
| boiler pressure too high | 800 | 3.0 | 5,100 | 3.2 | Similar |
| power flush central heating | 950 | 7.5 | 1,400 | 7.9 | Similar |
| emergency boiler repair near me | 60 | 9.0 | 2,300 | 11.4 | Desktop sample small |
| combi boiler vs system boiler | 1,500 | 5.2 | 2,000 | 5.0 | Similar |
How to read it:
- The first row shows a real device gap on a query with ample impressions on both devices. It is worth investigating.
- The fourth row shows a difference that rests on 60 desktop impressions. Mark it as too small to conclude from.
- Three rows show no meaningful difference.
A summary line done properly:
| Summary | Value |
|---|---|
| Queries in the matched list | 5 |
| Queries with impressions above the threshold on both devices | 4 |
| Of those 4, queries with mobile position lower by more than 2 | 1 |
| Of those 4, queries with desktop position lower by more than 2 | 0 |
A summary line to avoid: “Average position: desktop 5.8, mobile 6.9”. It averages across queries with very different volumes, and without the table behind it nobody can tell whether it describes one query or all.
When a per-query gap is real, the next questions are about cause.
| Question | Where to look |
|---|---|
| Does the mobile results page for that query contain features the desktop page does not? | Search the query on both devices and record what appears, with the date |
| Does a different URL rank on each device? | Add the page dimension |
| Does the mobile page differ in content from the desktop page? | A parity check of the two versions |
| Is the mobile page slower or harder to use? | Field performance data by device |
| Is the difference stable over time? | Repeat for the previous period |
Presentation rules for the report:
- State the filters above every table.
- Show impressions next to every position.
- Mark rows with small samples.
- Keep desktop and mobile in separate columns. Do not merge them into an “all devices” position alongside.
- Compare like periods. A change in position between two periods is read within one device.
Where the investigation points to the mobile page lacking content that the desktop page has, the method for confirming it is set out in the guide to how to identify important content missing from the mobile version of a website.
The method in order: one country, one date range, a matched query list, per-query comparison with impressions shown, and a summary that counts queries instead of averaging positions.
Add your comment to this answer