A practical research workflow
A Manual Keyword Cannibalization Audit
Two URLs appearing for related queries is a signal to inspect, not proof that they harm each other. Diagnose the task and the evidence before choosing a consolidation or redirect.
By TopTrending · Reviewed
Collect comparable query–page evidence
- Export query–page performance for the same property, search type, country, device and date range. Keep the original export unchanged.
- Record indexing status, declared and selected canonical where available, page purpose and recent release changes. Search Console can omit anonymized queries, so totals may differ.
- Compare at least two comparable windows and inspect query-level trends. Do not merge average positions or use aggregate position as proof of a page conflict.
- Open each page. Determine whether the visitor needs the same output, a different step or a different audience.
This is a manual workflow. The review process below is informed by official Search Console and canonical documentation, checked October 29, 2026. TopTrending does not connect to your Search Console, crawl the site or automatically diagnose cannibalization on this page.
Work through three different overlap patterns
Fictional practice data: all counts below are invented for the exercise, not TopTrending analytics or a customer result. No before/after gain is implied.
| Query | Page A / impressions / clicks | Page B / impressions / clicks | Interpretation and next decision |
|---|---|---|---|
| feedback digest template | /blog/weekly-feedback-template · 240 / 8 | /templates/feedback-digest · 260 / 11 | Both pages provide the same worksheet; aggregate counts alone do not establish switching or lost clicks. Inspect content and query-level history; consolidation is a candidate, not a proven gain. |
| customer feedback software | /learn/product-feedback · 300 / 4 | /compare/customer-feedback-tools · 700 / 35 | Pillar explains a process; comparison evaluates products. Keep both tasks. Clarify titles and internal anchors; do not merge on shared words alone. |
| weekly product feedback digest | /feedback-digest · 380 / 22 | /learn/prioritize-feature-requests · 75 / 3 | The product and method solve adjacent tasks; occasional shared queries. Keep and differentiate. Link the prioritization method from the workflow. |
The first pair is a consolidation candidate because both deliver the same worksheet. Even there, inspect links, page history and comparable windows before deciding; the fictional counts do not establish lost clicks. The other pairs cover adjacent tasks and should not be merged merely because they share words.
Choose the treatment that fits the cause
| Condition | Action | Acceptance check |
|---|---|---|
| Different tasks, both useful | Keep pages; clarify scope, headings and internal link labels. | Each page completes its distinct task and points to the relevant next step. |
| Same task, weaker duplicate | Choose the strongest destination, combine useful unique material and consider a permanent redirect for the retired URL. | Destination delivers the full task; update links and sitemap; check redirect and indexability. |
| Duplicate representation must stay accessible | Consider canonical only when content is genuinely duplicate or near-duplicate and the technical situation warrants it. | Canonical target is indexable and consistent; do not use it to disguise different tasks. |
| Insufficient or incomparable data | Keep the hypothesis open; improve exports and record changes. | A later review uses the same filters and an explicit change log. |
Record the decision and review the outcome
Download the practice query–page data and the blank audit worksheet. Keep query, both URLs, filters, comparable periods, task overlap, evidence, action, owner, release date and review result.
For a real change, verify status codes, canonical, internal links and sitemap before release. Compare later data using the same scope, accounting for seasonality and other changes. Low traffic may leave the outcome inconclusive.
Use the topic-cluster page map to clarify ownership. Read Google’s Search Console performance documentation and canonical guidance for metric and duplicate-content limits.
Check your own seed keyword
Move from a proposed task to keyword evidence. Custom research follows the existing account and credit limits.