How to Consolidate Two Pages That Compete for the Same Query

How do you consolidate two pages that compete for the same query?

Pick the page with the stronger history, move the unique content from the weaker one into it, permanently redirect the weaker URL to the survivor, and then fix every internal link that still points at the old address. Do those four steps in that order and nothing is lost.

Two pages chasing the same query is one of the most common problems on a site that has been publishing for a few years. Somebody wrote a guide in 2024, somebody else wrote a slightly different guide in 2025, and now neither ranks as well as one good page would.

This is the exact procedure I follow. It takes about an hour per pair and it is one of the highest return things you can do on an established site.

How do you confirm the two pages are actually competing?

Open Search Console, filter to each page separately, and compare their query lists. If the same queries appear for both, they are competing. If the overlap is a handful of low volume terms and each page owns a distinct set, leave them alone and go and find a real pair.

The other signal is instability. When two of your pages compete, the one Google shows for a query often flips between them week to week, which suppresses both. You see this as an average position that wanders without any content changes to explain it.

Do this check before you do anything else. I have watched teams merge pages that were not competing at all, which loses one page's traffic and gains nothing, because the diagnosis was a hunch rather than a query comparison.

Which page should survive?

The one with more organic impressions over the last six months, unless the other one is better written and the gap is small. History is hard to rebuild and prose is easy to move, so the default is to keep the URL that has earned attention and improve its content with the other one's material.

Look at backlinks as a tiebreaker rather than as the primary criterion. A page with genuine external links pointing at it is carrying something you cannot recreate, and moving it should be a deliberate decision rather than a side effect of preferring the newer writing.

Pick the URL before you touch the content. Deciding which page survives while you are in the middle of merging paragraphs leads to a hybrid that half redirects, and untangling that later is much harder than getting the decision right at the start.

What do you actually move across?

Only what the survivor does not already say. Read the weaker page and extract the sections that are genuinely new: an example the other lacks, a step it skips, an objection it handles better. Everything else is duplication and should be dropped rather than merged.

Resist the urge to keep both versions of a point. Merging two pages by concatenating them produces something long, repetitive, and worse than either original, and length has never been the thing that made a page rank. The merged page should be tighter than the sum of its parts.

While you are in there, rewrite the opening. The survivor's introduction was written for a narrower version of this page, and now it needs to answer the whole query. This is the same rewriting work I described in how to rewrite a page that ranks on page two, applied to a page that is about to get more responsibility.

Which redirect do you use and why?

A permanent one. Google's documentation on redirects states that with a permanent redirect, Googlebot follows the redirect and the indexing pipeline uses the redirect as a signal that the redirect target should be canonical. That canonical signal is the entire point of the exercise.

A temporary redirect does not do this. The same documentation says that with a temporary redirect, Googlebot follows it but the indexing pipeline does not use it as a signal that the target should be canonical. If you use a temporary redirect here, you have moved your visitors and left your search signals behind.

Google's documentation is explicit that the 301 and 308 status codes mean a page has permanently moved to a new location, and that you should use a permanent redirect when you are sure the redirect will not be reverted. Being sure is a real condition, which is why picking the surviving URL first matters so much.

How long do you keep the redirect in place?

Indefinitely. Google's redirect documentation does not give a timeframe, and the practical answer is that a redirect costs you nothing to keep and can only cost you something to remove. External links to the old URL will keep arriving for years and every one of them is a visitor.

The only reason I have ever removed one is a URL structure change that made the redirect chain too long. Chains are the real risk here, not the redirects themselves, because a redirect pointing at a URL that itself redirects adds latency and loses clarity. Point every old URL at the final destination directly.

Keep a record of the redirects you have created, with the date and the reason. Three years later somebody will look at the redirect list and wonder whether any of it can be cleaned up, and the answer will be much easier to give if the reasons were written down.

What breaks if you skip the internal link cleanup?

Every internal link still pointing at the old URL creates an unnecessary redirect hop and sends a mixed signal about which page you consider canonical. It works, in that visitors arrive, but you are quietly telling search engines that you still think the old page is a destination.

Find them by searching your site for the old slug rather than by relying on memory. On a CMS driven site the links live inside rich text fields, which means they will not show up in any template search, and they are easy to miss entirely.

Navigation, footers, and any reusable component deserve a separate check, because those links appear on every page and so carry more weight than any single article link. I go through the full sweep in how to audit internal links on a 500 page CMS.

How do you know whether the consolidation worked?

Compare the survivor's impressions and clicks against the combined total of both pages before the merge, not against the survivor alone. The honest benchmark is whether one page now does the work that two were doing between them, and anything above that is a gain.

Give it six weeks before judging. The old URL has to be recrawled, the redirect has to be processed, and the merged page has to accumulate enough data to compare. Checking at two weeks will show you a dip, because a dip is what the first two weeks usually look like.

Write down the before numbers on the day you merge. This is the step everyone skips and then regrets, because six weeks later the comparison you need is the one you did not record, and Search Console's date ranges will not reconstruct the combined figure for you.

What should you do next?

Find one pair. Sort your pages by impressions, look for two whose query lists overlap, and run this procedure on them today. One pair takes an hour and teaches you more about your own site's structure than an afternoon of reading would.

Once you have done one, look for the pattern that created it. Competing pages are usually a symptom of a briefing process that does not check what already exists, and fixing that upstream is worth more than fixing pairs downstream forever.

If you have two pages you suspect are fighting each other and you are not sure which one should win, send me both URLs. I am happy to tell you which one I would keep and why.