--- title: "Movers and shakers · gscdump" canonical_url: "https://gscdump.com/tools/movers" last_updated: "2026-10-03T04:31:36.367Z" meta: description: "Queries whose clicks changed 20% or more against the previous 28 days in your Search Console record, split into rising and declining. Free with Google sign-in." "og:description": "Queries whose clicks changed 20% or more against the previous 28 days in your Search Console record, split into rising and declining. Free with Google sign-in." "og:title": "Movers and shakers · gscdump" --- Which queries moved most against the 28 days before? # 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-in Clicks per query across two 28-day windows, for queries with 50 or more impressions and a 20% change. [nuxtseo.com](https://nuxtseo.com) · 2026-08-22 to 2026-09-18, 12 of 205 rows · captured 2026-09-22 Example Movers and shakers rows from nuxtseo.com | 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 [**Continue with Google **](https://gscdump.com/auth/google) HostedRead-only Search Console scope. Free during beta. or ``` 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: "", reportId: "movers", comparison: "prev-period" }` [Connect with MCP](https://gscdump.com/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.** The page moved and the clicks followed. Note the date of any change you made to it. - **Clicks down, position steady.** The rank held and the clicks did not. Search volume fell, or a new results page feature took the clicks above your row. - **Clicks down, position down.** The page lost rank. Compare it with the pages now above it, and check Google's Search Status Dashboard for an update in the window. - **Most rows in one table.** A site-wide swing points at something site-wide: a Google update, a template change, a redirect, or a robots change in the window. ## Common questions A query whose clicks changed by 20% or more between the last 28 days and the 28 days before, with at least 50 impressions. Rising and declining rows are listed separately. Clicks in the recent 28 days against clicks in the previous 28 days, as a percentage. Position change is the previous average position minus the recent one, so a positive number means a higher rank. Yes. When search volume for the query grows, clicks can rise even as the average position slips. The two columns move independently. The query had no rows in the previous 28 days, so there is no baseline position to compare against. Google reports with a 2-3 day delay, so the last days of the recent window may still be filling in. The query uses whatever the record holds at run time. ## **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 whose CTR sits below the benchmark for their position, ranked by the click 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. [**Join the waitlist **](https://gscdump.com/#get-access) [**Connect with MCP **](https://gscdump.com/mcp) ## Sitemap See the full [sitemap](/sitemap.md) for all pages.