detect_cannibalization
Detect keyword cannibalization from your latest Search Console pull: queries where two or more of your pages meaningfully compete for the same query…
Cost: 10 credits.
detect_cannibalization reads your latest pull_gsc_data and finds keyword cannibalization: queries where two or more of your own pages each pull a meaningful share of the impressions, splitting the ranking signal. Consolidating or clearly differentiating those pages usually lifts the query. Run pull_gsc_data first.
What it does
From the pull's current window, it groups rows by query and flags a query when two or more of its pages each clear both floors: at least 10 impressions and at least a 10% share of that query's impressions. A dominant page plus a negligible straggler is not flagged — only genuine competition. Groups are ordered by total impressions, biggest query first.
Example
Ask your MCP client in plain language:
Do I have any keyword cannibalization on example.com?
Input
| Field | Type | Required | Description |
|---|---|---|---|
project_id | string (uuid) | Yes | The project to analyze (must have run pull_gsc_data first). |
Returns
A list of cannibalized queries, each with its competing pages and their impressions, clicks, and average position (main contender first). If no query is contested, it says so (and you are still charged for the delivered analysis).
find_quick_wins
Find quick-win keyword opportunities from your latest Search Console pull: queries ranking in positions 8–20 with enough impressions to be worth a push…
analyze_content_decay
Find decaying pages from your latest Search Console pull: pages whose clicks dropped meaningfully (absolute and proportional) vs the previous window…