Movers and shakers
Queries whose clicks changed 20% or more between the last 28 days and the 28 days before, split into rising and declining.
What it returns
Real rows, no sign-inClicks per query across two 28-day windows, for queries with 50 or more impressions and a 20% change.
Keyword | Direction | Clicks before | Clicks now | Change | Position |
|---|---|---|---|---|---|
| share debugger | rising | 1 | 5 | +400% | +0.9 |
| schema validation | rising | 1 | 4 | +300% | -0.2 |
| schema detector | rising | 1 | 4 | +300% | -0.5 |
| microdata validator | rising | 1 | 4 | +300% | -0.1 |
| check sitemap online | rising | 3 | 11 | +267% | -0.4 |
| check meta title and description | rising | 3 | 11 | +267% | — |
| faq schema test | declining | 3 | 0 | -100% | +0.1 |
| meta title length check | declining | 1 | 0 | -100% | -3.1 |
| google schema checker | declining | 5 | 0 | -100% | -0.3 |
| rich snippet tester | declining | 1 | 0 | -100% | -9.4 |
| sitemap lastmod | declining | 1 | 0 | -100% | -2.3 |
| title length checker | declining | 2 | 0 | -100% | -1.6 |
These are nuxtseo.com's own rows, read from its Search Console record. Connect a Site below to run the same query over yours.
Run it on your own record
HostedRead-only Search Console scope. Free during beta.
gscdump analyze movers --site sc-domain:example.com --prev-start YYYY-MM-DD --prev-end YYYY-MM-DD
LocalMIT licensed, on npm.
Over MCP: run-report { siteId: "<site-id>", reportId: "movers", comparison: "prev-period" }
Connect with MCP to reach it from ChatGPT, Claude, Cursor, or Copilot.
What the query compares
Two windows of your Search Console record: the last 28 days and the 28 days before them. For every query with 50 or more impressions, the query takes clicks and average position from each window and lists the ones whose clicks moved 20% or more.
Rising rows sort by the size of the gain, declining rows by the size of the loss. Each table shows up to 50 rows, and the counters above them sum the clicks gained and lost across those rows.
Reading the two tables together
- Clicks up, position up. Recorded clicks rose and average position improved. The comparison does not establish why either changed.
- Clicks down, position steady. Recorded clicks fell while average position stayed similar. These rows do not measure search volume or results-page features.
- Clicks down, position down. Recorded clicks fell and average position worsened. The comparison does not establish the cause.
- Most rows in one table. Many reported queries changed in the same direction. These capped tables do not establish a change across the whole Site.
Common questions
See also
- Content decay
- Pages whose clicks fell 20% or more against the previous 28 days, with the clicks lost.
- Striking distance keywords
- Queries ranking 4-20 by impressions, with CTR and clicks for each.
- Opportunity keywords
- Queries scored by position, impressions, and CTR gap.
Every day you're not syncing is data Google will delete.
Eligible Sites backfill available Search Console history. Data sources depend on the tool and account. Free during beta.