If you’ve ever changed a page address on your website, redesigned your site, or switched from HTTP to HTTPS, you’ve probably come across the term “301 redirect”. And if you haven’t set one up properly, there’s a good chance you’re losing traffic, confusing Google, and sending visitors to dead pages without even realising it.
I’m Spencer Thomas, a freelance web designer in Brighton. I’ve built and maintained over 55 WordPress websites, and I deal with 301 redirects on a near-weekly basis. They’re one of the most important — and most misunderstood — tools in SEO. Get them right and your site keeps its rankings through major changes. Get them wrong and you can tank your search visibility overnight.
This guide explains what a 301 redirect is in plain English, when you need one, how to set one up (in WordPress, .htaccess, and Nginx), and the mistakes I see business owners make time and again. No jargon. No fluff. Just practical advice you can act on today.
What Is a 301 Redirect?
A 301 redirect is a permanent forwarding instruction. It tells browsers and search engines: “This page has permanently moved to a new address. Go there instead.”
Think of it like a postal redirect when you move house. You tell Royal Mail your new address, and any letters sent to the old one get forwarded automatically. A 301 redirect does the same thing for web pages. Anyone who visits the old URL — whether they clicked a bookmark, a link from another website, or a Google search result — gets seamlessly sent to the new one.
The “301” part is an HTTP status code. When your browser requests a page, the server responds with a three-digit code. A 200 means “here’s the page, everything’s fine.” A 404 means “page not found.” And a 301 means “this page has permanently moved — here’s where it lives now.”
The critical word there is permanently. A 301 redirect tells Google that the move is for good, which signals Google to transfer the old page’s search rankings and link equity to the new URL. That’s what makes it so important for SEO.
When Do You Need a 301 Redirect?
In my experience, there are six situations where a 301 redirect is essential. Miss any of these and you’ll end up with broken links, lost rankings, or frustrated visitors.
1. You’ve Changed a Page’s URL
This is the most common scenario. Maybe you’ve renamed a page from /our-services to /services, or you’ve cleaned up a messy URL like /?p=147 to something readable like /kitchen-renovations. Without a 301 redirect from the old URL to the new one, anyone using the old link — including Google — hits a 404 error.
2. You’ve Redesigned or Rebuilt Your Website
A website redesign almost always changes your URL structure. I see this constantly: a business gets a shiny new site, launches it, and wonders why their Google rankings vanish. The answer is usually that nobody set up redirects from the old URLs to the new ones. When I build a new WordPress site for a client, mapping old URLs to new ones and setting up 301 redirects is one of the first things on my checklist.
3. You’re Merging Pages
Sometimes you realise you’ve got three thin pages that would be better as one comprehensive page. When you merge them, you need to 301 redirect the old URLs to the new combined page. This consolidates the link equity from all three pages into one, which often results in the merged page ranking higher than any of the originals did individually.
4. You’re Fixing Broken Links
If you’ve deleted pages that other websites link to, those inbound links are now pointing at 404 errors. That’s wasted link equity — essentially, free SEO value going down the drain. A 301 redirect from the deleted page to the most relevant existing page recovers that value.
5. You’re Moving from HTTP to HTTPS
Every page on an HTTP site needs a 301 redirect to its HTTPS equivalent. If your site is still on HTTP in 2026, you’ve got bigger problems than redirects — but when you do make the switch (and you should), 301 redirects ensure that all your existing rankings and inbound links transfer to the secure version.
6. You’re Changing Domain Names
Moving from oldname.co.uk to newname.co.uk? Every page on the old domain needs a 301 redirect to its equivalent on the new domain. This is the highest-stakes redirect scenario — get it wrong and you can lose years of accumulated SEO value.
301 vs 302 Redirects: What’s the Difference?
This is one of the most common questions I get, and using the wrong one can genuinely hurt your rankings. Here’s the difference in plain English:
- 301 redirect = permanent move. “This page has moved for good. Update your records.” Google transfers the ranking signals and link equity to the new URL.
- 302 redirect = temporary move. “This page has temporarily moved, but it’ll be back.” Google keeps the old URL in its index and does not transfer link equity to the new one.
When to use a 301
Use a 301 redirect whenever the change is permanent. Changed your URL? 301. Redesigned your site? 301. Merged pages? 301. Moved to HTTPS? 301. Switched domains? 301. If the old page is never coming back, it’s a 301. That covers the vast majority of real-world scenarios.
When to use a 302
A 302 is appropriate when the move is genuinely temporary. For example, you’re running A/B tests and temporarily sending visitors to a different version of a page. Or you’re redirecting to a temporary maintenance page while you fix something. In my experience, 302s are rarely needed for small business websites. If you’re not sure which to use, it’s almost certainly a 301.
The SEO risk of getting this wrong
If you use a 302 when you should have used a 301, Google may not transfer link equity to the new page. I’ve audited sites where someone used 302 redirects for permanent URL changes — sometimes hundreds of them — and the site was haemorrhaging ranking power as a result. Google has got better at interpreting intent in recent years, but why leave it to chance? Use the right redirect for the job.
How to Set Up a 301 Redirect in WordPress
If your site runs on WordPress — and most of the sites I build do — you’ve got several straightforward options for setting up 301 redirects. You don’t need to touch any code.
Option 1: The Redirection Plugin (Free)
The Redirection plugin by John Godley is the most popular dedicated redirect plugin for WordPress, with millions of active installations. It’s free and it works well.
- Go to Plugins > Add New in your WordPress dashboard.
- Search for “Redirection” and install the plugin by John Godley.
- Activate it, then go to Tools > Redirection.
- In the Source URL field, enter the old URL path (e.g.,
/old-page). - In the Target URL field, enter the new URL path (e.g.,
/new-page). - Make sure the redirect type is set to 301 — Moved Permanently.
- Click Add Redirect.
The plugin also logs 404 errors, which is handy for spotting broken links you might need to redirect. I use this plugin on a good number of client sites because it keeps redirect management simple and centralised.
Option 2: Yoast SEO Premium
If you’re already using Yoast SEO Premium (which I’d recommend for most business websites), it has a built-in redirect manager. When you change a page’s slug or delete a post, Yoast will automatically prompt you to set up a redirect. You can also manually add redirects via SEO > Redirects in the WordPress dashboard.
The advantage of using Yoast is that you don’t need an extra plugin — everything stays within one tool. The disadvantage is that the redirect manager is only available in the premium version.
Option 3: Rank Math
Rank Math is another popular SEO plugin, and its free version includes a redirect manager — which is one of the reasons it’s gained popularity. Navigate to Rank Math > Redirections, click Add New, enter your source and target URLs, select 301 as the redirect type, and save. Rank Math can also auto-detect 404 errors and suggest redirects, which is useful during site migrations.
Which method should you choose?
My honest advice: pick whichever suits your setup. If you already use Yoast Premium, use its built-in redirects. If you use Rank Math, use its redirections module. If you use neither or want a dedicated tool, install the Redirection plugin. The important thing is that you actually set up the redirects — the specific plugin matters less than getting it done.
If any of this feels daunting, that’s what my WordPress support service is for. I handle redirects, migrations, and technical housekeeping so you don’t have to.
How to Set Up a 301 Redirect in .htaccess (Apache)
If your site doesn’t run on WordPress, or you prefer to handle redirects at the server level, you can add them directly to your .htaccess file. This file sits in the root directory of your website and controls how your Apache server handles requests.
Important: Back up your .htaccess file before making any changes. A syntax error in this file can take your entire site offline.
Redirecting a single page
Add this line to your .htaccess file:
Redirect 301 /old-page https://yourdomain.co.uk/new-pageThat’s it. Anyone visiting /old-page will be permanently redirected to /new-page.
Redirecting an entire domain
If you’re moving to a new domain, use this:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain\.co\.uk$ [OR]
RewriteCond %{HTTP_HOST} ^www\.olddomain\.co\.uk$
RewriteRule (.*)$ https://newdomain.co.uk/$1 [R=301,L]This redirects every page on the old domain to the equivalent page on the new domain. The $1 captures the path, so olddomain.co.uk/about goes to newdomain.co.uk/about.
Redirecting HTTP to HTTPS
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]This catches any request coming in over HTTP and redirects it to the HTTPS version. Essential for any site that’s migrated to SSL.
Redirecting non-www to www (or vice versa)
RewriteEngine On
RewriteCond %{HTTP_HOST} ^yourdomain\.co\.uk$ [NC]
RewriteRule (.*)$ https://www.yourdomain.co.uk/$1 [R=301,L]Consistency matters. Pick either www or non-www and redirect the other. Google treats them as separate sites, so if you don’t redirect one to the other, you’re splitting your link equity between two versions of the same site.
How to Set Up 301 Redirects on Nginx
If your server runs Nginx instead of Apache, you won’t have an .htaccess file. Redirects are configured in your Nginx server block (usually in /etc/nginx/sites-available/ or /etc/nginx/nginx.conf).
Redirecting a single page
server {
listen 80;
server_name yourdomain.co.uk;
location = /old-page {
return 301 https://yourdomain.co.uk/new-page;
}
}Redirecting an entire domain
server {
listen 80;
server_name olddomain.co.uk www.olddomain.co.uk;
return 301 https://newdomain.co.uk$request_uri;
}Redirecting HTTP to HTTPS
server {
listen 80;
server_name yourdomain.co.uk www.yourdomain.co.uk;
return 301 https://$host$request_uri;
}After making changes to your Nginx configuration, you’ll need to test the syntax with nginx -t and then reload the configuration with sudo systemctl reload nginx. If the syntax test fails, don’t reload — you’ll take the site down.
If the server-level stuff feels out of your depth, that’s completely normal. It’s the kind of thing I handle as part of my WordPress hosting and support service, so you don’t need to worry about breaking anything.
Common 301 Redirect Mistakes (and How to Avoid Them)
Over the years I’ve seen the same redirect mistakes come up repeatedly. Here are the ones that cause the most damage.
1. Redirect Chains
A redirect chain happens when page A redirects to page B, which redirects to page C, which redirects to page D. Each hop adds latency, wastes crawl budget, and can dilute link equity. Google will follow up to about five redirects in a chain, but after that it may simply give up.
The fix: Always redirect directly to the final destination. If you’re updating redirects and the target has changed, update the original redirect rather than adding another hop. Audit your redirects periodically to catch chains before they get out of hand.
2. Redirect Loops
A redirect loop is when page A redirects to page B, which redirects back to page A. The browser goes back and forth forever until it gives up and shows an error. This completely kills the page — nobody can access it.
The fix: Test every redirect after you set it up. If you get an “ERR_TOO_MANY_REDIRECTS” error in Chrome, you’ve got a loop. Check your redirect rules carefully for circular references.
3. Not Updating Internal Links
This is one of the most common mistakes I see. You set up a 301 redirect from the old URL to the new one — great. But then you leave hundreds of internal links across your site still pointing to the old URL. Every time a visitor or Google follows one of those links, they hit the redirect before reaching the page.
The fix: After setting up redirects, go through your site and update all internal links to point directly to the new URLs. Redirects are a safety net, not a substitute for proper internal linking. In WordPress, a search-and-replace tool like Better Search Replace makes this quick work.
4. Forgetting to Redirect Your Old Sitemap URLs
When you redesign a site, the old XML sitemap may still be cached by Google or listed in Search Console. If it contains URLs that no longer exist and you haven’t set up redirects, Google will try to crawl all those dead pages and find 404 errors everywhere.
The fix: After a migration, submit your new sitemap to Google Search Console and make sure every URL in your old sitemap either still works or has a 301 redirect in place.
5. Using 301 Redirects for Temporary Changes
If you’re temporarily sending visitors to a different page — during maintenance, for a seasonal promotion, or while running an A/B test — use a 302, not a 301. A 301 tells Google the move is permanent, and it will update its index accordingly. If you then remove the redirect, Google has to reprocess the change, which wastes time and can briefly hurt your rankings.
6. Redirecting Everything to the Homepage
I see this one a lot during site migrations. Rather than mapping old URLs to their most relevant equivalents on the new site, someone redirects every old page to the homepage. Google calls these “soft 404s” — they technically work, but they don’t pass link equity properly because the content doesn’t match. Always redirect to the most relevant equivalent page.
7. Not Monitoring After Launch
You’ve set up your redirects and launched the new site. Job done? Not quite. Check Google Search Console over the following weeks for crawl errors. Look at your analytics to make sure traffic to key pages hasn’t dropped. Run a crawl with Screaming Frog to catch anything you’ve missed. Redirects need monitoring, not just setting up.
How to Check If Your 301 Redirects Are Working
Setting up redirects is only half the job. You need to verify they’re actually working correctly. Here are three reliable methods.
Method 1: Your Browser
The simplest check. Type the old URL into your browser’s address bar and hit Enter. If the redirect is working, you should land on the new page and the URL in the address bar should update to the new address. If you see a 404 error or end up somewhere unexpected, something’s wrong.
To verify the redirect type, open Chrome DevTools (press F12), go to the Network tab, and reload the page. Look for the old URL in the list — the Status column should show 301. If it shows 302, you’ve used a temporary redirect when you likely wanted a permanent one.
Method 2: The Command Line (curl)
If you’re comfortable with the command line, this is the fastest way to check:
curl -I https://yourdomain.co.uk/old-pageLook for HTTP/1.1 301 Moved Permanently (or HTTP/2 301) in the response, followed by a Location: header showing the new URL. This tells you exactly what the server is doing with that request.
Method 3: Screaming Frog SEO Spider
For site-wide redirect auditing, Screaming Frog is the industry standard tool. Crawl your site and filter by status code to see all redirects at once. It’ll flag redirect chains, loops, and any redirects pointing to 404 pages. The free version crawls up to 500 URLs, which is enough for most small business websites.
I run a Screaming Frog crawl after every site migration as part of my SEO service. It’s the only way to be confident that nothing’s been missed.
The SEO Impact of 301 Redirects
Here’s the question everyone wants answered: do 301 redirects pass SEO value?
Yes, they do. Google has confirmed that 301 redirects pass link equity (sometimes called “link juice”) to the destination page. In practice, a well-implemented 301 redirect passes the vast majority of a page’s ranking power to the new URL.
There used to be a widespread belief that 301 redirects caused a 15% loss in link equity. Google’s own Gary Illyes has clarified that 301, 302, and other redirect types no longer lose PageRank. The ranking signals are passed through. That said, I’d still recommend 301 for permanent moves because it sends the clearest signal to search engines about the nature of the change.
What happens to rankings after a 301 redirect?
In most cases, you’ll see a brief fluctuation in rankings as Google processes the redirect and recrawls the new URL. For a straightforward page-to-page redirect on the same domain, this typically settles within a few days to a couple of weeks. For larger migrations — like moving to a new domain — expect fluctuations lasting several weeks to a few months.
The key factors that determine how smoothly your rankings transfer:
- Content relevance. Redirecting to a page with similar content preserves more ranking value than redirecting to an unrelated page.
- Speed of implementation. Set up your redirects before or at the moment of launch, not days or weeks later. Every day without redirects is a day where Google sees 404 errors instead of your content.
- Clean execution. No chains, no loops, no broken redirects. A clean redirect map is critical for large migrations.
When NOT to Use a 301 Redirect
301 redirects are powerful, but they’re not always the right solution. Here are situations where you should think twice.
- The page should still exist. If the original URL is still valid and the content hasn’t moved, you don’t need a redirect. Sometimes people set up redirects when what they actually need is a canonical tag to handle duplicate content.
- The move is temporary. As covered earlier, temporary changes should use a 302 redirect. Maintenance pages, seasonal promotions, and A/B tests are all temporary.
- You’re trying to manipulate rankings. Redirecting a bunch of unrelated old domains to your site to pass link equity is a tactic that Google has been penalising for years. It doesn’t work, and it can get your site demoted or removed from search results entirely.
- The page has no value. If a page had no traffic, no inbound links, and no rankings, there’s no SEO reason to redirect it. Letting it return a 404 (or better, a custom 404 page with helpful navigation) is perfectly fine.
- You want to remove content from Google’s index. A 301 redirect tells Google the content has moved, which keeps the content in the index under a new URL. If you want content gone from Google entirely, you need a 410 (gone) status code or use Google Search Console’s removal tool.
A Quick 301 Redirect Checklist
Before I wrap up, here’s a practical checklist I use for every site migration and URL change. Feel free to save this.
- Map your old URLs to new URLs in a spreadsheet before making any changes.
- Set up 301 redirects using a WordPress plugin, .htaccess, or Nginx config.
- Test every redirect to confirm it works and returns a 301 status code.
- Update all internal links to point to the new URLs directly.
- Submit your new sitemap to Google Search Console.
- Check for redirect chains and loops using Screaming Frog or a similar crawler.
- Monitor Google Search Console for crawl errors over the next two to four weeks.
- Watch your analytics for unexpected traffic drops to key pages.
- Keep your redirect rules in place indefinitely. Don’t remove them after a few months — inbound links from other sites may point to the old URLs for years.
Frequently Asked Questions About 301 Redirects
How long should I keep a 301 redirect in place?
Indefinitely, or at least for as long as the old URL might receive traffic. Inbound links from other websites, bookmarks, printed materials, and social media posts can keep sending visitors to old URLs for years. There’s no penalty for keeping redirects active, so leave them in place. Removing them too early just creates unnecessary 404 errors.
Do 301 redirects hurt page speed?
A single 301 redirect adds a tiny amount of latency — typically under 100 milliseconds. That’s negligible. The problem arises with redirect chains, where multiple hops stack up. A chain of three or four redirects can add noticeable delay and frustrate users. Keep your redirects direct (one hop) and there’s no meaningful impact on speed.
Can I set up a 301 redirect without access to my server?
If you’re on WordPress, yes — use a plugin like Redirection, Yoast Premium, or Rank Math. These handle redirects at the application level without needing server access. If you’re on a managed platform like Squarespace or Shopify, these platforms have their own built-in redirect tools in the settings panel. If you’re on a static site without CMS access, you’ll need access to your server configuration or your hosting control panel.
Will a 301 redirect fix a 404 error in Google Search Console?
Yes. Once you set up a 301 redirect and Google recrawls the URL, the 404 error will be resolved in Search Console. This can take anywhere from a few days to a few weeks depending on how frequently Google crawls your site. You can speed things up by using the URL Inspection tool in Search Console to request a recrawl of the specific URL.
What’s the difference between a 301 redirect and a canonical tag?
A 301 redirect physically sends visitors and search engines from one URL to another — the old page is inaccessible. A canonical tag (rel="canonical") is an HTML hint that tells Google which version of a page is the “main” one when multiple versions exist, but both pages remain accessible. Use a 301 when the old page should no longer exist. Use a canonical when both pages need to exist but you want Google to prioritise one of them.
How many 301 redirects can my site have?
There’s no hard limit from Google’s side. Sites with thousands of redirects function perfectly fine. The key is that each individual redirect should be clean and direct — no chains, no loops. If you’re running a large site with years of URL changes behind it, having hundreds of redirects in your .htaccess file or redirect plugin is completely normal and won’t cause issues.
Need Help With 301 Redirects or a Site Migration?
If you’ve read this far, you’ve got a solid understanding of how 301 redirects work and why they matter. For simple URL changes, the WordPress plugin approach is straightforward enough that most business owners can handle it themselves.
But for site migrations, domain changes, or situations where you’ve got hundreds of URLs that need mapping, having someone who’s done it dozens of times before makes a real difference. One missed redirect can mean a key page drops out of Google entirely.
I’ve handled site migrations for businesses across the UK — from small local service companies to larger e-commerce sites — and redirects are always a core part of that process. If you’re planning a redesign, moving to a new domain, or you’ve noticed crawl errors piling up in Search Console, I can help.
Take a look at my SEO services, my WordPress web design work, or my guide on responsive web design in 2026 if you’re thinking about a rebuild. And if you’d like to have a conversation about what your site needs, get in touch. No hard sell — just honest advice from someone with 51 five-star reviews and a genuine interest in getting it right.
