Explainers · Explainer
What Is a 301 Redirect? A Plain Explanation

Short answer
A 301 redirect is a server reply that tells a browser and a search engine that a page has moved to a new address for good. The server answers with status code 301 and a Location header naming the new address, and the browser loads the new page instead. Google treats a 301 as a signal that the new address should be the one shown in search results, so use it only when you are sure the move will not be reverted.
Key takeaways
- A 301 redirect is a server reply with status code 301 and a Location header that sends visitors to the new address.
- Google treats a 301 as a signal that the new address should be shown in search results, while a 302 keeps the old address.
- Use a 301 when a page has moved for good, when pages merge, or when a site moves to a new domain.
- WordPress wp_redirect() defaults to status 302, so pass 301 when you need a permanent redirect in code.
- Check a redirect with curl -I and keep the rule for at least a year when the old address still gets traffic.
What is a 301 redirect?
A 301 redirect is a server reply that tells a browser and a search engine that a page has moved to a new address for good.
The number 301 is the HTTP status code for “moved permanently”. When a visitor opens the old address, the server answers with a 301 status and a Location header that names the new address, and the browser loads the new page instead.
Google Search Central defines redirecting as the practice of resolving an existing URL to a different one, telling visitors and Google Search that a page has a new location (checked November 2026).
A 301 redirect is a signal, not a guarantee. Google Search Central states that Google Search uses some redirect types as a signal that the redirect target should be canonical, which is the address shown in search results (checked November 2026).
The old address keeps working as a doorway. Anyone who clicks an old link, a bookmark, or a search result lands on the new page without seeing an error.
How does a 301 redirect work?
The server sends a 301 status code plus the new address, and the browser then requests the new address on its own.
The exchange has three steps. First, the browser asks for the old URL, and the server replies with status 301 and a Location header holding the new URL.
Then the browser requests the new URL and shows that page.
Google Search Central states that the 301 and 308 status codes mean that a page has permanently moved to a new location (checked November 2026).
Google follows the redirect and treats the new address as the one to show in search results. Google Search Central states that for permanent redirects, Googlebot follows the redirect, and the indexing pipeline uses the redirect as a signal that the target should be canonical (checked November 2026).
Google Search Central gives this PHP example, and notes that headers must be set before anything is sent to the screen (checked November 2026).
header('HTTP/1.1 301 Moved Permanently');
header('Location: https://www.example.com/newurl');
exit();
In WordPress, the wp_redirect() function sends a redirect, but its default status is 302, not 301. Developer.WordPress.org states that the default status is 302, and that the function does not exit on its own, so it should almost always be followed by a call to exit; (checked November 2026).
What is the difference between a 301 and a 302 redirect?
A 301 redirect says the move is permanent, while a 302 redirect says the move is only temporary.
The choice decides which address Google shows in search results. Google Search Central states that permanent redirects show the new redirect target in search results, while temporary redirects show the source page (checked November 2026).
Google groups the status codes like this. Google Search Central lists 301 and 308 as permanent, and 302, 303, and 307 as temporary, along with meta refresh and JavaScript methods (checked November 2026).
| Status code | Meaning | Google shows in results |
|---|---|---|
| 301 | Moved permanently | The new address |
| 308 | Moved permanently | The new address |
| 302 | Found, temporary move | The old address |
| 303 | See other, temporary | The old address |
| 307 | Temporary redirect | The old address |
Use 301 only when you are sure the old address will not come back. Google Search Central states that you should use permanent redirects when you are sure that the redirect will not be reverted (checked November 2026).
When should you use a 301 redirect?
Use a 301 redirect when a page has moved for good, when two pages merge into one, or when a site moves to a new domain.
Google lists four common cases. Google Search Central names a move to a new domain, several URLs for one home page, merging two websites, and a removed page that should send users to a new page (checked November 2026).
A domain move needs a 301 for every old address, not just the home page. Each old page should point at the matching new page, so a visitor who clicks an old link lands on the same content at the new domain.
When should you NOT use a 301 redirect?
Do not use a 301 redirect for a short-term change, for a page that will return, or as a quick fix for a page you have not decided about yet.
A temporary move needs a 302, not a 301. Google Search Central states that if you just want to send users to a different page briefly, you should use a temporary redirect, which helps keep the old URL in search results (checked November 2026).
Do not add a 301 before you know the final address. If the new page moves again a week later, you will build a chain of redirects, and each extra step slows the page down and weakens the signal.
How do you set up a 301 redirect in WordPress?
Use a redirect plugin such as Redirection, which manages 301 redirects from the dashboard without editing server files.
WordPress.org describes Redirection as a redirect manager that lets you manage 301 redirections, keep track of 404 errors, and tidy up loose ends on your site (checked November 2026).
Follow these steps after you install and activate the plugin:
- Open Tools, then Redirection, in the dashboard.
- Enter the old address in the Source URL field, starting with a slash.
- Enter the new address in the Target URL field.
- Check that the type is set to 301 before you save.
- Open the old address in a private window to confirm it lands on the new page.
The plugin can also watch for slug changes and create the redirect for you. WordPress.org states that it can monitor when post or page permalinks change and automatically create a redirect to the new URL (checked November 2026).
A guide on how to set up 301 redirects in WordPress covers the full setup, including the Yoast SEO redirect tool as an alternative.
How do you set up a 301 redirect in .htaccess?
Add a Redirect line or a RewriteRule above the WordPress markers in the .htaccess file on an Apache server.
The simplest form uses mod_alias, and Google gives this exact example. Google Search Central shows Redirect permanent "/old" "https://example.com/new" for a permanent redirect, and Redirect temp for a temporary one (checked November 2026).
For a pattern that matches many addresses, use mod_rewrite instead. Google Search Central gives this example for sending one service page to a new page with a permanent redirect (checked November 2026).
RewriteEngine on
RewriteRule "^/service$" "/about/service" [R=301]
The [R=301] flag is what makes the rule send a 301 status. Without a status number, the same rule sends a temporary redirect, so check the flag before you save.
Note that rules in this file match a path without its leading slash. Apache states that in .htaccess context, the leading slash is removed from the value given to RewriteRule (checked November 2026).
On Nginx, the same job uses a return 301 line in the server config. Google Search Central gives this example for a permanent redirect on Nginx (checked November 2026).
location = /service {
return 301 $scheme://example.com/about/service;
}
A guide on how to change permalinks without breaking SEO explains when a redirect is needed after a permalink change, and which old addresses to map.
How do you check that a redirect works?
Open the old address in a private window, then confirm the status code and the destination with a header check.
The private window test shows what a visitor sees. Type the old address, press Enter, and confirm that the browser lands on the new page and that the address bar shows the new URL.
Then check the status code, since a page that lands in the right place can still send the wrong code. Run curl -I followed by the old address in a terminal, and read the first line of the reply plus the Location header.
A correct 301 reply looks like this:
HTTP/1.1 301 Moved Permanently
Location: https://www.example.com/new-page/
If the first line says 302, the redirect is temporary, even if the destination is right. That often happens when code calls wp_redirect() without passing 301 as the status, since the function defaults to 302 (checked November 2026).
What mistakes cause redirect chains and loops?
A chain happens when one redirect points at another redirect, and a loop happens when redirects point at each other in a circle.
A chain looks like this: /old/ points to /new/, and /new/ points to /newer/. The visitor waits through two jumps, and Google may stop following before it reaches the final page.
A loop looks like this: /a/ points to /b/, and /b/ points back to /a/. The browser gives up and shows an error about too many redirects, and no visitor reaches either page.
Fix a chain by pointing every old address straight at the final address. Fix a loop by listing every redirect rule for the two addresses, in the plugin and in .htaccess, and removing the one that sends traffic back.
A guide on how to fix too many redirects covers the loop case step by step.
A guide on what causes too many redirects explains the common setups that create one.
What myths about 301 redirects should you ignore?
The first myth is that a 301 passes all of a page search value to the new address at once.
The second myth is that a 301 removes the old address from search results at once. Google Search Central states that after a move to a new domain, Google will likely keep showing the old URLs in the results for a while, even though the new URLs are already indexed (checked November 2026).
The third myth is that a meta refresh works just like a 301. Google treats only an instant meta refresh, with a delay of 0 seconds, as a permanent redirect, while a delayed refresh counts as temporary (checked November 2026).
How long should you keep a 301 redirect?
Keep a 301 redirect in place for at least a year, and longer when the old address still gets traffic or links.
Google keeps track of both the old address and the new one after a redirect. Google Search Central states that when you redirect a URL, Google keeps track of both the redirect source and the redirect target, and one of them becomes the canonical address (checked November 2026).
A redirect with zero hits for many months is a fair candidate for removal, but only after you confirm that no live page on your own site still links to the old address. Update those links first, so the removal cannot break your own pages.
A guide on how to move a WordPress site without losing SEO covers the wider checklist for a move, including the sitemap and internal links that should match the new addresses.
Frequently asked questions
Can I use a 301 redirect for a temporary move?
No. Use a 302 redirect for a short-term move, such as a page that is briefly unavailable. A 301 tells Google the move is permanent and that the new address should be shown in search results, so a 302 is the safer choice when the old page will return.
Does a 301 redirect pass all search value to the new page?
It is a signal, not a guarantee. Google weighs the redirect with other signals, such as links and the content of the new page, so the new page still needs to match what visitors asked for. The old address can also keep appearing in results for a while after the move.
What is the difference between a redirect chain and a redirect loop?
A chain sends a visitor through two or more redirects before reaching the final page, while a loop sends them in a circle until the browser gives up. Fix a chain by pointing every old address straight at the final address, and fix a loop by removing the rule that sends traffic back.
Can a plugin create the 301 redirect for me?
Yes, in most cases. A redirect plugin such as Redirection can create the redirect when a slug changes, and it can also write rules to .htaccess for Apache. Check the type is set to 301 before you save, since WordPress code defaults to 302.
How do I check that my 301 redirect works?
Open the old address in a private window to confirm it lands on the new page, then run curl -I on the old address and check that the first line says 301 Moved Permanently and the Location header names the new address.
How long should I keep a 301 redirect?
Keep it for at least a year, and longer when the old address still gets traffic or links. Check the hit count in your redirect plugin first, and update any links on your own site that still point at the old address before you remove the rule.
Sources
- Redirects and Google Search Google Search Central
- wp_redirect() WordPress Developer Resources
- Redirection plugin WordPress.org
- Apache HTTPD / .htaccess WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


