Skip to content

When to redirect a page, and when to let it go

Last checked 15 November 2026

Redirect a page when there's a real replacement for it. When there isn't, let it show an error. A missing page isn't a disaster, and a forced redirect can leave readers more confused than an honest "not found."

When a redirect is the right call

Google lists the moments a redirect helps. The list includes removing a page and sending users to a new one.1 Another is merging two websites, so links to outdated addresses go to the correct pages.1

Google's Search Console help says the same for a page that's moved: use a 301 redirect to the new location.2

The test is simple. Would a visitor who clicked the old link be happy to land on the new page? If you renamed /prices to /pricing, yes. If you deleted a page on gardening tips and the nearest page is your contact form, no.

Deciding what to do with a removed pageA page address stops workingIs there a page on the same topic?Yes: redirect to it with a 301No: let it show a 404 or 410
The question is whether a matching page exists.

When to let it go

Sometimes a page is gone and nothing replaces it. An old event notice is a fair example. The honest answer is an error page.

Google's help page says 404 responses are not necessarily a problem if the page has been removed without any replacement.2

You may see the old address pop up in reports for a while. Google says Googlebot will probably continue to try the address for some period of time, but it will crawl it less and less often.2 Googlebot is Google's crawler, the program that visits pages.

You don't have to chase it. Leave the missing page returning an error and let that fade.

Which error to show

There are two error codes for a missing page, and a separate page covers how they differ.3

For now, one rule from MDN is enough. If you don't know whether the removal is temporary or permanent, a 404 should be used instead of a 410.3

Tidy up your own links

Whatever you choose, the links on your own pages still need attention. MDN tells website owners to remove or replace links that lead to a page returning a 410.3 The same sense applies to a 404 on your own site. A link to a page that's gone only sends your readers to an error.

You'll find those links with the steps in how to find broken links, and fix them using fixing a broken link.

If you want it out of search quickly

A missing page can linger in Google for a while. Google has a Removals tool in Search Console for this. It removes a page hosted on your site from Google's search results within a day.4

That's a short-term fix. Google says requests made in the Removals tool last for about 6 months.4 The page itself has to be removed or changed for the result to last.

A short test before you redirect

Run through these questions for each removed page:

  • Is there a page on your site about the same thing?
  • Would someone who clicked the old link be glad to arrive there?
  • Is the move meant to last?

If every answer is yes, a permanent redirect suits. If not, an error page is the better choice.

Redirects aren't free either. MDN says their use should be kept to a minimum.5 Before you add a rule to a server file or host setting, save a note of the current settings, and follow your own host's help pages.

Reference list

  1. Redirects and Google Search, Google Search Central
  2. Page indexing report, Google Search Console Help
  3. 410 Gone, MDN Web Docs (Mozilla)
  4. Remove your site info from Google, Google Search Central
  5. Redirections in HTTP, MDN Web Docs (Mozilla)