How to Set Up WordPress Redirects After Changing a URL

You renamed a guide from "/elden-ring-boss-tips" to "/elden-ring-boss-guide", and a week later Search Console shows a pile of 404 errors and the page has dropped from page one. The content did not get worse. The old address simply stopped pointing anywhere, so every link and every bit of ranking history went with it. Setting up WordPress redirects correctly is how you change a URL without paying that price.

This guide covers when you need a redirect, which type to use, three ways to add one on a WordPress fan site, and the mistakes that quietly undo the work.

When you need WordPress redirects

Any time a URL that already exists stops working, a redirect should replace it. On gaming community sites, the usual triggers are:

• Renaming a post slug to match a new game title or patch number.
• Changing the permalink structure, for example from "/2024/03/post-name" to "/post-name".
• Merging three thin patch note posts into one stronger guide.
• Moving a page into a new category when you restructure, which is worth planning with our guide on choosing between categories and tags for a gaming blog.
• Deleting an outdated tier list that still gets traffic from forum links.

WordPress does a little of this on its own. When you edit a slug on a published post, core stores the old slug and sends visitors to the new one. That helps, but it only covers post slugs, it is invisible in the dashboard, and it breaks if you later reuse the old slug. Do not rely on it for anything you care about.

301, 302 or 410 and which one to pick

The status code tells browsers and search engines what kind of move happened. Pick the wrong one and Google may keep the old URL indexed for months.

For 95 percent of fan site work, the answer is 301. A 410 is useful when you delete spam pages or leaked content and want them dropped from the index faster than a plain 404 would manage.

Three ways to add a redirect

Option 1: a redirect plugin

The free Redirection plugin is the easiest route for most admins. After activating it, go to Tools, then Redirection, enter the old path in "Source URL" and the new path in "Target URL", and save. It defaults to a 301. Turn on "Monitor permalink changes" in the options and it will create a redirect automatically whenever you edit a slug. It also logs 404 hits, which shows you which broken URLs real visitors are hitting.

If you already run an SEO plugin such as Rank Math or Yoast Premium, check whether it has a redirect manager built in before adding another plugin. Two redirect tools on one site is a reliable way to create loops.

Option 2: the .htaccess file on Apache

On Apache hosting you can add a line above the WordPress block in .htaccess, in the form "Redirect 301 /old-slug/ /new-slug/". Server redirects run before WordPress loads, so they are slightly faster and keep working even if a plugin breaks. The downside is that one typo can take the whole site offline, so download a copy of the file first and keep a working backup. Our guide on backing up a WordPress site the right way covers what to save.

Option 3: Nginx or host level rules

Nginx ignores .htaccess entirely. On managed hosts that use Nginx, look for a "Redirects" panel in the hosting dashboard, or ask support to add the rule. Cloud setups with a CDN often have their own redirect rules too. Keep all your redirects in one place so you know where to look when something misbehaves.

The case against redirecting everything to the homepage

A popular shortcut, often recommended in plugin tutorials, is "redirect all 404 errors to the homepage". It sounds tidy. It is not.

Google treats a redirect from a specific guide to an unrelated homepage as a "soft 404", so you get none of the link value you hoped to keep. Visitors are confused too. Someone clicking a forum link for a specific boss strategy lands on your front page with no idea where the content went, and they leave. Mass homepage redirects also hide real problems, because your 404 log goes quiet even when links are broken.

The better approach is one to one: redirect each old URL to the single page that answers the same question. If nothing on the site matches, let it return a 404 or a 410 with a helpful page that offers search and popular guides. An honest 404 beats a misleading redirect.

Mistakes that break redirects

• Redirect chains. Page A goes to B, which goes to C. Each hop slows the page and some crawlers stop after five. When you redirect again, update the original rule to point straight to the final URL.
• Loops. A rule that sends a page to itself, often caused by a trailing slash mismatch, produces "too many redirects" errors. Test with and without the slash.
• Forgetting internal links. A redirect is a safety net, not a fix. Search your posts for the old URL and update the links directly.
• Caching old responses. Clear your caching plugin and CDN after adding rules, or you may test an old version and think it failed.
• Plugin clashes. If a redirect works one day and not the next, two tools may be fighting. Our walkthrough on finding a WordPress plugin conflict helps isolate the culprit.

To test, open a private browser window, visit the old URL and confirm you land on the new one. A free header checker will show the status code, and you want to see a single 301 followed by a 200.

Frequently asked questions

Do WordPress redirects hurt SEO?

A correct 301 to a closely matching page passes nearly all of the ranking signals to the new URL. What hurts SEO is redirecting to unrelated pages, building long chains or leaving old URLs broken. Expect rankings to settle within a few weeks after a clean move.

How long should I keep a 301 redirect?

Keep it for at least a year, and ideally forever if the old URL had backlinks. Forum posts and wiki links on gaming sites stay online for years. A single redirect rule costs almost nothing to keep.

Can I redirect a page without a plugin?

Yes. On Apache servers you can add a rule to the .htaccess file, and on Nginx hosts you can add a rule in the server config or the hosting dashboard. Always back up the file first, because a syntax error can make the whole site unreachable.