Diagnose Local Landing-Page Cannibalisation With Query and Page Evidence

When two pages receive impressions for similar searches, teams sometimes conclude that they are competing against each other and delete one. That response may remove useful content without solving the underlying problem. Search Console can show which queries and pages receive recorded visibility, but overlap by itself does not prove harmful cannibalisation. This guide lays out a cautious diagnostic process for deciding whether two local pages serve the same intent or deserve to remain separate.

Treat overlap as a clue, not a verdict

Export query-page data for the relevant date range and compare the pages that appear for the same query themes. Check clicks, impressions, CTR, and average position together, while remembering that aggregated metrics can conceal differences in country, device, and result context. Two pages appearing for one phrase may reflect different intents, changing results, or a useful set of alternatives. The first task is to understand what each page is designed to answer.

Map the pages to customer intent

Write a one-sentence purpose for each URL. One page may explain a service; another may describe coverage in a particular town. Compare headings, unique information, calls to action, internal links, and actual business availability. If the pages answer distinct questions, query overlap may be acceptable. If both promise the same service in the same area with nearly identical information, the site may be creating unnecessary choice for users and search engines.

Inspect the timeline and technical signals

Compare periods before assuming that a recent decline was caused by the second page. Review publication and update dates, canonical tags, redirects, index status, internal links, and any template changes. A canonical or indexing issue can resemble a content problem. Keep a change log so a technical release is not mistaken for a ranking effect. Search Console data is evidence about recorded search performance, not a complete explanation of why a page was selected.

Choose among retain, differentiate, consolidate, or redirect

Retain both pages when their purposes are genuinely distinct and each serves a user need. Differentiate them when the subject is valid but the content or navigation makes the distinction unclear. Consolidation may be appropriate when two URLs substantially duplicate the same task, provided the surviving page can satisfy the combined need. Redirect only after checking backlinks, user pathways, business requirements, and the likely loss of unique information. Document why the chosen action is appropriate.

Evaluate without promising a quick result

Record the target query group, affected URLs, change date, and evaluation period. Compare relevant metrics afterward, but account for seasonality, demand, site-wide changes, and data delays. Do not use one short-term movement as proof that the diagnosis was correct. If traffic falls, check whether the new page still satisfies the former page's intent and whether a redirect or canonical was implemented properly. The outcome may require more than one observation cycle.

Worked example

Hypothetical example: a clinic has a page for a named treatment and another for treatment availability in a nearby town. Similar queries appear in both reports, but the pages answer different questions. The audit retains both and improves their purpose statements and cross-links.

Preserve useful query-level detail

A page-level total can hide that one URL serves branded searches while another serves service research. Keep query and page dimensions in the working export when available, and review the strongest examples manually. Avoid publishing sensitive or unnecessary raw search data; use the minimum detail needed for the diagnosis.

Plan for redirects and external references

Before retiring a URL, check internal links, known external links, and any customer materials that may still point to it. A redirect should lead to a page that genuinely fulfils the old destination's purpose. If no close replacement exists, reassess whether consolidation is the right choice rather than redirecting automatically.

Frequently asked questions

Does query overlap prove cannibalisation?

No. It triggers investigation but cannot establish harmful competition on its own.

Should I merge every page with similar keywords?

No. Decide based on intent, unique usefulness, technical signals, and the actual evidence.

How soon should results be judged?

Choose a period appropriate to the site's traffic and normal variation; state that window before evaluating.

Decision rule

Decision rule: do not delete a page until you can explain the duplicate user need, identify the replacement destination, and check the technical consequences.

## Make the diagnosis falsifiable

Write down what evidence would show that the suspected overlap is not harmful. Perhaps the pages serve different query modifiers, attract different devices, or lead to distinct conversions. Check examples that could disprove the initial theory before deciding to merge anything. This practice prevents a common mistake: treating any shared query as proof that one URL is damaging another. If the evidence remains mixed, make a smaller content or navigation change first and monitor it rather than immediately removing a page that may be serving a legitimate audience.

Evidence to retain

For the cannibalisation diagnosis, save the query-to-URL evidence and the reason for the final retain, differentiate, consolidate, or redirect decision.