Redirects send visitors and search engines from one URL to another. They are essential when you move pages, change URLs, merge content or switch domains. But choosing the wrong type of redirect, or setting redirects up carelessly, can confuse search engines, waste crawl resources and lose the value of links you worked hard to earn.
This guide explains the difference between 301 and 302 redirects, when to use each, how other redirect types fit in and how to implement redirects correctly on WordPress.
What Is a Redirect?
A redirect is an instruction from the server telling browsers and crawlers that the requested URL now lives somewhere else. Users are taken automatically to the new location, usually without noticing.
Types of Redirects
| — | — | — |
|---|---|---|
| 301 Moved Permanently | Page has moved permanently | URL changes, merged content, domain migrations |
| 302 Found | Page is temporarily elsewhere | Short-term promotions, A/B tests, maintenance |
| 307 Temporary Redirect | Temporary, preserves request method | Technical temporary redirects |
| 308 Permanent Redirect | Permanent, preserves request method | Technical permanent redirects |
| Meta refresh | Browser-level redirect after a delay | Not recommended for SEO |
How Search Engines Treat 301 and 302
A 301 redirect is a strong signal that the new URL should replace the old one in search results. Google consolidates signals such as links to the new URL. A 302 redirect suggests the original URL will return, so search engines may keep the original URL indexed.
Google has said that it can treat long-standing 302 redirects as permanent if they remain in place for a long time, but relying on this is unwise. Use the redirect type that matches your intention.
When to Use a 301 Redirect
- You changed a post’s URL slug
- You merged two similar articles into one
- You deleted a page and have a relevant replacement
- You moved from HTTP to HTTPS
- You switched from www to non-www or vice versa
- You migrated to a new domain
- You restructured categories or URL formats
When to Use a 302 Redirect
- A product page temporarily redirects during a limited sale
- A page is under maintenance and will return
- You are testing a new version of a page temporarily
- Users are temporarily sent to a location-specific page
Redirect Best Practices
Redirect to the most relevant page
Send users to the page that best replaces the old content. Redirecting everything to the homepage is confusing and may be treated as a soft 404.
Avoid redirect chains
A chain occurs when URL A redirects to B, which redirects to C. Chains slow down users and crawlers. Update redirects so A points directly to C.
Avoid redirect loops
A loop occurs when URLs redirect back to each other endlessly, making pages inaccessible. Test redirects after creating them.
Update internal links
After redirecting, update internal links to point directly to the final URL. Redirects should catch old external links and bookmarks, not handle your own navigation.
Keep redirects in place
Keep permanent redirects for a long time, ideally at least a year and often indefinitely, especially if old URLs have backlinks.
Update sitemaps
Remove redirected URLs from your sitemap and include only final destination URLs.
How to Set Up Redirects in WordPress
| — | — | — |
|---|---|---|
| Redirection plugin | Easy interface, logs 404s | Adds a plugin |
| .htaccess (Apache) | Fast, server-level | Mistakes can break the site |
| Hosting control panel | Simple for domain-level redirects | Limited flexibility |
| Nginx configuration | Fast, server-level | Requires server access |
For most WordPress users, a redirect plugin is the safest option. It also helps you find 404 errors that need redirecting.
Redirects During Site Migrations
Domain or structure migrations require careful planning:
- Create a complete list of old URLs and map each to its new URL
- Implement 301 redirects for every important page
- Test a large sample of redirects before and after launch
- Update internal links, canonicals and sitemaps
- Use the Change of Address tool in Search Console for domain moves
- Monitor Search Console for errors in the following weeks
How to Check Redirects
- Use a redirect checker tool to see the status codes and path
- Run a site crawl to find chains, loops and redirected internal links
- Use browser developer tools to inspect network responses
Common Redirect Mistakes
- Using 302 for permanent changes
- Redirecting all deleted pages to the homepage
- Creating chains through repeated URL changes
- Removing redirects too soon
- Forgetting to update internal links and sitemaps
Real-World Example
A blog changed its permalink structure from /2023/05/post-name/ to /post-name/ without redirects. Hundreds of old URLs returned 404 errors, external links broke and traffic fell sharply. The owner installed a redirect plugin, created a rule to 301 redirect the old format to the new one and updated internal links. Over the following weeks, Google processed the redirects and most traffic returned.
Frequently Asked Questions
Do 301 redirects lose SEO value?
Google has said that 301 redirects do not cause a loss of PageRank. Signals are consolidated to the new URL.
How long should I keep a 301 redirect?
At least one year, and ideally permanently for URLs with backlinks or traffic.
Can I change a 302 to a 301 later?
Yes. If a temporary move becomes permanent, update the redirect type.
Should I redirect 404 pages?
Redirect only when there is a relevant replacement. Otherwise, a 404 is acceptable.
Are JavaScript redirects bad for SEO?
Google can process them, but server-side redirects are more reliable and recommended.
Do redirects slow down websites?
A single redirect adds minimal delay. Chains add more, so keep redirects direct.
Conclusion
Redirects protect users and SEO when URLs change. Use 301 redirects for permanent moves and 302 redirects for temporary situations, redirect to relevant pages, avoid chains and loops and keep internal links updated. With careful redirect management, you can restructure your site without losing traffic or link value.
