Two articles fighting for the same query is the silent tax on long-running content sites. Each page ranks at position 7-12 when one consolidated page would sit at 3-5. This tutorial uses AI to detect cannibalizing pairs across your library, then walks the merge-vs-differentiate decision per pair. Expect 30-60% of the flagged pairs to merit a merge, the rest a clean differentiation in title and intent. Wins show up in 4-8 weeks as the surviving URL climbs.
What this covers
A scriptable detection pass: pull queries each URL ranks for from Search Console, find URLs sharing primary queries, ask AI to classify each pair (merge / differentiate / leave alone), then act. Detection is the cheap part; the decision is where AI helps most — it can read both articles and propose the merged outline or the differentiation angle in seconds.
Who this is for
Content sites with 300+ articles, especially those that have grown organically over 2+ years without an editorial taxonomy. SEO managers running a quarterly hygiene pass. Indie operators who suspect their old posts are competing with new ones but cannot prove it. Skip on sites under 100 articles — cannibalization at that scale is rare.
When to reach for it
Quarterly maintenance, after a Google update that shuffled rankings (cannibalization gets exposed when search shifts), when launching a new pillar that overlaps an old one, or when a specific keyword you target is stuck at page 2 despite multiple articles ranking for it.
Before you start
- Connect Search Console and export 90 days of query-to-URL data. Without real query data, AI guesses at cannibalization from titles alone, which is unreliable.
- Define your merge threshold: typical rule is two URLs sharing 3+ queries with overlapping intent, both ranking on page 1 or 2.
- Have your 301 redirect setup tested. Merges require redirects, and a broken 301 turns the merge into a deletion.
- Snapshot current rankings before any change. You need a baseline to measure the lift.
Step by step
- Export Search Console: query, URL, clicks, impressions, position, last 90 days. Pivot so each query shows the top 3 URLs ranking for it.
- Find candidate pairs: any query where two of your URLs both rank on the first two pages. A small script flags these in seconds.
- Feed AI each candidate pair with both article bodies (first 500 words each) and the shared queries. Ask it to classify: merge, differentiate, or leave alone.
- For merge candidates, ask AI to produce a unified outline favoring the stronger URL (more inbound links or higher current position). The other URL gets 301-redirected.
- For differentiate candidates, ask AI to propose distinct title and intent angles. Example: one article targets the how-to query, the other targets the comparison query.
- Execute in one batch per week. Merges are riskier (redirect, rewrite, monitor). Differentiations are safer (title and H1 changes, plus a few paragraphs).
- Monitor each pair for 4-8 weeks. The kept URL on a merge should climb 3-5 positions; differentiated pairs should both improve as intent clarifies.
First-run exercise
- Pick the 10 pairs with the highest combined impressions on shared queries. These have the biggest upside and the clearest signal.
- Run AI classification on this batch. Time: 15 min export, 10 min AI classify, 30 min per merge decision, 15 min per differentiation. Budget 3 hours for 10 pairs.
- Save AI’s classifications and your final calls side by side. Disagreements are where you learn the prompt’s blind spots.
- For the second batch, refine the prompt to handle the failure mode that bit you most.
Quality check
- Every merge has a defined winner URL based on real signals (inbound links, current position, content depth). Coin flips lose authority.
- Every 301 lands on a relevant URL, not a category index. Topic-mismatched redirects get reclassified as soft 404s.
- After a merge, the kept URL contains every unique value from the redirected URL. Losing unique content is how merges fail.
- Differentiations show in title and H1, not just frontmatter. Google reads visible signals.
How to reuse this workflow
- Re-run quarterly. Cannibalization regrows whenever you publish new content adjacent to old.
- Maintain a “merged URL” log with the redirect target and the merge date. Audit logs save you when a future contributor accidentally recreates the merged article.
- Add a pre-publish check: any new article must declare its primary query, and the check warns if any existing URL already ranks for that query.
Recommended workflow
90-day Search Console export -> script flags candidate pairs by shared queries -> AI classifies merge / differentiate / leave alone -> execute merges with 301 + content unify -> execute differentiations with title and intent shift -> monitor for 4-8 weeks -> document outcomes.
Common mistakes
- Merging based on title similarity alone. Two articles can have similar titles but distinct intent — leave them alone.
- Deleting the loser instead of 301-redirecting. You lose every external link pointing at it.
- Differentiating only the title while leaving body text overlapping. Google reads body, not just title.
- Merging across categories. Topical context matters; a tutorial and a news piece on the same query should stay separate.
- Running the workflow on too small a window. 30 days of query data is noise; 90 days reveals real patterns.
- Skipping the post-merge monitor. Sometimes the merged article ranks worse — you need to know within 8 weeks to revert.
FAQ
- How do I pick the winner URL in a merge?: Inbound links first, current position second, content depth third. If all three disagree, keep the URL with the older publish date — it has accrued more trust.
- Can I merge three URLs at once?: Yes, but rarely worth it. Three-way merges produce sprawling articles. Prefer two two-way merges instead.
- What if AI says “leave alone” but I disagree?: Trust your judgment on intent. AI reads text well but lacks site context — your editorial taxonomy beats its inference.
- How long until rankings move on the kept URL?: 4-8 weeks. The redirect needs to be discovered, the kept URL re-crawled, the consolidated signals reassigned.
- Does cannibalization apply to category pages?: Yes. A category page and a popular article on the same query is a common cannibalization pattern.
- Should the merge target be a fresh URL?: No. Pick the stronger of the two existing URLs. A fresh URL starts from zero authority.