Incognito mode won't tell you your real Google ranking
It's the advice every result on page one repeats: open a private window and search your keyword. It sounds clean and it's nearly useless. Incognito clears three things and leaves untouched the five that actually move the result.
TL;DR
- ✓ Incognito clears cookies, history and your session. That's it. Your IP, your language, your device and the timestamp still ride along on every query.
- ✓ Location is the heaviest variable and incognito doesn't touch it. Google still geolocates you from your connection inside a private window.
- ✓ What moves your slot isn't personalization, it's SERP features. An AI summary or a local pack pushes you down the page while your organic position stays exactly where it was.
- ✓ One observation is not a measurement. Two checks are only comparable if they share query, location, language, device and time window.
- ✓ History starts the day you add the keyword. 5 keywords on a weekly check in the Free plan already build a series manual searching never will.
Why everyone recommends incognito mode to check your Google ranking
Search for how to check your Google ranking and page one will hand you the same answer ten times over: open an incognito window, type your keyword, count down the results until you find yourself. The advice is old, it's free, and its logic feels airtight. If Google shows your own site higher because you visit it daily, then wiping the trail should reveal the neutral result — the one a stranger sees.
The trouble is that the advice was minted around 2010, when Google had just extended personalized search to signed-out users and the filter bubble debate was at its loudest. In that context it made sense: browsing history was the strange, suspicious variable, and erasing it looked like enough to reach a clean result. Fifteen years later the results page barely resembles that list of ten blue links, and history went from being the main source of distortion to being one of the smallest.
There's also a less technical reason the advice survives: it feels good. You open the window, type, count, and walk away with a number. That number feels objective because you saw it with your own eyes. Data from a tool feels borrowed; what appears on your screen feels true. It's the same bias behind every business owner who swears the site is "number one" because searching the brand from the office always puts it at the top. Of course it does — that's a branded query typed from the company's own network.
This isn't an argument that incognito is worthless. It's an argument that it solves a small problem and leaves the big one intact. Below I separate exactly what it clears and what it doesn't, how much each thing weighs, and which conditions a check has to meet before today's number can be compared with next month's. If you'd rather skip to what can be measured continuously and automatically, that's on the Rankiamos features page. If you're here for the argument, keep reading.
What incognito mode does clear (and it's less than you think)
Be fair to the tool before dismantling it. A private window does three real things and does them well. First, it starts with no cookies, so both the site and Google treat you as a first-time arrival. Second, it doesn't write that session into your history, so what you search there won't shape what you see tomorrow. Third — and this is the part that matters most for SEO — it doesn't carry your Google session, so you aren't signed in and account-level signals don't apply.
All of that is fine. The catch is that the list of what it doesn't clear is longer, and its items weigh more. Here's the full split.
| Signal | Cleared by incognito? | Impact on the slot you see |
|---|---|---|
| Browser cookies | Yes | Low |
| Session search history | Yes | Low |
| Signed-in Google account | Yes | Medium on ambiguous queries |
| Your IP address and the location it implies | No | Very high |
| Browser and system language | No | High |
| Device type and screen size | No | High |
| Which SERP features fire | No | Very high |
| The exact moment of the query | No | Medium |
Look at the shape of that table. The three green rows are things incognito fixes, and on most commercial or informational queries they move very little. The five amber rows are what's left standing, and that's where both "very high" labels sit. Translated: incognito cleans up the cheap noise and never touches the expensive kind.
There's a fourth point almost nobody makes explicit: incognito doesn't hide you from Google. A private window stops your browser from storing data locally. It doesn't anonymize your connection and it doesn't stop Google inferring where you are. It's a privacy feature aimed at other people who use your computer, not an anonymity mechanism aimed at the search engine. Conflating those two is the root of nearly every misunderstanding on this topic.
Four sources of noise incognito doesn't remove
Ordered by how much they distort the number you're about to write down.
1. Your location, inferred from your connection
This is the single most decisive variable and incognito leaves it fully intact. Google infers where you are from your IP address and tailors results to that area whether the window is private or not. Searching "seo agency" from Austin and from Dallas returns different result pages for the same query, on the same device, typed the same way. No private window corrects that, because it isn't personalization — it's localization, and Google applies it by design.
What makes it worse for measurement is that the inference isn't stable. Switch from Wi-Fi to cellular and your zone can move. Leave the office and the corporate network was placing you in a different neighborhood anyway. Turn on a VPN and the exit node picks for you. This article doesn't develop the topic — city-level measurement has its own guide on tracking rankings across multiple cities, and viewing results for a different country is a separate subject that deserves its own piece — but the conclusion stands: if location isn't a declared parameter of the measurement, nothing else you do matters.
2. Browser language and regional settings
Your browser announces which languages you prefer on every request, and Google uses it. If you added a second language at some point, or your operating system shipped in a language you never changed, the SERP you see for a given query can include results a monolingual user in the same city would never be shown. The incognito window inherits all of it: same browser, same language preference.
This bites hardest on anyone working bilingual markets — US Hispanic audiences being the obvious case. An SEO with English and Spanish both enabled sees a mixed results page and draws conclusions about an audience whose phones are set to one language only. Same city, same query, two different result sets, and incognito is entirely irrelevant to the difference.
3. The SERP features that shift your visual position
This is the one that changed the game most and gets discussed least in the posts recommending incognito. Your organic position and where you actually appear on screen stopped being the same thing. Between the top of the page and your third organic result there can be an AI summary, a "people also ask" block, a video carousel, a local pack with three business listings and a row of ads. You're still result number three and you can still land below the fold on a laptop.
So when you count by hand in a private window, what are you actually counting? Usually a blend: you skip the ads, you may or may not count the local pack as a slot, and you ignore the questions block. That informal rule drifts from one day to the next without you noticing, and it drifts hardest between people. Two members of the same team can report 4 and 7 for the same keyword on the same day because they counted differently, not because they saw different pages.
And it compounds: these features switch on and off by query and by moment. A search that triggers an AI summary today may not tomorrow. Your organic position didn't shift a single slot, but the page looks completely different and so does your traffic. That's why tracking citations inside Google's AI summary is a separate measurement from classic position, not a cosmetic detail.
4. The exact timestamp and index volatility
Google isn't reading a frozen table, it's computing a result. The index updates continuously, live experiments run on the results page, and responses can come from infrastructure that isn't synchronized to the second. Two identical searches ten minutes apart can return different orderings without anyone having published anything.
Then add observer bias, the cheapest source of noise to eliminate and the one nobody eliminates. You search your brand at 9am on the day you shipped an article, or right after a client emailed you sounding worried. You never search at a neutral moment, because the impulse to search always comes from something that just happened. An automated series measures the Tuesday when nothing happened — and that's exactly the data point that gives meaning to the Tuesday when something did.
One scoping note: the gap between mobile and desktop positions is a separate case and a bigger one than most people assume; it's covered in the guide on mobile vs desktop rankings. For our purposes here, just remember that incognito doesn't change your device either: if you check from a laptop, you're measuring desktop, and most of your audience probably isn't there.
Google personalized results: the DuckDuckGo finding that undercuts the advice
So far the argument has been that incognito doesn't touch the variables that matter. Here comes the more uncomfortable part: it doesn't fully solve the one thing it promises to solve either. In December 2018 DuckDuckGo published a filter bubble study in which a group of volunteers searched the same terms at the same time. The relevant conclusion is that most participants saw a different set of results from one another for the same query, and running the search in private mode while logged out barely reduced that variation.
Google publicly disputed the methodology and has argued repeatedly that history-based personalization is limited and concentrated on ambiguous or repeated queries. Both positions can be partly right at once, and you don't need to referee the debate to extract the practical lesson, which is this: even if you side entirely with Google and accept that history-based personalization is small, that weakens the incognito advice rather than saving it. If history barely influences results, clearing it barely changes them. And if it does influence them, the study suggests a private window doesn't fully neutralize it. Either way, incognito isn't the measurement method you were told it was.
What both sides do establish is that Google personalized results are the tip of the iceberg, and a small tip. The bulk of the variation comes from everything above: where you are, in which language, on which device, at which moment, and with which features live on that results page. None of those five is personalization in the strict sense, which is exactly why none of them is fixed by privacy.
How to cite this without getting burned
If you're putting the DuckDuckGo study in a deck, date the source (December 2018) and mention that Google objected to the methodology. A finding from more than seven years ago about a product that changes weekly is not definitive proof of anything; it's a useful signal. Honesty is tactical here too: present an old data point as current, have the client check it, and you lose the entire argument — including the parts that are solid.
Why your Google ranking changes between one search and the next
"Why does my Google ranking keep changing" shows up daily in forums, and the usual answer is one word — volatility — which explains nothing. Breaking it down is more useful, because each cause has a different consequence for how you should be measuring.
-
Cause 1 · The index is always moving
Google crawls and reprocesses continuously. A competitor's new URL, a changed title elsewhere, a recalculated link — any of those reshuffles the list. It's the most legitimate source of movement and the only one you actually want to measure. Consequence: you need a time series, because only many points let you tell a real move from a bounce.
-
Cause 2 · Google is running experiments
The results page is permanently under test: formats, blocks, the order features appear in. You can land on one variant and then on another on the next search. Consequence: a single observation proves nothing, and two contradictory observations in a row don't mean something is broken.
-
Cause 3 · SERP features fire and vanish
The same term can trigger an AI summary in the morning and not in the afternoon, or show a local pack only when Google reads local intent. Consequence: separate organic position from on-screen placement, and record which features were live when you measured. Counting by eye blends the two irreversibly.
-
Cause 4 · You aren't searching the same thing
"Rank tracker" and "seo rank tracker" are two different queries, as are a singular and a plural, or the same words in a different order. Typing by hand, you rarely enter the identical string two days running, and autocomplete happily nudges you off course. Consequence: the query has to be stored literally, not retyped from memory.
-
Cause 5 · You changed the context without noticing
Last time you checked from your phone on cellular, this time from the laptop at the office. Or it was 7pm then and it's 9am now. Consequence: context has to be a fixed parameter. That's the line between an experiment and an anecdote.
One frequent confusion deserves clearing up here. People compare what they saw in incognito against the average position figure in Search Console, find they don't match, and conclude one of the two is lying. Neither is: they answer different questions and are computed differently. How that metric is built and why it rarely matches what you see on screen is covered in detail in the piece on Search Console average position versus real position. For our purposes one rule is enough: don't audit an average with a manual search, and don't audit a manual search with an average.
The conclusion of this section is short and it's the hinge of the whole article. Variation is normal and unavoidable. The point of measuring well isn't to eliminate it — you can't — it's to zero out the variables you do control so that whatever movement remains actually means something. That's precisely where manual searching fails: it adds variance instead of removing it.
Checking your real Google ranking: what makes a check comparable
Six conditions. Manual searching meets one, on a good day.
Enough about what's wrong — here's the standard. A check is decision-grade when today's result is comparable with last week's, and that takes six conditions. They aren't optional or interchangeable: fail one and the rest lose value.
| Condition | What it means in practice | Manual search meets it? |
|---|---|---|
| Literal query | The same string, character for character, on every check. | Rarely |
| Declared location | Country and city set as parameters, not inferred from your connection. | No |
| Fixed language | Search language is a parameter, not your browser's preference list. | No |
| Defined device | You know whether the number is mobile or desktop, and you don't mix them. | Sometimes |
| Stable cadence | It runs every day or every week regardless, not when you remember. | No |
| Dated record | Every result is stored with its date and can be pulled up again later. | Never |
That last row is the decisive one, and it means this debate isn't really about accuracy at all. You can grant that an incognito search gives you a roughly correct number and the argument still holds, because the number isn't stored anywhere. Three months from now, when you want to know whether that keyword improved, you'll have exactly zero comparison points and a vague feeling that "we used to be lower". You can't justify a budget or defend a result to anyone with that.
So the right question isn't "does incognito give me the exact number?" but "does this method build a series?". Manual searching produces loose observations; an automated check produces a series. And everything worth deciding in SEO — whether a change worked, whether a drop is yours or the market's, whether a competitor is eating your ground — comes out of the series, never out of the observation.
One detail on the location point, since it's the objection I get most: "I can force location with DevTools or a VPN." You can. And it works the first time. The problem is reproducing it identically every week, for every city and every device, for months, without slipping once. A method that depends on your discipline to stay intact is already broken.
Building a history from zero: 5 keywords, weekly, free
The practical objection to all of the above is usually financial: "I get the argument, but I'm not paying for a tool to watch three keywords." Fair enough — which is why it's worth grounding the actual starting point, which costs nothing. The Rankiamos Free plan includes 2 projects, 5 keywords, an automatic weekly check, Google Search Console integration and a site scan, with no credit card. The one condition: the weekly check pauses if you go 30 days without opening the app.
5 keywords sounds like nothing until you choose them well. Most small projects don't have five terms that genuinely move the business: they have two or three, plus a long list of variants that change no decision. If you have to pick five, this is the split I use: the head query the money comes from, the variant with the clearest purchase intent, the brand term (so indexing problems surface fast) and two terms sitting between positions 8 and 20, which move the most and teach you the most.
The detail that decides everything: a keyword's history starts the day you add it. It isn't retroactive and there's no way to recover the past. If you'd stopped hesitating two years ago, you'd have two years of series today. This is also why adding the keyword before a significant site change isn't a process nicety: it's the difference between being able to demonstrate the effect and not.
On cadence, be honest about what each rhythm can answer. A weekly check answers "is this keyword trending up or down this quarter?" well. It does not answer "which exact day did it move?", and that second question is the one you need right after shipping a change or when a client asks you to explain a drop. That's what the Pro plan's daily check is for: roughly thirty points a month instead of four, and thirty points is where a step change becomes distinguishable from a bounce. (On Pro, a keyword with 5 or more measurements that goes 30 days without any change drops to a check every 3 days until it moves, and on either plan you can re-measure a keyword by hand 6 hours after its last check.)
Since we're on quotas, the concrete rule: each keyword-by-city combination consumes one unit, so tracking one term across two cities burns two of your 5 Free units. On Free, each keyword is measured on one device, mobile or desktop. On Pro you can pick mobile, desktop or "Both," but each device consumes its own unit: tracking the same keyword on both costs two units, not one. The full per-plan breakdown is on the pricing and plan limits page.
One last point about where the data comes from, because it closes the loop. Queries don't originate from your connection or your browser: they're resolved through DataForSEO using the country and language you set for each keyword, on Google (and also on Bing, on the Pro plan). Your iPhone, iPad, Mac or Apple Watch is the screen where you read the result, not the measurement point. That's where your history, your cookies and your IP stop contaminating the number.
How Rankiamos handles it
Take your browser out of the equation and leave the data point dated.
📍 Location as a parameter, not an accident
Country, language and, if you want, a city are set on each keyword and repeated identically on every check. Coverage spans 19 countries — 17 Spanish-speaking LATAM countries, Spain and the US (measured in English) — plus 52 cities to choose from for city-level tracking.
📆 Automatic cadence and dated records
Weekly on Free, daily on Pro, and on both plans you can re-measure a keyword by hand 6 hours after its last check. Every measurement is stored with its date, so the series builds itself even on the weeks you never open the app (on Free, the weekly check pauses after 30 days without opening it).
📱 Each device uses its own unit (Pro)
On Pro you pick mobile, desktop or "Both"; each device consumes 1 unit, so tracking the same keyword on both costs 2. On Free, each keyword is measured on one device. Each keyword-by-city combination also consumes one unit, which is worth planning around before you add cities.
🤖 Citations in Google's AI summary
On Pro, alongside organic position, see whether Google showed its AI summary, whether it cites you and up to 6 cited sites. On every plan, the daily alert tells you when the summary appears, cites you or stops citing you. That's the part of the SERP that moves your traffic without moving your slot.
The honest close: no tool gives you "the" absolute position, because that position doesn't exist. There's a position for a query, a location, a language, a device and a moment. What a tool can do is pin those five variables down and never let go — which is exactly what manual searching doesn't do. If you want the full list of what gets measured continuously, it's in the product feature breakdown. And if you'd rather start without spending anything, 5 keywords on a weekly check is a perfectly respectable place to begin.
Free plan: 2 projects, 5 keywords, weekly check · iPhone · iPad · Mac · Apple Watch
Frequently asked questions
So is incognito mode useless for SEO? ▾
How much does Google actually personalize search results? ▾
Why does my Google ranking change between one search and the next? ▾
How do I check my Google ranking in a way that stays comparable over time? ▾
Can I just force a different location in my browser? ▾
Is the Rankiamos Free plan enough to stop searching manually? ▾
Does Rankiamos measure from my phone or from somewhere else? ▾
Read also
Search Console average position vs real position
Why the number in the report almost never matches what you see on screen, and how it's actually calculated.
GeolocationTracking rankings across multiple cities
The variable that shifts your result the most, turned into a parameter you can fix and compare.