301 Redirects: When to Use Them, How to Set Them Up and Costly Mistakes

Every time a page changes address, someone has to tell Google and visitors where it went. That’s the redirect’s job. And among the types that exist, the 301 is the one that preserves the SEO work you’ve already built. Using it wrong, or forgetting to use it, is the most common way to lose traffic overnight without understanding why.

This guide explains what a 301 redirect is, when to use it, how it differs from a 302 and a 410, and how to apply it without making the mistakes that cost rankings. With practical examples for WordPress users and a step-by-step for reviewing what already exists on your site.

What Is a 301 Redirect?

A 301 redirect is an instruction telling the browser and Google that a page has permanently moved to a new address. The number 301 is an HTTP status code that means exactly that: “moved permanently”.

When someone visits the old URL, the 301 automatically takes them to the new one, without the visitor doing anything. They don’t even notice; they just arrive in the right place. And, more importantly for SEO, the 301 passes most of the authority the old page had built up over time to the new address. That’s why it’s the silent hero of any URL change.

Without a redirect, every page that changes address becomes a dead end. Visitors hit an error, Google finds a dead page and all the authority that address had earned simply evaporates. This control over how Google reads your URLs is central to technical SEO, the foundation that must be solid before any content strategy.

When to Use a 301

A 301 fits every situation where a URL no longer exists at the old address but the content lives on somewhere else. Some cases are more common than others.

The first is a page changing address. If you rewrite a post’s URL to make it cleaner, or remove the year from a slug so you can update the content later, the 301 takes visitors from the old URL to the new one, preserving the rankings you’ve earned.

The second is content consolidation. When two similar pieces compete for the same search, the move is to merge the best of both into one page and 301 the other to it. That fixes cannibalization, where your own pages compete against each other, and concentrates strength at a single address. It’s the same principle behind topic clusters, applied at the URL level.

The third is migrating an entire site, when you change domains, platforms or reorganize your whole URL structure. Here, the redirect map is what keeps you from losing years of work at once. It’s a big enough case to deserve its own guide on site migration without losing SEO.

The fourth is standardizing your site address. Many people don’t realize it, but versions with and without “www”, or with “http” and “https”, can be treated by Google as different sites. A 301 unifies everything into one version, keeping strength from splitting across addresses that, for you, are the same place.

301, 302 or 410: Which to Use

This is where a common mistake lives. Choosing the wrong code sends Google the wrong message, and the result shows up in rankings.

A 301 is for a permanent change. Use it when the page won’t return to the old address. It passes authority and is what you’ll want in the vast majority of cases.

A 302 is for a temporary change. Use it only when the page really will return to the original address soon, like during brief maintenance or an A/B test. The problem is that many people apply a 302 thinking it’s the same as a 301, and then Google doesn’t pass authority as it should, because it reads the change as temporary and keeps the old page in memory.

A 410 isn’t a redirect; it’s the opposite. It tells Google the page has been removed for good and no longer exists anywhere. Use it when the content is gone and there’s nowhere to redirect. It’s more direct than letting the page become a 404 error, because it signals the removal was intentional, speeding up the URL’s removal from results.

How to Set Up a 301 on WordPress

On WordPress, there are two main ways to create a 301 redirect, and the choice depends on your technical comfort.

The simplest is a plugin. Many SEO plugins, including the one that generates your sitemap, have a built-in redirect module. You enter the old and new URLs and the plugin handles the rest. It’s the recommended path if you don’t want to touch server files, because it reduces the risk of accidentally taking the site down.

The most direct is the server configuration file, .htaccess on Apache servers. One redirect line in that file points the old URL to the new one:

Redirect 301 /old-page/ https://www.yoursite.com/new-page/

To force a single version of the domain (https and www), a rewrite rule does the job:

RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^(.*)$ https://www.yoursite.com/$1 [L,R=301]

It’s faster and doesn’t depend on a plugin, but it demands extra care: a syntax error in that file can take the whole site down. If you’re not comfortable with it, use the plugin or ask whoever handles your technical SEO.

Whichever method you use, test afterward. Visit the old URL and confirm it goes straight to the right address, with no intermediate hops and no error page along the way.

The Mistakes That Cost Traffic

Some 301 slip-ups are as common as they are damaging. Know them before you make changes, because prevention is far easier than diagnosing a drop later.

The first is redirect chains. They happen when URL A redirects to B, which redirects to C. Each hop slows loading and dilutes the authority passed along. Always point straight to the final destination: A goes to C, skipping B. Long chains also weigh on page speed, which ties directly into a slow website.

The second is redirecting everything to the homepage. When a page disappears, laziness says send everyone home. To Google, that’s almost the same as an error, because it doesn’t deliver the content the person wanted. Always redirect to the page most similar to the original, the one that best replaces what the visitor was looking for.

The third is forgetting to update internal links. After changing a URL, links pointing to the old version keep working thanks to the 301, but they go through an unnecessary extra hop. Ideally, update those links to point straight to the new address, easing server load and preserving speed.

The fourth is using a 302 instead of a 301 by mistake. As we saw, that prevents full authority transfer. Always check that the code applied really is the permanent one, because a single digit changes everything in Google’s eyes.

How to Review Your Site’s Redirects

If your site has been around a while, it has probably accumulated old redirects, some forgotten, others misconfigured. A periodic review keeps them from becoming a silent problem.

Start by listing every active redirect, in the plugin or the server file. Check whether any form a chain, pointing to another URL that also redirects. Fix each chain so it points straight to the final destination. Then check whether any redirect sends visitors to the homepage unnecessarily, and adjust it to the most suitable page.

This kind of review is a mandatory item in any SEO audit, precisely because problematic redirects aren’t visible to the naked eye but steadily drain authority and speed.

Frequently Asked Questions About 301 Redirects

Does a 301 pass all of the old page’s SEO?

It passes most of the authority, enough to preserve rankings in nearly every case. That’s why the 301 is the standard for any permanent URL change. A small loss may occur, but it’s far smaller than letting the page break and become a dead end.

How long should I keep a 301 redirect?

As long as possible, ideally forever. As long as any external link or Google’s memory points to the old URL, the 301 stays useful. Removing it too early reopens the hole it plugged, and the traffic that flowed through it disappears again.

Do 301 redirects slow down my site?

A direct redirect has minimal impact on speed. The problem comes with chains, when several hops pile up before reaching the destination. That’s why the rule of always pointing to the final destination matters for both speed and SEO.

Should I use a 301 or a 410 for a page I removed?

If there’s a similar page to send visitors to, use a 301. If the content is simply gone with no replacement, a 410 is more honest with Google than letting the page become an unexplained 404 error, because it signals the removal was your decision.

What’s the difference between a 301 and a canonical for similar content?

A 301 eliminates one page and sends everyone to the other. A canonical tag keeps both pages live and just tells Google which one concentrates the strength. Use a 301 when the old page no longer needs to exist, and a canonical when both need to stay accessible.

Do I need to notify Google after creating a redirect?

It isn’t required; Google finds redirects when it crawls the site normally. But updating the sitemap and internal links speeds things up, helping Google understand the change faster. In large migrations, monitoring Search Console in the following weeks is what shows whether everything was recognized correctly.

Change Addresses Without Losing Rankings

Redirects seem like a technical detail, but they’re where a lot of traffic is silently lost. A botched URL change erases months of work at once, and worse, the drop is often noticed only weeks later, when the cause is hard to trace.

If you’re going to reorganize URLs, consolidate content or migrate your site, start with an SEO audit from Malamute Digital. We map every redirect needed so the change happens without losing what you’ve built, with the care of a team that treats technical SEO as a foundation, not a detail.