A position check is an observation of a particular search, not a universal score for a website. Record context before comparing results or deciding what to change.
Define the search conditions
Specify query, language, location, device and date. Record the ranking URL and result type. A map entry, an advertisement and an organic web result are different placements and should not be counted interchangeably.
Use repeatable evidence
Prefer a consistent tracking method over occasional personal searches. Search Console can provide first-party query and page performance, but its average position is not identical to a single live result. Record each source’s definition and limits.
Act on a pattern, not one movement
Review relevant page and query groups across a suitable period. Check whether a change is accompanied by impressions, clicks or qualified outcomes. Do not rewrite a useful page simply because a single check differs.
Put the method to work
Illustrative check: a service page appears differently on mobile in Copenhagen than on a desktop elsewhere. The team preserves both observations and chooses one consistent market-and-device setup for future comparison rather than averaging unlike searches.
Your next steps
- Record query, location, device and date.
- Identify the actual ranking URL.
- Compare consistent observations over time.
Questions & answers
Does private browsing remove all variation?
No. Location, device, result changes and other conditions can still affect what is shown.
Does Gavek provide a live Google ranking database?
Not currently. This page describes a checking workflow using appropriate external or first-party evidence.
Documentation & further reading
- support.google.com · › webmasters › answer › 7042828
- developers.google.com · › search › docs › monitor-debug › debugging-search-traffic-drops ›
- support.google.com · › webmasters › answer › 7576553
Explore the related in-depth guide ↗ · Build an action plan ↗