Keyword cannibalisation: when to merge overlapping pages

What keyword cannibalisation is, and when overlap is fine

Keyword cannibalisation is the SEO industry's name for two or more pages on one site chasing the same search. You end up with two half-strong pages instead of one strong one, and Google keeps swapping which of them it shows. Content cannibalisation is the wider version: pages that cover the same topic for the same reader, even when each targets slightly different wording.

Picture a pest control business on the Sunshine Coast with a page called Termite inspections and another called Pre-purchase termite checks, written two years apart. Both answer the same questions for the same homeowner. One ranks for a few weeks, then the other takes over. Neither holds a spot for long.

Google's canonicalisation guide explains part of the pattern. When pages look the same or have very similar main content, Google picks one as the canonical, crawls it most regularly and crawls the duplicates less often. The page it picks isn't always the one you'd choose. The same guide says some duplicate content on a site is normal and isn't a violation of Google's spam policies, so this is a housekeeping problem, not a punishment.

Overlap on its own is fine. Search the phrase yourself and read page one. If Google shows a mix of guides and service pages, it reads the search as mixed intent, and a guide plus a service page from your site can both belong. If page one is all service pages, a guide of yours showing up is the warning sign. Several of your pages appearing for your business name is normal too.

How overlapping pages appear on small local sites

Most overlap on a local business site isn't planned. It builds up as different people add pages over the years without checking what already exists.

Rule out technical duplicates before you touch any content. Some apparent cannibalisation is really one page reachable at several addresses. Google's canonicalisation guide lists protocol variants (the HTTP and HTTPS versions of a site), site functions such as sorting and filtering, and a demo version accidentally left open to crawlers among the usual reasons for duplicate URLs. On a local site, check that only one of http and https, and www and non-www, loads (redirect the others site-wide to one version), that the trailing-slash and non-slash forms of a page don't both load, that links tagged with tracking parameters, such as a tagged Business Profile website link, point a canonical at the clean URL, and that any staging copy of the site sits behind a login. These need a redirect or canonical fix, not a content merge.

Once the technical duplicates are gone, look for the content causes below.

• A rebuild or redesign put pages on new URLs and left the old ones live without redirects, so two versions of each service page now compete.
• Two writers, or the same writer years apart, wrote about the same service under different titles because there was no record of which page already owned the search.
• Suburb pages were made by copying one template and changing the place name.
• A blog post or guide was written around a booking search, such as a suburb plus a service, instead of a question, so it now competes with the service page.
• Google Ads landing pages were left indexable and linked from the menu, so they compete with the page they were copied from.
• Internal links use the same anchor text, such as the service name, to point at two different pages, which tells Google both pages are about the same thing.

Gather the query evidence first

Don't merge on a hunch. Run two quick triage checks, then confirm with Search Console's Performance report.

For triage, search Google for site: followed by your domain and the phrase, such as site:example.com.au termite inspection. Treat this as a prompt, not proof: Google's documentation for the site: operator says it doesn't necessarily return every indexed URL. Then run a site crawler and sort by title and H1. Pages with near-identical titles or headings are your shortlist.

Read the Search Console numbers with two cautions from its help pages. The chart counts impressions by property, so when two of your pages appear for one search the chart counts one impression, while the Pages table credits each page. And filtering by query or URL can leave out anonymised queries, so filtered totals won't always match the unfiltered chart.

One more trap. Search Console assigns most performance data to the canonical URL, so if Google has already folded one page into the other, the weaker page may barely appear. That's a clue in itself, and the URL checks in the next section confirm it. With those cautions in mind, it only takes a few filters.

1. Set the date filter to Last 16 months. Google's guide to debugging traffic drops suggests this view, and it stops a seasonal dip passing for a cannibalisation problem.
2. Add a query filter for the search you're worried about, such as termite inspection, then open the Pages tab. A Queries containing filter matches every search that includes the phrase, so each URL listed earned impressions for that search or a longer one, such as termite inspection cost.
3. Flip it around. Filter by each page's URL in turn, open the Queries tab and export both lists.
4. Line the exports up side by side and mark the queries on both lists. A few shared long-tail searches mean little. Shared core searches that carry most of each page's clicks mean a lot.
5. Put the query filter from step 2 back on and leave it there. Then add a Page filter set to Compare with both URLs, so each line on the chart counts only searches containing that phrase. Search Console's help says you can filter by more than one dimension at once and run one comparison at a time. If one page's impressions climb whenever the other's fall over the same months, Google is likely swapping them for that search.

Check the URLs and choose the keeper

Query data shows the pages compete. URL evidence shows which one should survive. Run each page through the URL Inspection tool and read two lines: the user-declared canonical and the Google-selected canonical. Search Console's help notes that Google sometimes chooses a different URL from the one you declared. If Google names page A as the canonical for page B, it's already treating them as duplicates.

The Page indexing report shows the same thing across the whole site. Look for pages listed under "Duplicate, Google chose different canonical than user" or "Duplicate without user-selected canonical" and check whether they overlap with another page.

Before you choose, list every place each URL is used: menus, internal links, your Google Business Profile website link, Google Ads final URLs, directory listings and links from other sites. The keeper is usually the page with more of those and more enquiries. If Google already treats one page as the canonical, lean towards keeping that one.

When the numbers are close, keep the page that is more current and accurate, and the one with the cleaner, more general URL. A page called /termite-inspections/ outlives one called /termite-special-2022/. Then carry the older page's unique details across before you redirect it, so nothing useful is lost.

Choose the fix: merge, separate, canonical or leave alone

Not every overlap ends in a merge. Match the fix to what the evidence showed. Suburb pages are the common local case: two pages for neighbouring suburbs can both earn their place when each carries real local detail, and when only the suburb name changes they're far more likely to compete. The guides on service area pages and when local landing pages deserve indexing cover that test. Google's spam policies describe doorway abuse as pages created to rank for specific, similar search queries, and list pages targeted at specific regions or cities that funnel users to one page as an example, so near-identical suburb pages need consolidating without delay.

Google's guide to consolidating duplicate URLs ranks the tools: a redirect is a strong signal that its target should become canonical, a rel="canonical" link is also a strong signal, and listing a URL in your sitemap is a weak one. It adds that these signals stack when combined. None of them is a command, which is why the verification steps later in this guide matter.

When both pages stay, separate them with internal links. Google's link guidance says good anchor text is descriptive, reasonably concise and relevant to the page it links to, and warns against generic anchors such as read more. If every link says termite inspections, whichever page it points to, change the service page links to book a termite inspection in Caloundra and the guide links to what a termite inspection checks. The guide on linking regional hubs and suburb pages covers this across a local site.

Avoid these mistakes, which tend to make the problem worse.

• Redirecting retired pages to the home page. Google's site move guidance warns against redirecting many old URLs to one irrelevant destination and names the home page as the example.
• Using noindex or robots.txt to settle the overlap. Google's canonical guide says not to use robots.txt for canonicalisation, and that noindex blocks a page from Search completely. The guide to noindex, canonical tags and redirects explains when each one fits.
• Deleting a page without checking its links and enquiries first.
• Adding a canonical between two pages that do different jobs, instead of rewriting them so each one is clearly different.
• Merging a guide into a service page, or the reverse, when the evidence showed they serve different searches.
• Leaving redirect chains, where an old URL redirects to the retired page, which then redirects to the keeper.

Merge, redirect and verify

Work through the steps in order and expect some wobble. Google's traffic-drop guide says changing URLs can bring ranking fluctuations while Google recrawls and reindexes.

No one can guarantee the merged page will beat the two old ones, so keep a short log: old URL, keeper, date, reason, and the before and after numbers. If the keeper still trails months later, that log shows whether the merge or something else is to blame. For merges that are part of a bigger rebuild, see website migration and SEO handover.

1. Pick the keeper and leave its URL alone. Moving both pages to a fresh address gives Google two changes to process instead of one.
2. Bring across what the other page did well: answers people searched for, photos, local detail and useful FAQs. Rewrite them into the keeper so it reads as one page with one voice, and check the shared queries from your export are now answered on it.
3. Add a permanent, server-side 301 redirect from the old URL to the keeper. Google's canonical guide names redirects as the method for getting rid of existing duplicate pages, and its redirect documentation says Google uses a permanent redirect as a signal that the target should be canonical.
4. Point straight at the final URL. Google's site move guidance advises redirecting to the final destination directly, so if older URLs already redirect to the page you're retiring, update them to point at the keeper.
5. Update everything that points to the old URL: internal links, menus, the XML sitemap, your Google Business Profile website link, ad final URLs and any directory listings you control. Google's site move guidance asks for internal links and sitemaps to use the new URLs.
6. On the day: load the old URL and confirm it reaches the keeper in one hop with a 301 status. Your browser's developer tools or a site crawler will show it. Then run Test live URL on the keeper in URL Inspection.
7. Over the next few weeks: the old URL should move to Page with redirect in the Page indexing report, which Search Console describes as a non-canonical URL that redirects and won't be indexed. URL Inspection on the keeper should show it as the Google-selected canonical.
8. Once things settle: filter the Performance report by the target query and open the Pages tab. Impressions should now gather on the keeper. Search Console's help suggests weekly or monthly granularity when comparing date ranges, which smooths out day-of-week swings.
9. Check enquiries as well as rankings. Compare calls and forms from the keeper with what both pages produced before. The guide to call tracking and conversion reconciliation shows how to line those numbers up.
10. Leave the redirect in place. Google's site move guidance says to keep redirects for as long as possible, generally at least a year.

Worked example: a Caloundra pest control business

This example is hypothetical; the business and pages are made up. Say a pest control business in Caloundra has three pages about termites: a Termite inspections service page, a Pre-purchase termite checks page from an old campaign, and a guide titled Termite inspection Caloundra: what to expect. Website calls have flattened and the service page seems to come and go in search.

Step one is the technical check. The site loads only on https with no www, and the trailing-slash forms redirect, so this is a content problem. A site: search for the domain and termite inspection lists all three pages, which gives the shortlist.

Step two is the query evidence. Over the last 16 months, a query filter for termite inspection shows all three URLs in the Pages tab. The exports show the service page and the pre-purchase page share most core searches, while the guide earns question searches plus some Caloundra booking searches. Comparing the service page and the guide with the query filter on shows their lines crossing month to month.

Step three is the URL evidence. URL Inspection on the pre-purchase page shows Google has selected the Termite inspections page as its canonical. The service page is also the one linked from the menu, the Business Profile and directory listings, and call tracking shows most termite calls start there. It is the keeper.

Step four is the decision. The pre-purchase page does the same job for the same customer, so it is merged: its section on what buyers should ask before settlement moves into the service page, and the old URL gets a 301 to the keeper. The guide does a different job, so it is separated. Its title and H1 become What a termite inspection checks, the suburb is dropped, and a link near the top sends readers ready to book to the service page. Every internal link that said termite inspections now points only at the service page.

Step five is verification. The owner logs the change, confirms one 301 hop, and checks the Page indexing report until the pre-purchase URL shows as Page with redirect. Once the data settles, the Pages tab shows the service page carrying the Caloundra searches and the guide keeping its question searches. Calls are compared with the same months last year, because termite work is seasonal.

Step six stops the problem coming back. The owner starts a keyword map, one row per search the business cares about, and checks it before any new page goes live. The rule is one search, one job, one URL. Before publishing, ask four questions: does a page already answer this search, is the new page doing a different job, which existing page will link to it and with what anchor, and does the map need a new row. A local SEO plan should keep this map current as services and suburbs are added.