Keyword Cannibalization Check

Identify queries where multiple pages on the same site are competing for rankings.

Steps

1. Call list_properties to confirm the exact site_url.
2. Prefer gsc_build_cannibalization_decision_queue for the requested date range. Use defaults unless the user asks for different thresholds.
3. Treat the returned queue as a top-row Search Analytics sample, not all query+page combinations.
4. Review candidates where a query has two or more distinct pages in the returned rows.
5. For each case, use the queue's page metrics, winning-page heuristic, losing pages, impact score, confidence, warnings, limitations, and provenance.
6. Sort and prioritize using the returned action item order unless the user asks for a different view.
7. If the new queue tool is unavailable, fall back to get_advanced_search_analytics with dimensions=query,page and row_limit=500 or the highest supported row limit, then group by query client-side.

Output format

For each cannibalization case:

• Query: the competing keyword
• Pages: list each URL with its metrics
• Severity: High / Medium / Low based on impressions at stake
• Recommendation: explain the queue's winner heuristic, then require manual SERP, business-intent, canonical, internal-link, and conversion review before suggesting consolidation, content updates, canonicals, redirects, or merges

Present as a markdown table followed by a prioritized action list.

Note: This is a sampled diagnostic based on the rows returned by Search Analytics. It can reveal likely cannibalization, but it is not proof and is not a guaranteed complete export of every competing page for every query.