LINK-V
LINK-V · Article

Should you redirect, canonicalize or remove an old page?

November 21, 2026

Retiring or merging a website page? Choose by the answer readers still need. Use a redirect for a move, a canonical for equivalent versions, or a proper removal response when no replacement exists.


Should you redirect, canonicalize or remove an old page?

Start with what someone should find when they open the old address. If the answer has moved permanently to a relevant replacement, redirect them there. If essentially the same page remains available at several addresses, a canonical can indicate the preferred version for search. If the resource has gone and there is no relevant replacement, return a proper not-found or gone response.

These choices do different jobs. A redirect sends the visitor onward. A canonical leaves the visited page available and expresses a preference to search systems. A removal response says the resource is unavailable. Choosing between them starts with the content decision, before anyone changes a setting.

Grace WebCompare lets you inspect HTTP responses, redirect destinations and canonical paths, compare old and new sites, and rescan an affected URL after a correction. Use the findings to check your decision; you still need to judge whether the destination gives readers the right answer.

Check pages with Grace WebCompare

Does the page still help?

Age alone is no reason to remove a page. An older guide may still answer a useful question. Keep it at its current address if it remains accurate and helpful, or update it where the answer needs attention.

Before retiring it, read the page and write down its purpose in one sentence. Then open the proposed replacement. Does it preserve that answer, or merely discuss a similar subject? A general service page may mention appointments without explaining the preparation instructions in the old guide.

If a page disappeared unexpectedly or will return after a temporary interruption, investigate that situation first. Permanent retirement is a deliberate content decision, not the default response to a technical fault.

Where should readers go?

The answer moved

A preparation guide has moved to a new address. The replacement still contains the instructions. A permanent redirect takes someone following the old URL to that guide.

The same answer has two URLs

Two available addresses show essentially the same guide. A canonical can indicate which version you prefer search systems to use, while visitors can still open either page.

The resource has gone

A permanently expired notice has no useful replacement. A 404 or 410 response can accurately report that it is unavailable, with a helpful explanation for visitors.

These are hypothetical examples. For a merger, check what survives in the combined page. Redirecting an old guide to a combined guide can make sense when the relevant instructions remain easy to find. Sending every retired page to the homepage simply because it exists can leave readers stranded.

Google’s guidance on URL changes recommends relevant destinations and warns against redirecting many old URLs to an irrelevant page. When there is no relevant replacement, it allows a 404 or 410 response.

When is a redirect right?

Use a permanent redirect when the page has permanently moved and the new destination is a suitable replacement. Ask the person implementing it to confirm the appropriate permanent response, usually HTTP 301 or 308. Those numbers describe the server’s response to the old address.

Follow the old URL yourself and inspect the final page. It should open the intended replacement and still deliver the answer. Have the team check the response and the destination’s canonical preference as well. A page that loads successfully can still be the wrong destination.

Google’s redirect documentation explains permanent and temporary moves. A temporary arrangement needs its own choice; do not label it permanent merely to finish the cleanup.

Changing every address from www to the version without it, or the other way around, is a separate sitewide choice. Our explanation of whether your website should use www covers that consistency.

When is a canonical right?

A canonical declaration identifies a preferred URL for duplicate or very similar content. It fits situations where those versions remain available. For example, two URLs may expose essentially the same guide while you want one to be the preferred search version.

A canonical does not send someone to another page. If readers opening the old address should be taken to the replacement, a canonical alone does not accomplish that move. It also cannot make a broad service page equivalent to a detailed guide whose instructions have been removed.

A canonical is a preference, not a promise that Google will select or index that URL. Have the team check that canonical declarations, redirects and links support the intended version rather than pointing in conflicting directions.

Google’s canonicalization guidance explains how it selects a representative URL and weighs different signals. Agree which page should be preferred, inspect the content of both versions, and ask the team to verify the implementation.

What if there is no replacement?

For an agreed permanent removal, ask the team to return an actual HTTP 404, meaning not found, or 410, meaning gone. The page visitors see can still explain what happened and offer useful navigation. Its server response must accurately report the missing resource.

A page saying “this content has been removed” while returning a successful 200 response gives a different technical message. Google may treat an apparent error page with a successful response as a soft 404. Have the response checked, rather than judging only by the visible wording.

Google’s HTTP status guidance explains how these responses affect crawling and indexing. Previously indexed URLs returning 404 or 410 are removed over time. There is no promised removal deadline here, and choosing 410 does not come with a guaranteed speed advantage.

What should you record?

Keep one short decision for each affected page: its old address and purpose, whether to keep, move, retain as a duplicate or remove it, the destination or preferred URL where relevant, and the reason. Name the person responsible for implementation and record what was checked afterward.

Finish with an observed result: the old address leads to the intended answer, the retained duplicate has the intended preference, or the removed resource returns the agreed response.

Review links on your own website that still point to the changed page. Update moved destinations and remove or rewrite references that promise an answer you no longer provide. Our guide to keeping internal links useful after website changes explains that follow-through.

Rescan affected URLs after technical corrections and record any remaining content decision separately. A successful response does not prove relevance, complete discovery or indexing. Redirects and canonical signals cannot guarantee rankings or retained search traffic.

If this page decision is part of a whole-site replacement, our guide to redesigning a website while protecting useful search traffic covers the wider preparation and launch review. For one old page, the immediate task is smaller: choose the right reader outcome, implement it and check what actually happens.

Questions about old pages

Does every removed page need a redirect?

No. Use a redirect when a genuinely relevant replacement exists. An obsolete resource without one can return 404 or 410. Avoid sending unrelated pages to the homepage.

Does a canonical move visitors?

No. The visited page remains available. A canonical expresses a preferred version for duplicate or very similar content; it does not take the visitor to another URL or guarantee indexing.

Can we merge two guides?

Yes, if the combined guide preserves the relevant answers. Check each old page’s purpose before redirecting it. A shared topic alone does not establish that the new page is a useful replacement.

Is an error message enough?

Check the server response too. A removed resource should return the agreed 404 or 410 response, even when the page also provides a helpful explanation and navigation.

LINK-V LINK-V