Why Is My Old, Retired Web Page Still Ranking Above My New One?

You launched a shiny new page, retired the old one, and weeks later the dead page is still sitting at the top of Google while your replacement is nowhere. Frustrating, and more common than you'd think. The good news: an old page ranking instead of your new page is almost always a fixable technical problem, not a permanent verdict on your content.

This guide explains why Google clings to outdated pages, how to diagnose which issue you've got, and the exact steps to hand the rankings over to the right URL.

Key takeaways

• An old page usually keeps ranking because Google still sees it as the "best" version: no redirect, a stale canonical tag, or leftover internal links all point back to it.
• Google needs time to recrawl and reprocess changes; rankings rarely swap over instantly, and big index updates can take weeks.
• A proper 301 redirect from the old URL to the new one is the single most reliable fix when you've genuinely replaced a page.
• If both pages should exist, canonical tags and internal linking decide which one Google favours.
• Check Google Search Console first: it tells you which URL Google has actually indexed and why.

First, why does this happen at all?

Google doesn't rank the page you *want* to rank. It ranks the page it has crawled, indexed, and judged most relevant for a search. When you replace a page, several signals still quietly favour the old one:

• Backlinks and authority. The old URL may have years of links, mentions, and trust behind it. Your new page starts closer to zero.
• Internal links. If menus, buttons, and old blog posts still point to the retired URL, you're telling Google the old page matters.
• Crawl lag. Google hasn't necessarily seen your change yet. It recrawls pages on its own schedule, and popular URLs can get cached behaviour that lingers.
• Mixed signals. A redirect that isn't quite right, or a canonical tag pointing the wrong way, leaves Google guessing, and it often guesses "old page."

Google is explicit that consolidating duplicate or replaced URLs is your job to signal clearly, through redirects and canonical tags, in its guidance on canonicalisation and duplicate URLs. Get those signals right and the rest tends to follow.

The most common causes (and how to spot them)

1. You deleted or replaced the page but never set up a redirect

This is the classic. You built a better page at a new URL and left the old one live, or worse, deleted it so it now 404s while Google still shows it in results for a while.

If the old page still loads on its original URL, Google has no reason to move on. Nothing tells it "this content now lives over here."

How to check: visit the old URL. Does it still open? Does it 404? Either way, if there's no redirect to the new page, that's your problem.

2. Your canonical tags are pointing at the old page

A canonical tag tells Google which version of similar content is the "master" copy. If your new page carries a canonical tag pointing back at the old URL (easy to do when you duplicate a template or migrate a CMS), you've politely asked Google to keep ranking the old one.

How to check: view the source of your new page and search for `rel="canonical"`. Confirm it points to the new page's own URL, not the retired one.

3. Internal links still feed the old URL

Your navigation, footer, related-posts widgets, and older articles may all still link to the retired page. Internal links are a strong relevance signal, so if the whole site keeps pointing backwards, Google follows.

How to check: in Google Search Console, open the Links report and look at internal links for both URLs. If the old page has far more, that's a signal problem.

4. Google simply hasn't recrawled yet

Sometimes you've done everything right and Google just hasn't caught up. Recrawling and reprocessing take time, especially across a large site or during a slow crawl period. This is the "google not updating rankings" scenario, and patience plus a nudge usually sorts it.

5. The old page is genuinely a better match

Uncomfortable but worth facing: sometimes the outdated page outranking your new one is Google's honest opinion. If the old version had more depth, better internal linking, or matched the search intent more closely, the new page has to earn its place, not just inherit it.

How to fix an old page outranking your new one

Work through these in order.

1. Decide the page's fate. Should the old page exist at all? If it's fully replaced, it should redirect. If both serve a purpose, they need clearly different intents so they don't compete.

2. Set up a 301 redirect. For a replaced page, a permanent 301 redirect from the old URL to the new one passes the accumulated authority across and removes the duplicate from the running. Avoid temporary 302s for permanent moves; they tell Google the change isn't final.

3. Fix your canonical tags. Make sure the new page self-canonicalises and that no stray tag points back to the retired URL.

4. Update internal links. Repoint menus, buttons, and in-content links to the new URL. This is quick, high-impact, and often overlooked after a redesign or website rebuild.

5. Resubmit and request indexing. In Google Search Console, use the URL Inspection tool on the new page and request indexing. Make sure your XML sitemap lists the new URL and not the old one, then resubmit it.

6. Strengthen the new page. If the old page won on merit, close the gap: match the search intent, add the detail readers actually want, and earn a few quality links. Our SEO services exist for exactly this kind of consolidation and recovery work.

How long does it take to see the swap?

There's no fixed timer. A single well-redirected page on a healthy, frequently crawled site can update within days. A larger migration, or a site Google crawls slowly, can take several weeks to fully settle. During that window you may see both URLs flickering in and out of results, which is normal as Google reprocesses the change.

Resist the urge to keep changing things every day. Set the signals correctly, confirm them, then give Google time to act. If nothing has budged after a few weeks, that's when to dig deeper with a full technical review, which is where a website audit earns its keep.

Frequently asked questions

Why is Google showing my old page instead of the new one?

Because Google still treats the old URL as the best, most-linked, most-trusted version. Usually there's no redirect, a canonical tag points the wrong way, or internal links still favour the old page. Fix those signals and Google reassigns the ranking.

Will a 301 redirect pass my rankings to the new page?

A permanent 301 redirect is designed to consolidate the old URL into the new one and pass its authority across. It's the most reliable fix when a page has genuinely been replaced, though Google still needs time to recrawl and process it.

How do I force Google to recrawl my new page?

Use the URL Inspection tool in Google Search Console and request indexing, and make sure the new URL is in your XML sitemap. You can't truly *force* Google, but these steps put the change firmly on its radar.

Should I delete the old page completely?

Only if it has no replacement and no value. If you've built a newer version, redirect the old URL rather than deleting it, so you keep the authority and avoid dead 404s in the index.

What if my new page just isn't as good?

Then Google is doing its job. Improve the intent match, depth, and internal linking of the new page so it deserves the top spot, rather than expecting it to inherit rankings automatically.

Get a clear diagnosis, fast

Most "wrong page ranking" problems come down to two or three fixable signals, but spotting exactly which ones takes a proper look under the bonnet. Run a free instant website audit with Climbio to see how your pages are performing, then, if you'd like a human to sort the redirects, canonicals, and internal links for you, book a call and we'll get the right page ranking again.