Index of every page on this site: llms.txt
Skip to content

Review search traffic each week

Use a repeatable window so a new, incomplete Search Console day does not look like a drop.

Choose two complete weeks

gscdump report movers --site example.com --period 7d --vs prev-period --explain

Check the dates in the plan. Stored Reports end on the newest synced day. Live Reports end three days ago in Google's Pacific reporting calendar. If the Store covers only part of either week, the CLI prints a sync command. Build history before comparing.

Run the movers Report

gscdump report movers --site example.com --period 7d --vs prev-period --json

The result has Sections for changed queries and pages, decay, and near-ranking opportunities. Each Section has its own coverage and findings. Check meta.degraded and partial-data warnings before treating a missing finding as no change. The Reports reference lists all Sections and window options.

Check the rows

Choose one changed page from the Report. Keep its Site and search type. Query that page for the same current dates, then the previous dates:

gscdump query --site example.com --type web --page /blog/post \
  --start 2026-08-15 --end 2026-08-21 --dimensions date,page --format table

Replace those dates with the Report window. Check clicks, impressions, and position together. A Report finding is a lead, not a cause. The query guide explains filters and source metadata.

Pick a follow-up

SignalNext check
One page lost clicksInvestigate a page drop.
Impressions held while clicks fellCheck low CTR.
Brand mix changedSeparate brand traffic.
Several months changedCheck growth trends.

Other questions: Investigate traffic.

Run this with an agent

Install the gscdump agent skill, then adapt this prompt to your Site.

Use the installed gscdump skill. Ask which Site to review. Compare two complete weeks with the movers Report. Check a changed page against source rows. Show dates and uncertainty.