WordPress

Redirection Plugin Review: How to Fix 404 Errors Without Editing .htaccess

WordPress November 6, 2026 16 min read
Redirection Plugin Review: How to Fix 404 Errors Without Editing .htaccess

A visitor clicks a link to your site, and sees a page that says “Not found”.

It happens to every website. You change a post’s address, delete an old page, move to a new domain, or fix a typo in a title. Somewhere, a link still points to the old address, on another site, in a search result, or in an old email. Each of those visitors reaches a dead end, and search engines notice the broken pages too.

The standard fix is a redirect: a rule that sends the old address to the new one. For years, that meant editing the .htaccess file by hand, which is easy to get wrong. One wrong character can take your whole site down.

Advertisement

The Redirection plugin offers a safer way. You manage redirects from your WordPress dashboard, and the plugin also keeps a log of 404 errors, so that you can see which broken links really matter. In this review, we’ll explain how it works, how to set it up, and when it is not the best choice.

What Is a 404 Error, and Why Does It Matter?

A 404 error means that the server could not find the page that the visitor asked for. The address may be wrong, or the page may have moved or been deleted.

A few 404 errors are normal. They become a problem when:

  • Important pages that used to receive traffic now return a 404.
  • Other sites link to your old addresses, and those links stop working.
  • You change your permalink structure or move your site, and many addresses change at once.
  • Search engines keep trying to crawl addresses that no longer exist.
  • Visitors leave because they cannot find what they wanted.

A good 404 page helps, but a redirect that sends the visitor to the right new page is better.

What Is a Redirect?

A redirect tells browsers and search engines that a page has moved. The most common types are:

TypeNameUse it for
301Moved permanentlyA page that has a new address for good
302Found, a temporary moveA short-term change
307Temporary redirectA temporary move that keeps the request method
308Permanent redirectA permanent move that keeps the request method
410GoneA page that was removed on purpose
451Unavailable for legal reasonsRare legal cases

For most site owners, 301 is the one that matters. It tells search engines that the old address has been replaced by the new one.

What Is the Redirection Plugin?

Redirection is a free WordPress plugin for managing redirects and tracking 404 errors. It is listed on the Redirection page on WordPress.org. According to its documentation, it works from a WordPress admin screen, so you do not need to know server configuration.

Its main features are:

  • Creating and managing redirects from the dashboard.
  • Support for regular expressions, to redirect groups of addresses with one rule.
  • Several status codes, including 301, 302, 307, 308, and some error codes.
  • Conditional redirects, based on factors such as login status, browser, referrer, or IP address.
  • Logging of 404 errors, so that you can find broken links and fix them.
  • Optional logging of redirect activity, with hit counts.
  • Automatic redirects when a post or page address changes.
  • Import and export of redirects in several formats, and import from other redirect plugins.
  • Options to handle redirects through WordPress, Apache, or Nginx.

Redirection Plugin at a Glance

PointWhat to know
PriceFree
Main jobCreate redirects and log 404 errors
Editing .htaccess by handNot needed
Best forBlogs and small business sites that change addresses now and then
Learning curveLow for simple redirects, higher for regular expressions
Main riskRedirect loops and large logs if you do not set limits

How to Install and Set Up Redirection

  1. Take a full backup of your site.
  2. Go to Plugins, then Add New, and search for Redirection.
  3. Install and activate the plugin.
  4. Go to Tools, then Redirection, and run the setup.
  5. Choose whether to monitor changes to post addresses. If you turn this on, the plugin creates a redirect for you when you change a post’s address.
  6. Choose whether to keep logs of redirects and of 404 errors, and for how long.
  7. Let the plugin test its connection to your site.
  8. Open the Redirects tab, and add your first redirect.

Choose your log settings with care

Logs help, but they grow. On a busy site, a 404 log can fill the database with thousands of rows. Set a short log expiry, such as a few weeks, and turn off IP logging if you do not need it. This also helps with privacy.

How to Create a Redirect

  1. Go to Tools, then Redirection.
  2. Open the Redirects tab, and click Add New.
  3. In Source URL, enter the old address, such as /old-page/.
  4. In Target URL, enter the new address, such as /new-page/.
  5. Check the group and the status code. For a permanent move, use 301.
  6. Click Add Redirect.
  7. Test it by opening the old address in a private window.

Use relative paths for pages on your own site, and a full address for another site.

Tips for good redirects

  • Redirect to the most relevant page, not always the home page. A visitor who looks for a specific topic wants that topic.
  • Avoid chains, where A goes to B and B goes to C. Update the first rule to go straight to C.
  • Do not create loops, where A goes to B and B goes back to A.
  • Use 301 for permanent moves.
  • Keep a short note of why you added each redirect.

How to Fix 404 Errors With the 404 Log

This is the most useful part of the plugin for most sites.

  1. Go to Tools, then Redirection, and open the 404s tab.
  2. Look at the list. It shows the address, how often it was requested, and the last time.
  3. Sort by the number of hits. Fix the most requested addresses first.
  4. For each address, decide: does the page have a new home?
  5. If yes, click the address, and add a redirect to the new page.
  6. If the page is gone for good and has no replacement, leave it as a 404 or use a 410 status.
  7. Ignore addresses that look like bot probes, such as requests for files that never existed on your site.

Group similar errors

If many addresses share a pattern, such as an old category base, a regular expression can redirect them all at once. The plugin also offers a bulk option to redirect several errors together.

Redirect Methods: WordPress, Apache, and Nginx

By default, the plugin handles redirects inside WordPress. Each request goes through WordPress first, and then the plugin checks its rules. This is simple, and it needs no server changes.

The plugin also offers other options, according to its documentation.

MethodHow it worksGood forThings to know
WordPressThe plugin handles redirects in PHPMost small sitesSlightly slower than a server rule, since WordPress loads first
ApacheRedirects are saved to the .htaccess fileSites on Apache that want server-speed redirectsThe plugin writes to .htaccess, so check file permissions
NginxYou export rules to add to the server configurationSites on NginxYou must add the rules yourself or ask your host

For most small sites, the default WordPress method is fine. If you have thousands of redirects, or very high traffic, a server-level method is faster.

Common Uses

Changed post address

You changed a post’s slug from /old-title/ to /new-title/. Turn on the option to monitor address changes, or add a 301 redirect from the old address to the new one.

Deleted page

You removed an old service page. Redirect it to the closest current page, or to a page that lists your services.

New permalink structure

You switched from a date-based structure to a simple one. Use a regular expression to redirect all old posts at once, and test several examples before you save.

Moving to a new domain

Redirect each old address to the same path on the new domain. Also set up www and non-www rules, and keep the redirects for a long time.

HTTP to HTTPS

Most hosts handle this at the server level, so you may not need the plugin. If you do use it, test for loops.

Affiliate or short links

You can create short, branded links, such as /go/product, that redirect to a long address. Keep notes, and check them for broken targets from time to time.

Redirects and SEO

A 301 redirect passes most of the value of the old address to the new one, and it tells search engines to update their records. Good redirects help you keep traffic when you change addresses.

  • Redirect old addresses to the closest matching page.
  • Avoid redirecting many unrelated pages to the home page. Search engines may treat these as soft errors.
  • Update internal links to point straight to the new address, so that visitors do not need to pass through a redirect.
  • Keep important redirects for a long time, ideally for as long as the old address has links or traffic.
  • If you use an SEO plugin with its own redirect manager, do not run two redirect tools for the same addresses. Our comparison of Rank Math vs Yoast SEO explains which of them include a redirect manager in the free version.

Pros and Cons

Pros

  • Free, and made for this one job.
  • No .htaccess editing is needed.
  • A 404 log that shows which broken links matter.
  • Regular expressions and conditional rules for advanced cases.
  • Automatic redirects when you change a post address.
  • Import and export, and import from other redirect plugins.
  • Options for Apache and Nginx, if you want server-level speed.

Cons

  • The default method loads WordPress for each redirect, which is slower than a server rule.
  • Logs can grow large if you do not set limits.
  • Regular expressions are powerful and easy to get wrong.
  • Overlap with an SEO plugin’s redirect tool can cause conflicts.
  • You can create loops and chains by accident.

Common Mistakes With Redirects

  • Redirecting everything to the home page.
  • Creating a chain of several redirects.
  • Making a loop, so that the page never loads.
  • Using a temporary redirect for a permanent move.
  • Leaving 404 logging on without an expiry, and filling the database.
  • Using two redirect tools for the same address.
  • Not testing the redirect in a private window.
  • Forgetting to clear the cache after you add a redirect. A caching plugin may serve the old result.
  • Writing a regular expression that catches more than you meant.

If a redirect rule breaks your site, or locks you out of the dashboard, rename the plugin’s folder over FTP to turn it off, and log in again. Our guide on what to do when your WordPress website breaks after an update shows how to do this, and how to recover safely.

Troubleshooting Redirection

ProblemLikely causeWhat to try
Redirect does not workCache, or a wrong source addressClear caches, and check the source address exactly
Too many redirects errorA loopFind the rule that sends the page back, and remove it
Plugin says it cannot connect to the REST APIA security rule or a permalink problemSave permalinks, and check firewall rules
404 log is emptyLogging is off, or a plugin handles 404sTurn on logging, and test
Redirects stopped after an updateA plugin conflictTest with other plugins off. Our guide on how to find which plugin is breaking your site shows the method
Slow site with many redirectsThe WordPress method with thousands of rulesUse a server-level method

Regular Expressions Made Simple

Regular expressions, often called regex, let one rule match many addresses. They look strange at first, but a few patterns cover most needs.

You want toSource patternTargetResult
Redirect one folder to another, keeping the page name^/old-blog/(.*)$/blog/$1/old-blog/my-post/ goes to /blog/my-post/
Remove a date from old addresses^/[0-9]{4}/[0-9]{2}/(.*)$/$1/2022/05/my-post/ goes to /my-post/
Redirect a retired category to a new page^/category/old-topic/(.*)$/new-topic/All old topic addresses go to one page
Ignore a trailing slash^/page$/page/Both versions end up at the same address

Safe habits for regex

  • Turn on the regex option for that rule only.
  • Test with real addresses before you save. Try several, including odd ones.
  • Keep the pattern as narrow as you can. A pattern that matches too much can redirect pages that you did not mean to move.
  • Add the new rule near the end of the list, so that specific rules run first.
  • Write a note that explains what the rule does, since you will forget in a year.

If you are not sure, use simple one-to-one redirects. They take longer to set up for many pages, but they are easy to check.

Handling Query Strings and Trailing Slashes

Small differences in an address can change whether a redirect matches.

  • Some addresses carry query strings, such as ?utm_source=newsletter. The plugin lets you choose whether to ignore the query, match it exactly, or pass it to the target. For tracking links, passing the query to the target keeps your campaign data.
  • Addresses with and without a trailing slash are different to a strict rule. Check how your site normally behaves, and make your rules match.
  • Upper and lower case can matter on some servers. The plugin has an option to ignore case.

Test each type of address, so that you do not leave a gap.

Advertisement

Using Groups to Stay Organized

Redirects can be sorted into groups. A group is a folder for related rules, such as “Old blog”, “Site migration”, or “Affiliate links”.

  • Use one group for each project or purpose.
  • Turn a whole group on or off when you need to test.
  • Export one group at a time, if you want to move rules to another site.
  • Give groups clear names, so that a new person can read your list.

A tidy list matters more as the number of rules grows. A list of two hundred unnamed rules is hard to maintain.

A Site Migration Checklist

A move to a new domain or a new structure is where redirects matter most.

  1. Crawl your old site, or export your list of pages from your sitemap and your search console reports.
  2. List the old address and the new address for each page.
  3. Import the list into the plugin as a CSV file, or add the rules with regex where a pattern fits.
  4. Set up www and non-www and HTTP to HTTPS rules at the server or in the plugin.
  5. Test a sample of old addresses, including your top pages by traffic.
  6. Check that internal links on the new site point to new addresses, not through redirects.
  7. Update your sitemap, and submit it in the search console of the new domain.
  8. Tell the search console about the change of address, if it applies.
  9. Watch the 404 log for several weeks, and fix any missing rules.
  10. Keep the redirects in place for at least a year, and longer for pages with links from other sites.

A good migration keeps most of your traffic. A careless one can lose it for months.

Performance Notes

Redirects add a small step to each request. A single redirect is fast, but there are some things to avoid.

  • Long chains add delay at each step. Point the first rule straight to the final address.
  • Thousands of rules in the WordPress method mean more checks on each redirected request. A server method scales better.
  • Logging every redirect adds database writes. Turn off redirect logging if you do not use it.
  • Cached pages are not affected, since redirects happen before the page is built.

If your site is slow, redirects are rarely the cause, but if you suspect a plugin, a speed audit of images, hosting, caching, and plugins is the better place to start. For permalink and routing errors in general, the official WordPress common errors page explains how to reset your .htaccess file and permalinks.

Privacy and Log Management

Logs can hold visitor data, such as IP addresses and browser details.

  • Turn off IP logging, or reduce it, if you do not need it.
  • Set a short retention period for both logs.
  • Do not share exports of logs without removing personal data.
  • If your visitors are in places with strict privacy rules, check what you must say in your privacy policy.
  • Delete old logs after you finish a migration or a clean-up.

Backup and Export Habits

Redirects are valuable data. A large list can take weeks to build.

  • Export your redirects as a file, from time to time, and store it with your other backups.
  • Take a full site backup before you import a big list or run a regex rule.
  • When you change plugins or move a site, export first, and import after.
  • Keep a copy of your list in a spreadsheet, with a column for the reason and the date.

When Not to Use the Plugin

Redirection is not the right tool for every case.

  • If your host provides a redirect tool in its panel, and you only need a few rules, that may be enough.
  • If you need high-speed rules for huge lists, a server configuration or a CDN rule set is better.
  • If your SEO plugin already handles redirects, avoid adding another tool, unless you need the 404 log or regex.
  • If a redirect problem is caused by a server rule, such as a forced HTTPS rule, fix it at the server.

Choose one main place to manage redirects, and write down where it is. Many redirect problems come from rules scattered across the host, the SEO plugin, a redirect plugin, and a CDN.

Quick Setup Checklist

  1. Back up your site.
  2. Install Redirection, and set log retention to a short period.
  3. Turn on monitoring of address changes, if you want automatic redirects.
  4. Open the 404 log after a week, and sort by hits.
  5. Add 301 redirects for the top broken addresses.
  6. Test each one in a private window.
  7. Check for chains and loops.
  8. Export your redirects, and store the file.
  9. Review the log each month.

How Often Should You Check for 404 Errors?

A monthly check is enough for most sites. Open the 404 log, sort by hits, and fix the top few addresses. After a redesign, a migration, or a change of permalink structure, check every few days for the first two weeks, since that is when new broken links appear.

Also check your search console reports. They show broken addresses that search engines found, including some that the plugin may not have seen, because the plugin only logs requests that reach your site.

Treat the 404 log as a to-do list. A few minutes each month keeps your site tidy, protects your traffic, and stops small problems from piling up.

Frequently Asked Questions (FAQs)

Does the Redirection plugin edit my .htaccess file?

Not by default. It handles redirects inside WordPress. If you choose the Apache method, it can save redirects to .htaccess.

Is the Redirection plugin free?

Yes, it is a free plugin.

What is the difference between 301 and 302?

A 301 is a permanent move, and a 302 is a temporary move. Use 301 when the old address is gone for good.

Will redirects hurt my SEO?

Good redirects help. Bad ones, such as loops, chains, or sending everything to the home page, can hurt.

How do I find broken links on my site?

Use the 404 log in the plugin, and also check your search console reports for crawl errors.

Can I redirect many pages at once?

Yes. Use a regular expression, or the bulk option in the 404 log. Test with a few examples first.

How many redirects can the plugin handle?

A few hundred are fine with the default method. For thousands, consider a server-level method.

Should I redirect all 404s to the home page?

No. Redirect each address to the most relevant page, and leave genuinely gone pages as 404 or 410.

Can someone fix my 404 errors for me?

Yes. If you prefer an experienced person to audit your broken links and set up redirects, you can get WordPress management help through this Fiverr gig.

Final Thoughts

The Redirection plugin gives you a safe, simple way to fix 404 errors and manage redirects without touching .htaccess. Its 404 log shows which broken links matter, and its redirect rules let you fix them in a minute.

Use it with care: send each old address to the most relevant page, avoid chains and loops, set a log expiry, and test each rule in a private window. For most small sites, the default method is fine. If your list of redirects grows very large, move to a server-level method, and keep a backup before every change.

Advertisement
Mindful reading

Better ideas, delivered thoughtfully.

Receive useful articles, thoughtful perspectives and practical knowledge from Mindful Tomorrow without unnecessary noise.

Scroll to Top