---
title: "Fixing keyword cannibalization: merge, differentiate, or noindex"
slug: "cannibalization-fixes"
category: "seo"
tags: ["seo", "cannibalization", "redirects", "noindex", "canonical", "intent"]
status: "stable"
last_updated: 2026-09-27
summary: "Pick the fix for two pages competing on one query: merge with a 301 when intents match, sharpen each page when intents differ, noindex a non-search page, and never use rel=canonical between editorial pages."
related: ["[[seo/cannibalization]]", "[[seo/content-pruning]]", "[[seo/redirects]]", "[[seo/internal-linking]]", "[[seo/structured-data]]", "[[glossary/canonical-url]]", "[[seo/indexnow]]"]
---

## Overview

Fix a confirmed cannibalization case by matching the remedy to the overlap. Two pages with the same intent get merged; two pages with different intents get sharpened apart; a page that exists for navigation or a campaign gets a noindex tag. This page assumes the conflict is already detected with the Search Console check in [[seo/cannibalization]]; for pruning decisions beyond a two-page conflict, see [[seo/content-pruning]].

## Fix by merging when the pages overlap substantially

If two pages cover the same intent with overlapping content, merge them. This is the most common fix.

- Pick the stronger page based on backlinks, current position, and content depth.
- Move the unique content from the weaker page into the stronger page.
- 301 the weaker URL to the stronger URL. Do not 404; the inbound links carry ranking signal.
- Update every internal link that pointed at the weaker URL to point at the stronger one directly. Google has said 301s do not lose PageRank, but direct links avoid a redirect hop for users and crawlers. See [[seo/redirects]] and [[seo/internal-linking]].
- Re-submit the stronger URL through the sitemap `lastmod` and through IndexNow.

Expect the merge to take weeks to settle while engines recrawl and reprocess both URLs. Neither engine publishes a timeline, and the combined page is not guaranteed to capture the sum of both pages' clicks.

## Fix by differentiating intent when the pages serve distinct purposes

If the two pages overlap on keyword but serve different intents (one informational, one commercial; one tutorial, one reference), the fix is to sharpen each page toward its intent.

- Rewrite each H1 and first paragraph to make the intent unambiguous. "How postgres indexes work" (informational) vs "Postgres index management for production teams" (commercial).
- Use structured data that matches each page's visible content, such as `Article` on the tutorial and `Product` or `Service` on the commercial page. Markup helps page understanding; it does not by itself separate intents. See [[seo/structured-data]].
- Cross-link explicitly: the informational page links to the commercial page with anchor text that signals the intent shift ("hire a team to do this" or "production setup guide").
- Track each page against its own keyword, not the shared one.

This fix is harder than a merge and slower to take effect, but it preserves two pages where two pages are warranted.

## Fix with noindex only when the weaker page serves an internal purpose

If one of the two pages exists for internal navigation, a campaign landing page, or a non-search purpose, noindex it.

```html
<meta name="robots" content="noindex,follow" />
```

Examples that warrant noindex: a category page that exists for site navigation but should not compete with the main pillar page, a thin tag archive, a duplicate page for email-campaign tracking. The `follow` keeps the page passing link equity to its outbound links; the `noindex` removes it from the competition.

## Avoid canonical between editorial pages

Do not use `rel="canonical"` between two competing pages on the same site. Canonical is for duplicate URLs of the same content (parameter variants, protocol variants). Pointing one editorial page's canonical at another editorial page loses the long-tail traffic on the second page and does not consolidate the way 301 does.

## Common errors

- Solving cannibalization with `rel="canonical"` between pages. Canonical is for URL duplicates, not for editorial deduplication. Long-tail traffic on the canonicalized page dies.
- Merging without a 301 redirect. A 404 on the old URL throws away every inbound link. Always redirect.
- Assuming the page Google ranks is the page you want to rank. Sometimes the older, weaker page outranks the newer, better one. Decide which page should win by content quality, not by current position, and merge in that direction.

## Related

- [[seo/cannibalization]]
- [[seo/content-pruning]]
- [[seo/redirects]]
- [[seo/internal-linking]]
- [[seo/structured-data]]
- [[glossary/canonical-url]]
- [[seo/indexnow]]