Two of Your Blog Posts Are Fighting for the Same Search: How to Find and Fix Keyword Cannibalization

Greg — Fri, 13 Nov 2026 10:54:53 +0000

Disclosure: written by the team behind BlogWorkflow, an SEO article writer. This post was drafted with AI assistance and contains no product pitch.

If you have kept a technical blog for a year or two, there is a good chance you have written the same post twice without noticing. One year it was "Setting up ESLint in a monorepo", the next it was "ESLint config for workspaces". Both are decent. Both target the same search. And instead of one strong page, Google now sees two half-strong pages and keeps swapping which one it shows.

That pattern is usually called keyword cannibalization. It is not a penalty, and Google does not punish you for it. The cost is quieter: links, clicks and attention are split across two URLs, and neither one ends up as the obvious best answer. This post shows how to find it with free tools and how to pick the right fix.

What it looks like in practice

The symptoms are easy to misread as "SEO is random":

A post that used to rank steadily now jumps around from week to week.
Search Console shows two or more of your URLs getting impressions for the same query.
The page Google shows for a query is the older, weaker post, not the one you updated last month.
Readers land on a post and then click through to your other post on the same topic, because the first one did not fully answer them.

None of these alone proves cannibalization. Two pages ranking for a broad query can be perfectly healthy if they serve different intents. The question is always: would a reader searching this query be happy with either page, or does each page do a different job?

Step 1: Find candidate overlaps in Search Console

You need a verified property in Google Search Console. Then:

Open Performance → Search results and set the date range to the last 3 months.
Click + New → Query, choose "Exact query", and enter a query you care about (for example eslint monorepo).
Switch to the Pages tab.

If two or more of your URLs show impressions for that one query, write them down. Repeat for your ten or twenty most important queries. Google's help page on the Performance report explains how queries and pages are counted if the numbers look odd.

A quicker first pass for small blogs: search your own site with site:yourblog.dev eslint monorepo. If several posts come up with near-identical titles, you have candidates.

Step 2: Decide whether the overlap is real

Put each pair side by side and answer three questions:

Query: eslint monorepo
Page A: /eslint-monorepo-setup (2024)
Page B: /eslint-config-workspaces (2025)
Same reader? yes / no
Same intent? learn / fix / compare / set up
Could one replace the other? yes / no

If the reader and the intent are the same and either page could replace the other, the overlap is real. If Page A is a setup tutorial and Page B is a comparison of lint tools, they are different jobs and you should leave them alone, just link between them.

Step 3: Pick the fix

There are four fixes. Choose the lightest one that solves the problem.

1. Merge and redirect. Best when two posts cover the same thing and one is clearly better. Move anything useful from the weaker post into the stronger one, then send the old URL to the new one with a permanent (301) redirect. Google's guide to redirects and Google Search explains why a permanent server-side redirect is the clearest signal. Update your own internal links so they point straight at the surviving post.

2. Canonical tag. Use this when both pages must stay live (for example, a printable version or a copy syndicated on another platform) but you want one treated as the main version. Google's page on consolidating duplicate URLs covers when rel="canonical" is the right tool and why it is a hint rather than a command.

3. Differentiate. When both posts deserve to exist, make their jobs obviously different. Rewrite the weaker post's title, intro and headings around a narrower question ("ESLint flat config migration in a monorepo" instead of a second general setup guide), and cut the sections that duplicate the other post.

4. Re-point internal links. Sometimes the overlap is mostly caused by your own links: the old post gets linked from every new article, so it keeps looking important. Decide which page is the main one for the topic and make your internal links, navigation and "related posts" point there.

Step 4: Stop it from happening again

The cheapest fix is the one you never need. Before writing a new post, spend two minutes checking what you already have:

Keep a simple list of published posts with one column for the main query each post targets.
Before starting a draft, search that list and your own site for the new post's main query.
If an existing post already owns that query, update it instead of starting a new one, or give the new post a clearly different job.

If you want a fuller version of that pre-writing check, this guide on how to fix keyword cannibalization before it starts walks through a topic-to-URL map and a short dedup checklist.

A note on expectations

After a merge or redirect, give Google a few weeks to recrawl both URLs before judging the result. Rankings can wobble while it settles. The examples above (ESLint posts, the query and the URLs) are illustrative, not data from a real site; the useful part is the process, which works the same way for any topic on any blog.

Quick checklist

[ ] Listed my top queries and checked the Pages tab for each
[ ] Marked pairs where two URLs share the same reader and intent
[ ] Chose one fix per pair: merge + 301, canonical, differentiate, or re-point links
[ ] Updated internal links to the surviving or main page
[ ] Added a "main query" column to my list of published posts

DEV Community: Greg