Know where you stand. Every week.

Once a week, on each keyword’s own cadence counted from the day you added it — so keywords added on different days are checked on different days, and no single date holds them all. Weekly rather than daily is a decision rather than a shortfall: a position moves a place or two between one day and the next for reasons nobody can act on, and a daily check bills you for that noise. The screen groups checks into weekly rounds for the same reason, and a week in which nothing was checked is left out of a line rather than drawn as a flat stretch.

Desktop by default. Mobile is a switch on the project, and turning it on gives every keyword in that project a second check every week — so each keyword then spends two of the workspace’s tracked-keyword slots rather than one, which is why the switch is where the arithmetic is stated. Turning it off is never refused, whatever state the subscription is in.

Every check records the market it was asked in, and this screen shows only the checks taken in the market the project is in now. A check from before you changed market is kept and is left out of this screen’s own reading, because a position in one country is not a stale answer about another — it is an answer to a different question.

• A distribution across 7 buckets: five ranked bands, plus the two facts a position cannot state on its own — checked and found nowhere, and not yet checked.
• Each keyword’s change against its own previous check, dated, with an upward glyph meaning a smaller number.
• A line per keyword over the last 8 weekly rounds, broken wherever a week measured nothing.
• Which blocks the results page carried — a featured answer, a local pack, images — as presence only.
• Which of your own URLs ranked, so two of your pages competing for one phrase is visible rather than averaged away.
• A visibility estimate for your set and for each rival you track, from a published click-through curve and labelled as an estimate.

Three of the columns are three different instruments and the page names each one’s source in its heading: the position is this product’s own weekly check; Volume is Google Ads’ monthly searches in the project’s market, refreshed once a month; Clicks is Search Console’s own count over the window the column names, and is blank until you connect a property. A search position and a Search Console position are two different measurements and never share a column or a chart.

A bucket’s own change is printed without a colour, deliberately. Two keywords leaving the lowest ranked band is good news if they moved up into the band above and bad news if they fell out of the ranks entirely, and the count alone cannot tell which — so it says what moved and leaves the reading to you. A single keyword’s change is two dated measurements of one thing, which is where a colour is honest.

Nothing here is defaulted to zero. A keyword whose volume has never been measured, a keyword Search Console stored nothing for, and a rival a check never found are each printed as a dash. A bucket’s count is a real count, so a bucket holding nothing prints nought.

Nothing fires the moment a position moves. There is no per-event notification in this product — no push, no webhook, nothing at all triggered by one keyword changing place — and the screen is where a change is, dated, beside the keyword it happened to.

What does reach you is an email in a week that had something in it. The workspace’s owners are sent a digest whose rankings line says how many tracked keywords improved and how many declined, each against its own previous check, beside the same week’s crawl and model findings. It is a summary of a week rather than a reaction to an event, it is on until somebody turns it off, and the switch is on the People page of the workspace.

It also does not watch a keyword you have not chosen. The set is yours to curate, and untracking one is always allowed — removing scheduled work is the one thing that is never refused.