Web design & digital marketing in Poole, helping 400+ businesses since 2010.
Expect Best logoExpect Best
SEO

301 Redirect: When to Use One and When Not To

Written by Expect Best · 22 October 2026

A 301 redirect tells browsers and search engines that a page has moved permanently to a new address. It is the most useful single tool for protecting search visibility during any change to a website, and the one most often applied in a way that destroys the thing it was meant to protect.

What a 301 redirect actually does

When a page has ranked for a while it has accumulated signals: links pointing at it, a history in the index, a position it earned. Those attach to the URL rather than to the words on it.

Move the content to a new address with no redirect and all of that is orphaned. The new page starts from nothing, and anyone following an old link gets an error.

A 301 tells search engines to transfer the old page's standing to the new one and to replace it in the index. Done properly, most of the value carries across.

301 or 302

A 302 says the change is temporary and the original should stay in the index. That is occasionally what you want, such as during genuine maintenance or a short-term promotional swap.

It is almost never what people actually mean. The common mistake is using a 302 for a permanent move, usually because a plugin defaulted to it, which leaves search engines holding on to the old URL and the new one struggling.

If the change is permanent, and it usually is, use a 301.

Where they go wrong

Chains. Page A redirects to B which redirects to C. Each hop adds delay and loses a little value, and chains build up quietly across successive redesigns until nobody remembers why they exist. Redirect straight to the final destination and periodically flatten the ones that have accumulated.

Loops. A redirects to B and B redirects back to A. The page becomes completely unreachable and it is surprisingly easy to create by accident when two rules overlap.

Bulk redirects to the homepage. The most damaging and the most common, usually done because mapping two hundred URLs individually was tedious. Search engines treat a redirect to an irrelevant page as a soft error, so the value does not transfer. You get the work of redirecting with none of the benefit, and a confusing experience for anyone following an old link.

Redirecting to something unrelated. The same problem in miniature. The destination should be the closest genuine equivalent, and where nothing is equivalent, a helpful 404 is more honest than a misleading redirect.

When not to redirect

If a page is genuinely gone and has no equivalent, let it 404, or use a 410 to say it is deliberately gone. A useful 404 page with a search box and links onward is better than sending somebody somewhere irrelevant.

Redirecting everything reflexively is how sites end up with thousands of rules nobody can audit, several of them contradicting each other.

Keeping them

There is a persistent belief that redirects can be removed after six months or a year once search engines have caught up.

They should not be. Links on other people's websites do not expire, printed materials do not update, and bookmarks last for years. Removing a redirect turns every one of those into an error, and it is a pointless saving because redirect rules cost essentially nothing to keep.

Where this matters most

Any site change that alters URLs: a website redesign, a platform move, a domain change, tidying up an old structure. Each is an opportunity to protect what you have built or to lose it in an afternoon.

One practical note: implement them at the server or platform level where you can, rather than through a plugin. Plugin-based redirects work, but they load on every request and they disappear if the plugin is ever removed, which happens during exactly the sort of tidy-up where nobody is thinking about redirects.

The work is unglamorous and entirely front-loaded. Map the URLs first, redirect each to its closest equivalent, test before launch, then watch Search Console for a month. Our website migration guide covers the full process, and our SEO service treats this as the first thing to check whenever traffic drops suddenly.

FAQs

Redirect FAQs

The questions that come up during any site change.

A 301 says the move is permanent and the new page should replace the old one in the index. A 302 says it is temporary and the original should be kept. Using 302 for a permanent move loses you the benefit.

Close to it for a relevant, single-hop redirect. Chains and irrelevant destinations both lose value, which is why the mapping matters more than the mechanism.

You should not. Links on other websites do not expire, and neither do bookmarks. A redirect removed two years later turns those into 404s.

Quantity is rarely the issue. Chains are. A thousand clean single-hop redirects are fine; fifty three-hop chains are a problem.

Want a website that actually generates enquiries?

Tell us what you need and we will come back with honest advice and a clear quote, no pressure.