Scans and geographies
What gets fetched, where, on what, and how often — the configuration that drives the cost.
What a scan is
A scan pairs a keyword list with the dimensions to measure it across: search engines, devices, and geographies. Its cost is the product of those, per keyword — see slots.
Multiple scans per domain are normal: a broad national one, plus a tighter local one over a shorter list.
Geographies
Results differ by location, especially for anything with local intent. The selector cascades: country → region → city. Country-level tracking is available on every plan; city-level is a paid capability, because city-level results are a separate fetch each.
Search volume is collected at country level even when positions are tracked per city. City-level volume figures from data providers are floored at a value low enough to be misleading, so publishing them as if they were measurements would be worse than honestly showing the country figure.
Devices
Desktop and mobile results genuinely differ, often a lot for local queries. Each device is fetched separately, so each counts toward slots. If budget is tight, track the device your customers actually use rather than both.
Schedule
Scans run weekly. They also run automatically when you change what is tracked, so new keywords get their first measurement promptly rather than waiting.
Weekly rather than daily is deliberate. Daily rank data is mostly noise — positions fluctuate for reasons unrelated to anything you did — and paying to collect that noise buys volatility rather than insight.
Running a scan now
Update rankings now triggers an immediate run. Two things to know: if a run is already in progress you join it rather than starting a second one (which would buy the same pages twice), and there is a cooldown between on-demand runs so an impatient click cannot run up the bill.
Pausing
Deactivating a scan stops its fetching and frees its slots at the end of the billing month. The history stays.