Managed IT · October 6, 2026 · intSignal Team

When Two of Your Own Pages Compete for the Same Search

Share this article

Companies that sell both a platform and a service around that platform end up with page pairs. A product page for the thing you operate, and a service page for working on the customer's existing stack. Both legitimately about "managed SOC", "SIEM" or "network operations".

Both also target the same search term, and search engines pick one. Usually not the one you would have chosen, and the choice can change between crawls — which looks like ranking volatility and is actually your own pages trading places.

Decide it with data, not an opinion

The temptation is to reason from the site structure about which page ought to own a term. Don't. The data already says which page has traction, and that is a much better starting point.

Pull impressions, clicks and average position per URL for the competing term. Ours were unambiguous:

PageImpressionsAvg position
/products/managed-soc86462
/products/siem—26.6
/products/managed-noc21143.6
service-page counterparts0—

The product pages had all of the history. The service pages had none. Whatever the ideal architecture, one side of each pair had accumulated signals over years and the other had not.

So the product pages kept the head terms. That decision took ten minutes once the numbers were in front of us, and it would have been an unresolvable argument without them.

The loser gets a different job, not a deletion

This is the part usually got wrong. The instinct is to consolidate — redirect one into the other, "fix" the duplication. That throws away a page serving a different buyer.

The two pages answer genuinely different questions:

  • "I want a SOC. Can you provide one?" → the product page
  • "I already have a SIEM and nobody is watching it. Can you run it?" → the service page

Second search, second buyer, often a bigger one. So the service pages were retargeted rather than removed — retitled and rewritten around the stack the customer already owns:

  • head term → "Managed SOC"
  • retargeted → "SOC services for your existing stack", "co-managed SIEM", "we run the platform you already bought"

Now they compete for different searches, both rank for what they are about, and neither undermines the other.

Make the relationship explicit on both pages

Once the pair has distinct jobs, say so where a reader lands. We added a short block to both halves of each pair — two ways to buy this capability, with a link to the other:

Two ways to buy this. Use our platform, fully operated by our team — or keep the platform you already own and have us run it. Same outcomes, different starting point.

This helps a reader who arrived at the wrong one, and it tells a crawler that these are deliberately distinct pages rather than near-duplicates.

One warning from doing it badly first: check where those cross-links actually land. Our initial link from the product page pointed at an old service URL that 301s straight back to the product page — a circular link that sends a visitor nowhere, slowly. Point internal links at final destinations, not at redirects.

Confirm it worked

After retitling, watch for three things over a few weeks:

  1. The head term stabilises on one URL. The flip-flopping between your own pages stops.
  2. The retargeted page starts earning its own impressions on different queries. If it earns none after a couple of months, the new target is not a real search and the page needs a different job or an honest merge.
  3. Total impressions across the pair go up, not down. If they fall, you have narrowed coverage rather than divided it.

The checklist for finding these

Cannibalisation is easy to spot once you look for it:

  • group your search data by query and list queries where more than one of your URLs appears
  • flag queries where the ranking URL has changed between periods
  • compare page titles across the site for near-identical head terms
  • look for pages with impressions but a near-zero click-through — often a page ranking for something it does not actually answer, because a sibling page is the better match

Then for each pair, the same two questions: which page has the history, and what different job can the other one do? If there is no different job — if they really are the same page twice — that is when you consolidate, with a 301 and an internal-link sweep.

But check for the different job first. Most "duplicate" pairs are two real buyers that were never given their own page.

Share this article