Changing a page URL seems simple until visitors start landing on broken links, old pages remain in Google, or a valuable service page loses search visibility.
A redirect tells browsers and search engines where to go when someone requests a URL that has moved. But choosing the wrong redirect type can create problems that are not immediately obvious.
The 301 vs 302 redirect decision comes down to one question: Is the URL change permanent or temporary?
A 301 redirect tells search engines that a page has permanently moved. A 302 redirect sends visitors to another location temporarily, without signaling that the original URL should be permanently replaced.
For WordPress website owners, understanding that distinction matters when updating permalinks, deleting outdated pages, redesigning a website, running temporary campaigns, or reorganizing content.
This guide explains when to use each redirect, how they affect SEO, and how to configure and test them in WordPress using plugins or server-level rules.
Key Takeaways
- 301 redirects are permanent. Use them when a page has moved, a permalink has changed permanently, or two pages have been consolidated.
- 302 redirects are temporary. Use them when visitors need a temporary alternative but the original URL is expected to return.
- Both redirect types send visitors to another URL, but they communicate different signals to search engines.
- A WordPress redirect plugin is often the easiest way to manage redirects without editing server files.
- Redirects should point to the most relevant destination, not automatically to the homepage.
- Always test response codes, redirect chains, destination pages, and internal links after making changes.
301 vs 302 Redirect: What Is the Difference?
Both 301 and 302 are HTTP status codes that tell a browser to request another URL.
For example, suppose a plumbing company changes its service page from:
https://example.com/plumbing-services
to:
https://example.com/residential-plumbing
A visitor using the old address should reach the new page instead of seeing a 404 error.
A redirect makes that possible.
The difference is what the redirect communicates about the original address.

What Is a 301 Redirect?
A 301 redirect means “Moved Permanently.”
It tells browsers and search engines that the requested resource has a new permanent location.
When Google encounters a properly implemented 301 redirect, it treats the destination URL as a strong canonicalization signal. Over time, Google may replace the old URL with the new destination in search results.
A WordPress 301 redirect is appropriate when:
- A blog post receives a new permanent URL.
- A service page moves into a different website section.
- Two similar articles are combined into one stronger resource.
- A business moves from an old domain to a new domain.
- HTTP URLs are permanently redirected to HTTPS.
- An outdated product has a closely relevant permanent replacement.
For example:
/services/roof-repairs/ → /roof-repair/
If the company intends to keep the second URL permanently, a 301 redirect is the appropriate choice.
Importantly, a 301 redirect does not guarantee that rankings will remain unchanged. Google still evaluates the destination’s content, relevance, and other ranking signals.
What Is a 302 Redirect?
A 302 redirect means “Found” and is commonly used to indicate a temporary move.
Visitors are sent to another URL, but the original address remains the intended long-term location.
Consider an online retailer temporarily redirecting a product page to an availability notice while the item is out of stock.
For example:
/products/custom-office-desk/ → /products/office-desk-temporarily-unavailable/
If the original product page will return, a 302 redirect may be appropriate.
Google generally treats temporary redirects differently from permanent redirects. A 302 does not independently signal that the destination should replace the original URL as the canonical page.
However, Google may still index the destination based on other signals.
According to Google Search Central’s documentation on redirects, permanent redirects signal that the destination should be considered canonical, while temporary redirects do not provide that same canonicalization signal.
301 vs 302 Redirect Comparison
| Feature | 301 Redirect | 302 Redirect |
| Meaning | Moved Permanently | Temporary redirect |
| Primary purpose | Permanent URL change | Short-term URL change |
| SEO signal | Destination is a strong canonical candidate | Does not signal a permanent canonical change |
| Original URL in Google | Usually replaced over time | Generally intended to remain |
| Best for | URL changes, migrations, consolidation | Temporary maintenance, testing, short-term alternatives |
| Browser caching | May be cached as a permanent redirect | Caching depends on response headers |
| Can be reversed? | Yes, but search engines may need time to process the change | Yes, typically intended to be reversed |
| WordPress setup | Plugin or server configuration | Plugin or server configuration |
The important distinction is not whether one redirect is universally better for SEO.
It is whether the redirect accurately describes what is happening to the page.
When Should You Use a 301 or 302 Redirect?
The easiest way to choose between redirect types is to look at the intended lifespan of the original URL.
If the original address is being retired permanently, use a 301.
If the original address will be used again, consider a 302.
Real WordPress websites encounter several situations where this choice matters.

Use a 301 When Permanently Changing WordPress URLs
Suppose a local HVAC business publishes an article at:
/blog/air-conditioner-repair-tips/
Later, the marketing team reorganizes the website and moves the article to:
/resources/ac-repair-guide/
The content has a permanent new address.
A 301 redirect should connect the old URL to the new one.
This matters because customers may still reach the old address through bookmarks, old social media posts, directory listings, or backlinks.
Without the redirect, those visitors could encounter a 404 error.
If the new page is substantially equivalent to the original, the redirect also helps search engines understand where the content moved.
Businesses changing multiple URLs should document those changes before deployment. The website migration checklist explains broader migration considerations, including URL mapping and technical testing.
Use a 301 When Consolidating Similar Content
Imagine a home remodeling company has three WordPress blog posts:
- /bathroom-renovation-planning/
- /bathroom-remodeling-guide/
- /bathroom-renovation-checklist/
All three cover overlapping information and compete for similar search queries.
The company decides to combine the useful material into a comprehensive bathroom renovation resource.
Rather than deleting the weaker articles and leaving broken links, it can redirect their old URLs to the consolidated guide.
A suitable redirect map might look like this:
| Old URL | New URL | Redirect |
| /bathroom-renovation-planning/ | /bathroom-renovation-guide/ | 301 |
| /bathroom-remodeling-guide/ | /bathroom-renovation-guide/ | 301 |
| /bathroom-renovation-checklist/ | /bathroom-renovation-guide/ | 301 |
This works best when the destination genuinely covers the information visitors expected.
Redirecting unrelated content to a broad service page simply to avoid a 404 is not a good substitute.
Use a 302 for Temporary Website Changes
Temporary redirects are useful when a page’s original address will become active again.
Examples include:
Temporary service interruption
A booking page is unavailable while a company updates its scheduling software. Visitors are temporarily directed to an alternative booking page.
Short-term campaign changes
A business temporarily sends visitors from an existing promotion URL to a replacement page during a scheduled campaign.
Website experiments
A marketing team tests an alternative landing page and plans to restore the original after the experiment.
Temporary product availability
A retailer temporarily directs visitors to an availability notice or relevant alternative while a product page cannot serve its normal purpose.
Not every temporary content change requires a redirect. If the original page remains useful, updating it with a clear notice may be better.
For website experiments, Google’s guidance on A/B testing recommends using a 302 rather than a 301 when temporarily redirecting users to a test variation.
When a Redirect Is Not the Right Solution
Not every missing WordPress page needs to redirect somewhere.
Consider a business that permanently stops offering a specialized service.
The original page has no replacement and no closely relevant destination.
Redirecting it to the homepage may confuse visitors because the homepage does not provide the information they requested.
In this situation, allowing the URL to return a 404 or 410 response may be more appropriate.
Similarly, if an internal link contains a typo, fix the link directly instead of automatically creating a redirect for every mistake.
The distinction matters because redirects solve address changes, not every content problem.
For a broader explanation of missing-page handling, see the guide to 404 errors and broken pages.
How to Set Up 301 and 302 Redirects in WordPress
WordPress provides several ways to manage redirects.
The best method depends on the number of URLs involved, the website’s hosting configuration, and who maintains the site.
For a typical small business website, using a reliable WordPress redirect plugin is usually the most manageable option.
For large migrations or specialized configurations, server-level redirects may be preferable.
Method 1: Set Up Redirects Using the Redirection Plugin
Best for: Small business websites, blog URL changes, content consolidation, and administrators who prefer a dashboard.
The Redirection plugin by John Godley allows WordPress administrators to manage redirects without directly editing Apache or Nginx configuration files.
It also supports redirect logs, 404 monitoring, and URL matching rules, as described in its official WordPress plugin listing.
Here’s how to create a redirect.
Step 1: Install the plugin
- Log in to the WordPress dashboard.
- Navigate to Plugins → Add New.
- Search for “Redirection” by John Godley.
- Install and activate the plugin.
- Complete the initial configuration process.
Before installing another plugin, check whether your existing SEO plugin or hosting provider already manages redirects.
Using multiple redirect systems unnecessarily can create conflicting rules.
Step 2: Open the redirect manager
Navigate to:
Tools → Redirection
The interface includes fields for defining the source URL and destination URL.
Step 3: Enter the original URL
Suppose you changed a WordPress post URL from:
/blog/website-care-tips/
to:
/blog/website-maintenance-guide/
Enter the old path in the Source URL field:
/blog/website-care-tips/
Step 4: Enter the destination
Enter the new URL in the Target URL field:
https://example.com/blog/website-maintenance-guide
Make sure the destination exists and returns a successful response.
Step 5: Choose the redirect type
Under the relevant redirect settings, select the appropriate HTTP status code.
Use:
- 301 for a permanent move.
- 302 for a temporary move.
Some plugin interface options may be under an advanced settings menu.
Step 6: Save and test
Select Add Redirect, then open the old address in a private browser window.
Confirm that visitors arrive at the correct destination.
Browser testing confirms the visitor experience, but a separate HTTP status check is still necessary to verify that the server returns the intended redirect code.
Method 2: Create Redirects With Rank Math
Best for: Websites already using Rank Math for SEO.
If Rank Math is installed, adding another WordPress redirect plugin may be unnecessary.
Rank Math includes a redirection module that supports common redirect types, including 301 and 302.
To configure a redirect:
- Open the WordPress dashboard.
- Navigate to Rank Math SEO → Dashboard.
- Enable the Redirections module if it is not already active.
- Open Rank Math SEO → Redirections.
- Select Add New.
- Enter the old URL under Source URLs.
- Enter the replacement under Destination URL.
- Select either 301 Permanent Move or 302 Temporary Move.
- Activate and save the rule.
Menu locations can vary depending on the plugin version and configuration.
One advantage of using an existing SEO plugin is keeping related technical SEO settings within the same management system.
However, avoid enabling automatic redirects without reviewing their targets.
A changed permalink does not always mean that the new destination is the best page for the visitor.
Method 3: Set Up WordPress 301 Redirects Using .htaccess
Best for: Apache hosting environments and administrators comfortable editing server configuration files.
WordPress websites hosted on Apache may use a .htaccess file to manage redirects.
This file typically sits in the website’s root directory.
Before editing it, download a backup. A malformed rule can interrupt access to the website.
A basic permanent redirect may look like this:
Redirect 301 /old-service/ https://example.com/new-service/
When someone requests /old-service/, Apache returns a 301 response pointing to the new address.
For a temporary redirect:
Redirect 302 /temporary-offer/ https://example.com/current-offer/
The basic format is:
Redirect STATUS OLD_PATH NEW_URL
Place custom directives in an appropriate configuration location, outside WordPress-managed blocks that may be overwritten. Confirm that the required Apache module is available and check for competing rules.
These examples apply to Apache configuration, not every WordPress hosting environment.
On Nginx, .htaccess files do not control redirects.
Method 4: Configure Redirects With Nginx
Websites using Nginx generally require redirect rules in the server configuration.
A permanent redirect can be defined as:
location = /old-service/ {
return 301 https://example.com/new-service/;
}
For a temporary redirect:
location = /temporary-offer/ {
return 302 https://example.com/current-offer/;
}
The distinction is the status code returned with the new location.
Administrators typically need to test the configuration and reload Nginx after making changes.
On managed hosting platforms, direct access to Nginx configuration may be restricted. In that case, the hosting dashboard or a supported plugin is usually the safer option.
For additional implementation details, WordPress developers can review the official WordPress wp_redirect() function documentation, which explains how WordPress sends HTTP redirect responses programmatically.
Custom PHP implementations should be handled carefully, especially when dealing with user-supplied destination URLs.

Which WordPress Redirect Method Should You Choose?
| Method | Best use case | Technical difficulty | Main consideration |
| Redirection plugin | Individual URLs and everyday maintenance | Low | Requires plugin management |
| Rank Math Redirections | Sites already using Rank Math | Low | Avoid duplicate redirect systems |
| Apache .htaccess | Server-controlled redirect rules | Medium to high | Incorrect rules can disrupt the website |
| Nginx configuration | Custom hosting and technical migrations | High | Requires server access and testing |
| Hosting redirect manager | Host-supported redirect rules | Low to medium | Features vary by provider |
For most small WordPress websites, the best method is the one that can be maintained consistently without introducing conflicting rules.
How to Test Redirects and Avoid Common SEO Mistakes
Creating the redirect is only half the job.
A redirect can appear to work in a browser while returning the wrong HTTP status, sending visitors through multiple URLs, or pointing to a page that no longer exists.
Those problems become particularly important when a business is changing dozens or hundreds of WordPress URLs.
Check the HTTP Status Code
A browser automatically follows redirects, which makes it difficult to see the original server response.
A command-line tool such as curl can reveal the status code.
For example:
curl -I https://example.com/old-service/
A correctly configured permanent redirect might return:
HTTP/2 301
location: https://example.com/new-service/
For a temporary redirect, the expected response would contain:
HTTP/2 302
location: https://example.com/temporary-service/
The final destination should normally return 200 OK when it is an active page.
The -I option requests headers using HEAD. If a server handles HEAD requests differently from GET requests, test with a normal GET request and inspect the headers instead.
Avoid Redirect Chains
A redirect chain occurs when one redirected URL leads to another redirected URL before reaching the final page.
For example:
/old-page/ → /updated-page/ → /new-page/ → /current-page/
Every additional step creates another request.
Long redirect chains may increase loading time, complicate crawling, and make future website maintenance harder.
The cleaner approach is:
/old-page/ → /current-page/
This is especially important during redesigns when URLs may have changed multiple times.
Review existing redirects before adding new ones. Otherwise, older rules can silently create unnecessary chains.
Prevent Redirect Loops
A redirect loop occurs when URL rules send requests back and forth without reaching a final page.
For example:
/page-a/ → /page-b/ → /page-a/
Visitors may see an error indicating that the page redirected too many times.
Common causes include:
- Conflicting WordPress plugins.
- Incorrect HTTPS or domain rules.
- Competing hosting and server redirects.
- Old URL rules that point back to themselves.
- Incorrect reverse-proxy or caching configurations.
When a loop appears, inspect the entire redirect path rather than repeatedly changing the destination.
Disable or adjust the conflicting rule after identifying which system controls it.
Update Internal Links Instead of Relying on Redirects
Suppose the navigation menu still links to:
/old-contact-page/
A 301 redirect sends visitors to:
/contact/
The navigation technically works, but the website is making an unnecessary redirect request every time someone clicks that menu item.
The better fix is to update the navigation link directly.
Check the following locations after changing WordPress URLs:
- Main navigation menus and footer links.
- Blog post links and related content blocks.
- Elementor, Divi, Gutenberg, or other page-builder buttons.
- Product and category links.
- XML sitemaps.
- Canonical URL settings.
- Email templates and important marketing links.
This is part of a broader WordPress content management process that keeps URLs, published content, and website navigation consistent.
Redirects should protect visitors arriving through old links. They should not replace updating links that the website owner can control.
Avoid Sending Every Old URL to the Homepage
Consider a roofing contractor that removes an old page about metal roof installation.
Redirecting that URL to the homepage may look like a quick fix.
But a visitor searching for metal roof installation information probably does not want a generic introduction to the company.
A closer replacement might be a current metal roofing service page.
Use the following decision process:
| Old page situation | Recommended action |
| Same content has a permanent new URL | 301 to the new URL |
| Closely related replacement exists | Consider a 301 to that page |
| Original page will return | Consider a 302 to a temporary alternative |
| Page is permanently removed with no replacement | Return 404 or 410 |
| Internal link contains an incorrect address | Fix the internal link |
| Old URL redirects through several pages | Point directly to the final destination |
Relevance matters more than simply eliminating every 404.

Monitor Redirects After Publishing
Search engines do not necessarily process URL changes immediately.
After implementing permanent redirects, review Google Search Console for changes in indexing and crawl behavior.
Pay attention to:
- URLs reported as pages with redirects.
- Unexpected 404 errors.
- Important destination URLs that are not indexed.
- Canonical URL selections.
- Changes in organic traffic to migrated pages.
A page labeled as redirected is not automatically a problem.
If the old URL intentionally redirects and the destination is accessible and indexable, that can be the expected result.
The objective is to confirm that Google can discover and understand the intended final page.
A Practical WordPress Redirect Checklist
The following process works for individual page changes, content cleanup projects, and larger website reorganizations.
Step 1: Identify the URLs That Will Change
Before editing anything, list every affected URL.
Include URLs from:
- Existing WordPress pages and posts.
- Google Search Console.
- XML sitemaps.
- Analytics reports.
- Internal link reports.
- Important external backlinks.
For small updates, a spreadsheet may be enough.
For a larger migration, a crawling tool can help identify URLs and internal linking relationships.
Step 2: Create a Redirect Map
Record the original address, its replacement, the intended redirect code, and the reason for the change.
For example:
| Old URL | New URL | Status | Reason |
| /old-services/ | /services/ | 301 | Permanent URL update |
| /summer-offer/ | /current-promotion/ | 302 | Temporary campaign change |
| /old-blog-guide/ | /updated-blog-guide/ | 301 | Content consolidation |
| /retired-product/ | None | 410 | Removed without replacement |
Adding an owner, implementation date, and testing status helps teams manage larger redirect lists.
For temporary redirects, record a review or removal date.
A 302 redirect should not be left in place indefinitely simply because nobody remembered to revisit it.
Step 3: Implement and Verify
Before deployment, back up relevant WordPress or server configuration data.
Then:
- Confirm the destination URL exists.
- Select 301 or 302 based on whether the move is permanent.
- Add the rule using one appropriate redirect system.
- Check the response status and Location header.
- Confirm the final destination loads successfully.
- Check that the redirect does not create a chain or loop.
- Test important URLs on desktop and mobile browsers.
- Clear relevant caches if old responses are still being served.
- Update internal links, canonical settings, and the sitemap where necessary.
- Monitor important pages after deployment.
For business-critical WordPress websites, test on a staging environment whenever possible, particularly when changing server rules or hundreds of URLs.
Step 4: Review the Results
After a URL change, check whether visitors and search engines are reaching the intended destination.
For permanent redirects, continue monitoring the old and new URLs while Google processes the change.
For temporary redirects, review whether the original page is ready to return.
Do not remove permanent redirects merely because the new page has started appearing in search results. Old backlinks, bookmarks, and marketing materials may continue sending visitors to the previous URL.
The objective is a stable, predictable website structure that remains understandable as content changes.
Make WordPress URL Changes Easier to Manage
Choosing between a 301 and 302 redirect should not be complicated.
When a page has permanently moved, use a 301. When the move is temporary and the original URL is expected to return, use a 302.
The bigger challenge is managing those redirects correctly as a WordPress website grows.
A reliable redirect process starts with mapping old URLs to relevant destinations, implementing the correct HTTP response, updating internal links, and testing the results.
Treat redirects as part of regular website management rather than an emergency fix after visitors begin reporting broken pages.
That approach helps keep WordPress websites easier to navigate, simpler to maintain, and better prepared for future content changes.
FAQs
Does a 301 redirect hurt SEO?
A properly implemented 301 redirect does not inherently hurt SEO. It helps search engines understand a permanent URL move, although rankings can still change because of destination content, technical errors, or other SEO factors. Redirecting to a relevant, accessible destination is more important than assuming a redirect automatically preserves every ranking.
Can a 302 redirect pass SEO value?
A 302 redirect can be followed by search engines, and Google evaluates multiple signals when deciding which URL to index. However, unlike a 301, it does not signal that the destination should permanently replace the source as canonical. Use a 302 because the move is temporary, not as a technique to manipulate rankings.
What is the best WordPress redirect plugin?
Redirection and Rank Math are practical options for managing WordPress redirects. Redirection is useful as a dedicated redirect manager, while Rank Math may be convenient for websites already using its SEO features. Choose one system that supports the required status codes, URL matching, and ongoing maintenance.
How do I redirect old URLs in WordPress without losing traffic?
Start by mapping each old URL to its closest relevant replacement. Configure a 301 redirect for permanent changes, update internal links, and confirm the destination is accessible and indexable. Monitor Search Console and organic traffic afterward because some ranking fluctuations may occur during URL transitions.
Can I change a 302 redirect to a 301 later?
Yes. If a temporary URL change becomes permanent, update the redirect to return a 301 response. Clear relevant caches and test the response afterward so browsers and search engines receive the updated instruction.
Should I use a 301 or 302 redirect for a deleted WordPress page?
Use a 301 if the deleted page has a relevant permanent replacement. Use a 302 only if the original page is expected to return and visitors need a temporary alternative. If there is no appropriate replacement, a 404 or 410 response may be more suitable than an unrelated redirect.
How long should I keep a 301 redirect in WordPress?
Keep permanent redirects for at least as long as Google needs to process the move, and generally longer when old URLs still receive traffic or have valuable backlinks. For important business URLs, maintaining redirects indefinitely can be reasonable when there is little operational cost. Review old rules periodically, but avoid deleting useful redirects simply because they are several years old.