How to Set Up 301 Redirects in WordPress Without Breaking SEO

Every WordPress site changes shape over time. Pages get renamed, posts get merged, categories get restructured, and sometimes an entire domain moves. Each of those changes leaves behind a URL that used to work and no longer does, unless you point it somewhere new. That pointer is a redirect, and getting it wrong is one of the easiest ways to lose traffic and rankings you already earned without noticing until weeks later.

This guide covers when you actually need a redirect, which status code to use in each situation, how to set one up in WordPress, and the mistakes that turn a routine cleanup into a ranking problem.

When you actually need a redirect

Not every URL change needs a redirect, but most do. The test is simple: if a URL that used to resolve to a page now resolves to nothing, or resolves to a different page than the one a visitor or search engine expects, you need a redirect. Four situations account for almost every redirect you will ever create on a WordPress site.

You changed a URL slug

Renaming a post slug for clarity, fixing a typo in a URL, or restructuring your permalink pattern all break the old URL the moment you save the change. WordPress does not redirect the old slug to the new one automatically. Anyone who bookmarked the old URL, any external site linking to it, and any cached version of it in Google's index now points at a dead page unless you redirect it.

You deleted a page or post

Deleting content is sometimes the right call, but the URL does not disappear from the internet just because the page is gone. Old backlinks, social shares, and search results still point there. If a reasonable replacement exists on your site, redirect to it. If nothing on your site covers that topic anymore, a redirect may not be the right move at all, more on that in the mistakes section below.

You merged two pages into one

Consolidating two thin, overlapping pages into a single stronger one is a common and often correct SEO move. When you do it, the page you retire needs a redirect to the page you kept, so the authority and traffic that page had accumulated transfers to its replacement instead of evaporating.

You changed domains

Moving from an old domain to a new one, or switching from http to https, or adding or removing a www subdomain, changes every URL on your site at once. This is the highest stakes redirect scenario because it happens all at once, at scale, and a mistake affects the entire site rather than a single page. It needs a full URL-by-URL mapping, not a single blanket redirect from the old homepage to the new one.

Redirect types explained: 301, 302, 307, 308, 410, and 451

HTTP status codes tell browsers and search engines what happened to a URL and how to treat it going forward. Using the wrong one does not just look technically sloppy, it changes how search engines index the page and whether they carry the old URL's signals to the new one.

The distinction that matters most for SEO is 301 versus 302. A 301 tells search engines the move is permanent, so they update their index to treat the new URL as the canonical one and pass the old URL's ranking signals forward. A 302 tells search engines the move is temporary, so they keep the original URL indexed and treat the destination as a short-term detour. If you use a 302 for a change that is actually permanent, search engines may keep crawling and ranking the old URL indefinitely, which defeats the point of redirecting in the first place. Default to 301 for anything you expect to stay changed, and reserve 302 or 307 for genuinely temporary situations, like a page under maintenance or a redirect that only applies during a promotion.

410 deserves more use than it typically gets. When you remove content with no replacement, a 404 leaves search engines to figure out on their own, over time, whether the page is really gone or just temporarily broken. A 410 states it outright, which tends to get the URL dropped from the index faster and stops it from showing up in crawl reports as an error that needs investigating.

How to set up a redirect in WordPress, step by step

WordPress does not include redirect management in core, so you need either a plugin or server-level rules. For most sites, a plugin is the more maintainable choice because it gives you a searchable list of active redirects, hit counts so you can see which ones are actually being used, and a way to edit or remove them without touching server files.

1. 1Identify the exact old URL, including trailing slashes and query parameters, since a redirect rule usually needs to match precisely.
2. 2Identify the correct destination URL, the most relevant live page for that content, not just the homepage.
3. 3Choose the right status code for the situation, 301 for permanent moves, 302 or 307 for temporary ones, using the table above.
4. 4Create the redirect rule in your redirect manager, entering the source path, destination path, and status code.
5. 5Test the redirect in an incognito browser window or with a header-checking tool to confirm it returns the status code you intended, not a soft redirect that loads content without changing the HTTP response.
6. 6Update any internal links on your site that still point to the old URL, since a redirect fixes the destination but not the extra hop.

Rankwyn's redirect manager supports all six status codes covered above and shows hit counts on every rule, so you can see at a glance which redirects are still being hit by real traffic and which ones have gone quiet and can be cleaned up. It also lets you create a redirect directly from a logged 404, which is the fastest way to close a gap the moment you spot it rather than tracking the URL down separately.

Monitoring 404s to catch the redirects you missed

No matter how careful you are during a migration or content cleanup, some URLs slip through. Someone finds an old link in a years-old social post, a partner site never updated a backlink, or a page you did not realize existed gets deleted along with its parent category. A 404 monitor is how you catch these after the fact instead of relying on catching every case up front.

A 404 monitor logs every request that hits a broken URL on your site, along with how often it happens and, where available, where the traffic is coming from. The pattern to look for is repetition: a single stray 404 might be a typo or a bot probing for vulnerabilities, but a URL that keeps showing up in the log, especially one with an obvious referring source, is worth redirecting. Rankwyn's site maintenance tools log 404s automatically and let you turn any of them into a redirect in one click, which keeps this from turning into a recurring manual audit. This pairs directly with catching broken links elsewhere on your site, since an outdated internal link and an unmonitored 404 are usually two symptoms of the same underlying gap.

Mistakes that hurt SEO

Redirects are simple in concept but easy to implement in ways that undo their own purpose. Three mistakes account for most of the damage.

Redirect chains

A redirect chain happens when URL A redirects to URL B, which itself redirects to URL C. This tends to accumulate over time as a site goes through multiple rounds of restructuring without anyone cleaning up the older rules. Each hop in the chain adds latency, and if the chain gets long enough, some crawlers stop following it before reaching the final destination, which means the content never gets credited at all. When you create a new redirect, check whether the destination URL is itself a redirect, and if it is, point your new rule directly at the final URL instead of adding another link to the chain.

Redirecting everything to the homepage

When a page is deleted and nobody wants to spend time finding the right replacement, the homepage becomes the default dumping ground for the redirect. This is a poor user experience, since a visitor looking for specific content lands somewhere unrelated, and it is a weak SEO signal, since search engines treat a mass pattern of unrelated pages redirecting to one destination as a sign the redirects are not meaningful. Take the extra minute to find the most relevant live page, a parent category, a related post, or a close substitute, and redirect there instead. If nothing relevant exists, a 410 is usually the more honest choice than forcing an irrelevant redirect.

Forgetting that internal links still point to the old URL

A redirect fixes what happens when someone requests the old URL, but it does not fix the fact that your own site may still be linking to that old URL from menus, related-post modules, or older articles. Every one of those links now sends a visitor through an unnecessary redirect hop, and at scale, that adds up to slower page loads and diluted internal link equity flowing through redirect chains instead of directly. After setting up a redirect, search your site for internal links pointing at the old URL and update them to point directly at the new one. This is the same housekeeping habit covered in why Google might not be indexing your WordPress site, where a buildup of small technical gaps, not one big mistake, is usually the real cause.

If you are managing this manually across a growing site, it gets harder to keep track of which redirects are load-bearing and which ones are stale. Rankwyn bundles the redirect manager, 404 monitor, and broken link checker together specifically because they solve the same underlying problem: catching the small technical gaps that quietly erode rankings before they compound. See pricing for what's included at each plan.