Investigate a page traffic drop
Start with the page and two matching windows. A drop in clicks alone does not identify its cause.
Confirm the drop
Use a page from weekly triage. Replace the dates below with equal, complete windows from its Report.
gscdump query --site example.com --type web --page /blog/post \
--start 2026-08-01 --end 2026-08-14 --dimensions date,page --format table
gscdump query --site example.com --type web --page /blog/post \
--start 2026-08-15 --end 2026-08-28 --dimensions date,page --format tableCheck whether clicks, impressions, or both moved. Read meta.source in JSON output when comparing saved and live runs. The query reference explains source routing.
Run page triage
gscdump report triage --site example.com --target /blog/post \
--target-kind page --period 90d --jsonThe triage Report checks change points, query movement, and position volatility. These Analyzers need a Store. If coverage is incomplete, the CLI prints a sync command. Check Section coverage before reading an empty result. See Reports.
Check query changes
gscdump query --site example.com --type web --page /blog/post \
--start 2026-08-15 --end 2026-08-28 \
--dimensions page,query --limit 100 --format csv --output current-queries.csvRepeat for the prior window. Check queries that lost impressions, lost position, or moved to another page. Google can omit some query detail. If two pages share queries, use page overlap before deciding which page to edit.
Check Indexing Evidence
If the page disappears from search, inspect the URL. Compare the observation date with the traffic window. A crawl or indexing observation does not explain every click change.
Choose the next check
Falling impressions with stable CTR suggest a visibility or demand question. Stable impressions with falling CTR suggest a search result review. A position change suggests ranking movement. Record the observed signal and a testable next step. Do not label a cause from one metric.