Setting Up Position Checks: Regions, Devices, Goals
The accuracy of position tracking is determined by settings, not the service: the same query in a different region or on a different device ranks differently. Below are the settings to specify when creating a project to ensure the numbers reflect your reality.
What to Set Up During Configuration
| Parameter | How to Choose |
|---|---|
| Search Engine | The one from which your traffic comes; checking "just in case" three systems multiplies expenses without benefit |
| Region | The city or country where the clients are located: for local businesses, the region radically changes the results |
| Device | Mobile and desktop yield different results; if traffic is mainly mobile, track it |
| Position Goal | Realistic: aiming for first place from the 40th is pointless, aiming for the top 10 is sensible |
| Cluster | A group of queries for one page — this way, you can see group movement rather than by individual keyword |
How Many Queries to Take
Not just any queries. The working set includes queries for which you are already showing and are close to the goal, plus a few flagship ones for control. It's convenient to take the list from Search Console: it shows what actually brings impressions. Up to a thousand queries are allowed for a project, but a hundred meaningful ones are more useful than a thousand random ones.
Frequency of Checks
- Daily makes sense in competitive niches and during active work.
- Once a week is a normal mode for most projects: daily fluctuations are still noise.
- Before and after changes — mandatory: without a reference point, you won't understand what worked.
What to Set Up Additionally
Notifications for entering and exiting the top — so you don't have to check the report every day. Connected Search Console will add real frequency to the queries and show missed traffic. An overview of the service as a whole — Rank Tracker.