How to Set Up a 301 Redirect in WordPress (3 Easy Methods + Best Practices)

You change a URL slug, clean up categories, or delete an old post, then a week later you notice traffic dipped. Or you spot a bunch of 404 error messages and think, “Wait, where are people even coming from?”

That’s where a 301 redirect helps. In plain terms, it sends visitors and search engines from an old page to a new page, automatically. No dead ends, no “Page Not Found,” no wasted backlinks.

Beginners run into this a lot: moving from HTTP to HTTPS (which requires an SSL certificate), switching to a new domain, retiring an old giveaway post, or just fixing messy permalink structure. This guide walks you through a simple, step-by-step way to set up a 301 redirect in WordPress, plus the best practices that keep your site tidy and your SEO rankings from sliding.

Before you redirect, make sure a 301 is the right choice

A redirect sounds like a quick fix, and it can be, but sloppy redirects create long-term headaches. The big risk is turning your site into a maze: page A goes to page B, which goes to page C, and nobody remembers why. Google still follows it, people still land somewhere, but it’s slower, harder to crawl, and harder to maintain.

So pause for a minute and decide what you’re actually trying to do.

If you’re replacing one page with another page that covers the same topic, a 301 is usually the right move. It tells search engines, “This content moved for good. Update your records.” That’s exactly what you want when you rename a blog post URL, merge two posts, change categories that affect the URL, or move to a new domain name and want old links to keep working.

If the old page has no real replacement, don’t force it. Redirecting everything to the homepage is tempting, but it’s often a bad match. Imagine clicking a link for “sourdough starter troubleshooting” and landing on a homepage. It ruins user experience because it is. Search engines read that mismatch too.

Also, try not to use redirects as a bandage for internal links you control. If your menu still points to the old URL, fix the menu. A redirect should help outside traffic and old bookmarks by preventing broken links, not cover up site housekeeping forever.

301 vs 302 vs 410, what they mean in real life

These HTTP status codes sound nerdy, but the meaning is simple:

• 301 (permanent): The page moved for good. Use this permanent redirect when a new page replaces the old one long term, helping preserve link equity.
  Example: you change /best-coffee-grinders/ to /best-coffee-grinders-for-beginners/.
• 302 (temporary): The move is short-term. Use a 302 redirect when you plan to bring the old URL back.
  Example: you run a seasonal promo page and send it to a “sale ended” page for a week, then restore it.
• 410 (gone on purpose): The content is removed and you’re not replacing it. This can be cleaner than redirecting to something unrelated.
  Example: an old giveaway post is done, and there’s no meaningful “new” page to send people to.

Rule of thumb: if the new page replaces the old one long term, use a 301. If you’re unsure, decide based on intent, not convenience.

A quick redirect planning checklist (so you do it once)

Before you create anything, do a fast check. It saves you from messy chains later.

• Confirm the old URL and how it’s written (with or without a trailing slash).
• Pick the best new match, not just “some page.” Closest topic wins.
• Don’t dump everything to the homepage unless there’s truly no better destination.
• Update internal links when you can (menus, buttons, in-post links). Redirects aren’t a substitute.
• Watch for redirect chains (old to older to new). Aim for one hop.
• Keep a simple redirect log in a note or spreadsheet, old URL, new URL, date, and why.

That’s it. Small prep, fewer regrets.

How to set up a 301 redirect in WordPress, three beginner-friendly methods

Quick safety note before you touch anything: if you can, take a backup (or at least a restore point with your host). Redirects are usually safe, but one wrong setting can send people to the wrong place fast.

Also, your hosting setup matters. Plugin redirects are easiest for most beginners. Server-level redirects (like .htaccess) can be faster and better for bulk changes, but they’re less forgiving. Pick the method that matches your comfort level.

Method 1, use an SEO plugin you may already have (Yoast, Rank Math, or AIOSEO)

If you already use an SEO plugin, check if it includes a redirect manager. Many do, but some lock redirects behind a paid plan. Don’t fight it. If the feature is locked, skip to the Redirection plugin method below.

I recommend using RankMath. They have a built in redirect manager.

The general steps are similar across SEO plugins:

1. In WordPress, open your SEO plugin settings and find the Redirects or Redirect Manager area.
2. Choose 301 as the redirect type.
3. Enter the old URL (often just the path, like /old-post/).
4. Enter the new URL (path or full URL, depending on the tool).
5. Save, then test the old link in a private browser window.

SEO plugin redirect tools are nice because they’re close to where you already work, and some can suggest redirects when you change a slug. Still, don’t assume it’s correct. Always test.

Method 2, use the free Redirection plugin (most common for beginners)

For a lot of WordPress beginners, the free Redirection plugin is the simplest route. It’s focused, it’s widely used, and it doesn’t try to do ten other jobs.

Here’s the basic flow:

1. Install and activate Redirection (Plugins, Add New).
2. Run the setup wizard (you can accept the defaults).
3. Go to Tools, Redirection, then click Add New.
4. Set Source URL (the old path) and Target URL (the new path or full URL).
5. Make sure it’s a 301 (permanent), then save.

About full URLs vs paths: in most cases, you can use paths. Example: source /old-post/ and target /new-post/. That’s cleaner, and it still works if your domain changes later. Use a full URL when you’re redirecting to a different domain.

The Redirection plugin can also track 404 errors. Helpful, but don’t treat it like whack-a-mole. You’ll see weird URLs from bots (random strings, old PHP files, spammy paths). Don’t redirect every one of those. Redirect real, human URLs that used to exist on your site.

Method 3, add a 301 in .htaccess (only if you are comfortable)

This method is mostly for Apache servers, and it’s handy when you have lots of redirects or you’re doing a domain move. It can also be faster than plugin-based redirects (as a server-side redirect) because it runs at the server level. Unlike a PHP redirect, which is less efficient for WordPress, this handles traffic before it hits your site’s code.

Be careful though. A small typo can take your site down until it’s fixed. For complex site migrations, .htaccess supports advanced options like wildcard redirects and handling query strings.

High-level steps:

1. Make a backup of your current .htaccess file.
2. Open your site files using your host’s File Manager or FTP.
3. Edit .htaccess (usually in the root directory, the same folder as wp-config.php).
4. Add a redirect rule, save, then test.

A simple example in plain text looks like this:
Redirect 301 /old-post/ https://yourdomain.com/new-post/

If this feels stressful, don’t push through it. Use a plugin, or ask hosting support to add the rule for you.

Best practices to protect SEO and avoid redirect problems

Redirects aren’t “set it and forget it,” at least not at first. Especially with a 301 redirect WordPress setup, you want to confirm they work, then clean up what you control so your site isn’t leaning on redirects forever.

Test every redirect and clean up what you can

After you add a 301 redirect in WordPress, test it right away:

Open an incognito or private window, paste the old URL, and see where you land. You’re checking two things: it goes to the right page, and it doesn’t bounce through extra hops.

If you want extra confirmation, you can use a redirect checker tool, but you don’t have to. For most beginners, “old link lands on the right new page” is the main win.

Then do the cleanup: update internal links, update menus, update buttons, and if you embed URLs in social profiles or email templates, fix those too. Your XML sitemap is usually handled by your SEO plugin, and it should start listing the new URL once WordPress knows about it. Still, it’s worth checking after big changes. To monitor and find missing pages after the setup, review your 404 error log.

Avoid common mistakes like chains, loops, and homepage dumping

Here’s the plain-English version:

• A redirect chain is A to B to C. It works, but it’s slower and messier.
• A redirect loop is A to B to A. That can break the visit completely.

Both confuse crawlers and waste crawl time. The fix is simple: point the old URL straight to the final destination, one step.

Also, avoid redirecting unrelated pages to the homepage. If the old page was about one topic, send it to the closest match. If there is no match, a 410 or a clean 404 can be better than faking relevance.

Finally, don’t remove redirects too soon. Keep them live for at least 6 to 12 months, and longer for URLs that had backlinks or steady traffic.

Key Takeaway

A clean 301 redirect WordPress setup is mostly judgment, not tech. First, confirm a 301 is the right call (permanent replacement). Next, pick the best destination page so the redirect makes sense to humans and search engines. Then set it up with an SEO plugin, the Redirection plugin, or .htaccess if you’re comfortable. After that, test, and update internal links so your site points to the new URL directly.

If you made a lot of URL changes, check Google Search Console for 404s over the next couple of weeks, and fix the ones tied to real pages. That’s how you protect your SEO rankings and keep traffic from leaking out through little cracks.