Keyword Cannibalisation: Find Competing Pages With Search Console and AI
Published October 14, 2026 · Written by Aanart
Contents
- 1What does keyword cannibalisation look like?
- 2Retrieve queries and pages together
- 3Compare the same query across two periods
- 4Check the page purpose and indexed version
- 5Choose a fix that matches the evidence
- 6Use internal links to explain the relationship
- 7Record the change and measure what follows
- 8Prevent overlap in the next content brief
Keyword cannibalisation happens when pages on the same website overlap in search intent and weaken the site’s organic performance. Investigate it when the page you intend to rank loses visibility, another similar page takes its place, and the combined results weaken.
Two URLs receiving impressions for the same query are a starting point for investigation. They can also serve different questions, formats or stages of a purchase.
SourcetoMCP connects Google Search Console to your AI assistant. You can retrieve query-and-page performance, compare periods and inspect Google’s recorded canonical choices before deciding what to change.
What does keyword cannibalisation look like?
A possible problem is two guides that both promise the same campaign reporting template, cover the same instructions and target the same reader. Your assistant can flag their overlapping search queries, but you still need to compare the actual pages.
A setup guide and a pricing guide for the same product answer different questions. Sharing some queries does not make either page redundant. Ahrefs also distinguishes harmful overlap from multiple pages that rank usefully for different searches. Ahrefs’ keyword cannibalisation guide.
On SourcetoMCP, our Claude Code marketing review explains a specific client workflow. Our AI marketing agents guide compares ways to run an agent and choose a workflow. Their related subject matter supports a contextual link, while each page retains its own purpose.
Record the question each page answers, the reader it serves and the next action it supports. This gives you something concrete to compare with the search data.
Retrieve queries and pages together
Start with a complete reporting period and a consistent country, device and search type. Use Web search for an ordinary article review.
Ask your assistant:
Retrieve Search Console performance for [property] for [complete dates], grouped by query and page. Show clicks, impressions, CTR and average position. Find queries associated with more than one returned URL. Keep the original URLs. State the filters, dates and number of rows. Label these as overlap candidates and make no changes.
SourcetoMCP supports query and page dimensions together, exact-query filters and date breakdowns. The current operation returns a maximum of 1,000 rows per request.
Google’s API returns top rows and does not guarantee every possible row. A result below the connector’s cap still does not prove complete coverage. Narrow the scope around a candidate query when you need to investigate it. Search Analytics API documentation.
For a wider set of search investigations, use the ChatGPT for SEO workflows.
Compare the same query across two periods
A change in which URL receives clicks becomes more useful when you compare suitable periods.
Filter to the exact query [query]. Retrieve page-level results separately for two equal-length complete periods using identical country, device and Web-search settings. Then retrieve page-by-date results for the same query to investigate when the change occurred. Preserve each report’s scope and flag incomplete results.
SourcetoMCP allows up to three dimensions in a performance request. Keeping the exact query as a filter and using page plus date for the time series helps contain the number of rows.
Consider this hypothetical example for “campaign reporting template” across two 28-day periods:
| Page | Earlier clicks | Later clicks | Earlier average position | Later average position |
|---|---|---|---|---|
| Campaign reporting template | 180 | 100 | 7.2 | 10.1 |
| Weekly campaign report template | 20 | 80 | 18.3 | 9.6 |
The first page lost 80 clicks, or approximately 44.4%. The second gained 60 clicks. Together, these two returned pages went from 200 clicks to 180, a 10% decline.
That pattern deserves investigation if the pages answer the same question. It does not establish that overlap caused the decline. Search demand, competing results, page changes and seasonality can also affect it.
Use Google’s returned average position for each row. Avoid averaging positions or CTR across page rows, and avoid presenting page-grouped impressions as a deduplicated query total.
Check the page purpose and indexed version
Search Console performance does not supply the full page text. Provide your assistant with the current copy, titles and headings, or inspect the pages using an available browsing tool.
Ask:
Compare these two page texts with the query and period data. Identify the question each page answers, duplicated sections and differences that justify separate pages. Explain whether the evidence supports leaving them separate, changing their focus or considering consolidation. List what remains uncertain.
Next, inspect the URLs through Search Console:
Inspect these candidate URLs. Return the indexing verdict, Google-selected canonical, declared canonical and last crawl time where available. Explain any discrepancy without assuming that it proves keyword cannibalisation.
The URL Inspection API reports information about Google’s indexed version. It cannot perform a live indexability test. Check the current page as well, especially after recent changes. Google’s URL Inspection API documentation.
Choose a fix that matches the evidence
| What you find | Action to consider | What to verify |
|---|---|---|
| Pages answer distinct questions | Keep both and make their purposes clearer | Titles, headings, copy and internal links match each purpose |
| Pages substantially duplicate the same useful answer | Consolidate the useful material into a chosen page | Content, links and business purpose justify the destination |
| Duplicate or very similar versions must remain accessible | Review a consistent canonical preference | The URLs really represent equivalent content |
| The intended page gives an incomplete answer | Improve its relevant sections | The missing information addresses the searcher’s question |
If you retire a page after consolidation, a permanent redirect to the relevant replacement helps users and search engines find it. Google documents 301 and 308 redirects as permanent methods. Google’s redirect guidance.
Canonical preferences apply to duplicate or very similar pages. They are not a general solution for articles that answer different questions. Google treats canonical annotations as a preference when choosing a representative URL. Google’s canonical guidance.
SourcetoMCP can support the investigation with Search Console reports and URL inspection. Applying redirects, canonical tags or page edits requires your website’s publishing tools or developer workflow.
Use internal links to explain the relationship
Link to the page that answers the reader’s next question, using anchor text that describes that answer.
A competitor-research article can link to a cannibalisation investigation when the reader is deciding whether a keyword gap needs a new page. A reporting template can link to the same investigation when several URLs appear for one query.
You can also distinguish broad guides from specialised follow-ups. For example, link a general SEO workflow to a detailed query-and-page check rather than duplicating the full process in both articles.
Before writing a new article from a keyword gap, compare it with your current content. Our competitor keyword analysis guide covers the external comparison. The workflow here checks overlap within your own site.
Record the change and measure what follows
Save the candidate query, page URLs, reporting filters, findings, proposed action and actual implementation date. The SEO report template provides a place to record findings and next actions.
After a change, check whether Google has crawled the affected URLs and compare performance over suitable complete periods. Review the intended page, the other candidate pages and the relevant query group.
If you also examine website behaviour, keep Search Console clicks separate from GA4 sessions and outcomes. Our Search Console versus Google Analytics guide explains that comparison.
Avoid declaring success solely because one page’s clicks increased. Check whether the results you wanted improved and whether other relevant pages lost useful traffic.
Prevent overlap in the next content brief
Before approving a new article, record its main question, target reader, existing related pages and proposed internal links.
Ask your assistant to explain why the new page deserves a separate URL. Where an existing page already answers the same question, investigate an update before creating another closely overlapping guide.
Connect Search Console through SourcetoMCP, retrieve one query-and-page sample and investigate the first pair of pages whose purpose and performance justify a closer look.