Check page overlap before publishing
Two pages can receive impressions for the same query without harming each other. Check the evidence before changing either page.
Describe the proposed topic
Use a short topic or URL slug that matches the planned page. The pre-publish Report needs --topic.
Run the pre-publish Report
gscdump report pre-publish --site example.com \
--topic 'running shoes' --period 90d --jsonRead its cannibalization and striking-distance Sections. Check each Section's coverage and source. If the Store covers only some dates, run the printed sync command. Live results may omit low-volume query detail.
Check shared queries
gscdump analyze cannibalization --site example.com --period 90d --jsonThe Analyzer finds query overlap among pages in this Site. Use the Analyzer reference to check source support. For one query, inspect page rows:
gscdump query --site example.com --type web \
--query 'running shoes' --dimensions page,query --format tableKeep the same 90-day window with --start and --end. The query guide explains row filtering.
| Evidence | Possible action |
|---|---|
| One existing page answers the same need | Improve that page before creating another. |
| Pages serve distinct needs | Make each page's purpose clear. |
| Data is sparse or partial | Gather more evidence before changing structure. |
Decide whether to update or publish
Record the existing pages, shared queries, and proposed reader need. Shared queries alone do not prove harm. If a live page lost traffic, use Traffic drop. More URL checks: Check visibility.