Old Blog Posts Are Cannibalizing New Content

You published a better post on a topic you had already covered, and the old URL still ranks while the new one sits below it. A third, even better version adds another competitor rather than settling it. Two of your pages are answering the same query, and the old one has what the new one hasn’t had time to earn: links from other sites and the internal links your own pages have pointed at it since it went live. The decision is whether to merge the two, separate them, or put the new work into the old URL, and four checks help you decide which.

What the old URL has that the new one doesn’t

Once two of your pages serve the same need, they compete for the same results. The older page has a head start you can see: referring domains, internal links, and a URL that other sites have cited. A new URL starts with none of that. You can’t read Google’s weighting from outside, so skip the guessing and decide which page should carry the topic from now on.

Four checks before you decide

The first two decide whether the pages compete at all. The last two decide which URL carries the topic.

1. Are the two queries the same query?

Compare the search results for the two target queries instead of judging by wording. If the same URLs rank for both, searchers are being served one set of answers for both, and your two pages are competing for it. If the results differ, the pages may be serving adjacent needs. This is a practical test, not a Google rule, but it replaces a hunch with something you can check.

2. Do the pages serve different intents?

A how-to guide, a comparison and a checklist on the same subject can coexist if each answers a different goal. If they do, separate them. If they answer the same goal, merge.

3. Which URL holds the links?

Pull the referring domains for both URLs. External links are an asset you can’t rebuild on demand, so the page that holds them is the first candidate to keep.

4. Is the link-holder’s traffic stable or sliding?

In Search Console’s Performance report, the Pages tab groups clicks and impressions by page, so you can follow both URLs over a long date range. A page that holds the links while its traffic has declined for months may be ranking on links it earned years ago while its content ages. That changes the question from “which URL do we keep” to “what does the old page’s content need.”

When to merge

Same query and same intent: merge.

Pick the keeper: the link-holder. If its content is the weak part, the merge is where you fix it.
Move the unique value of the other page into the keeper. Merge the content first, then redirect. A redirect to a page that no longer covers what the retired page covered sends visitors to something that doesn’t answer their question.
Add a permanent server-side redirect (301 or 308) from the retired URL to the keeper. Google’s redirects guide says to use permanent redirects when you’re sure the redirect won’t be reverted, so make the merge decision as if it were final.
Update your internal links and your sitemap to point at the keeper. Google’s guide to consolidating duplicate URLs says to link to the canonical URL rather than a duplicate, because consistent linking helps Google understand your preference. It also says all pages listed in a sitemap are suggested as canonicals, so list only the keeper. The guide adds that these methods stack: using two or more increases the chance that your preferred canonical is chosen.
Leave the redirect in place. Google’s site move guide, which covers URL changes, says to keep redirects for as long as possible, generally at least one year. It explains that this timeframe allows Google to transfer all signals to the new URLs, including reassigning links on other sites that point to the old ones.

What the 301 does, and what Google doesn’t quantify

The redirect is a signal about which URL should represent the content:

The target is what gets shown. Google’s redirects guide says a permanent redirect shows the new target in search results, while a temporary redirect keeps showing the source page. The consolidation guide lists redirects as a strong signal that the target should become canonical.
Link signals are combined. The consolidation guide says choosing a canonical helps search engines consolidate the signals they have for individual URLs, such as links to them, into the preferred URL.
The retired URL stays known. The redirects guide says the other URL becomes an alternate name of the canonical URL, and that alternate names may appear in search results when a query hints that users might trust the old URL more. Seeing the old URL now and then after a merge fits that description, and is not by itself a sign the redirect failed.

Google’s site move guide answers the loss question directly: 301 and other permanent redirects don’t cause a loss in PageRank. Beyond that, three claims hold: a strong canonical signal, combined link signals, and a redirect kept long enough for Google to move them.

Keep it to one hop

Point the redirect straight at the keeper. The site move guide says Googlebot can follow up to 10 hops in a chain of redirects, but advises redirecting to the final destination directly. Where that isn’t possible, it says to keep the chain ideally no more than 3 and fewer than 5. Chains add latency for users, and they add crawl requests: Search Console’s Crawl Stats report counts each request in a redirect chain separately. If an earlier migration already redirects to the page you’re now retiring, repoint that older redirect at the keeper as well.

Redirect only to a real match

A redirect serves the reader when the destination covers what the old URL covered. The site move guide warns against redirecting many old URLs to one irrelevant destination, such as the home page, because it can confuse users and might be treated as a soft 404. If an old post has no close match anywhere on your site, let it return a 404 or 410. Google’s crawl budget guide recommends a 404 or 410 for permanently removed pages and says soft 404 pages will continue to be crawled.

When to separate the pages

Different intents, or search results that don’t overlap, mean you keep both and sharpen each one so they stop competing. Tighten the old post around the query it owns. Aim the new post at the adjacent need it serves better. Make the title, headings and opening paragraph of each page state plainly which question it answers, so a reader and a crawler can tell the two apart at a glance.

Put the new work into the old URL

Publishing a new URL on a topic you already cover restarts the standoff: a page with no links against one that already has them. If the old page holds the links, update it instead. Move the new research, the better structure and the fresh data into the URL that already ranks, and the page keeps its links while it gains the better content. Build a new URL when the intent is different.

Preventing the next collision

Old-versus-new conflicts start as an inventory problem, and an inventory can catch them before you publish:

Keep a keyword-to-URL map. One primary query, one owning URL. Check the map before approving any new post.
Default to updating. If a query is already covered, improve the existing page before creating a competitor for it.
Compare search results before publishing. If a proposed post’s target query returns largely the same ranking URLs as a query you already cover, change the angle or fold the material into the existing page.

Frequently asked questions

Why can’t my better new post outrank my old one?

When both pages answer the same query, the old URL holds the links other sites and your own pages have pointed at it. The new URL starts without them. Merging into one URL, or updating the old page, puts the better content where those links already point.

Does a 301 redirect cost rankings?

Google’s site move guide says 301 and other permanent redirects don’t cause a loss in PageRank, so treat any quoted loss percentage with suspicion. Google also describes a permanent redirect as a strong signal that the target should be canonical, and says choosing a canonical helps consolidate signals such as links into the preferred URL. Point the redirect straight at the final page and keep it as long as possible, generally at least a year.

Which page should I keep?

Start with the one holding the external links. If its traffic has been declining, keep the URL and rebuild its content, moving the newer post’s material into it.

Can I redirect old posts to my home page?

Not as a catch-all. Google’s site move guide says that pattern might be treated as a soft 404. Redirect each old URL to a close match, or return a 404 or 410 when there isn’t one.