Redirection

Redirection is a free WordPress redirect manager focused on URL migrations, 404 monitoring, pattern matching, and bulk redirect administration. It is useful when you want a dedicated redirect tool instead of paying for a larger SEO suite just to manage moved, deleted, or renamed URLs.

What Redirection is designed to manage

The plugin handles common URL changes without requiring manual edits to Apache or Nginx configuration. You can create permanent and temporary redirects, return error responses for removed content, group redirects, and monitor which rules are actually being used.

That makes it useful during permalink changes, content consolidation, site redesigns, ecommerce catalog cleanup, domain moves, and long-term SEO maintenance. The interface stays inside WordPress, so editors and SEO teams do not need direct server access for normal redirect work.

Matching rules, regex, and query parameters

Simple redirects can match one source path exactly. More complex rules can use regular expressions to cover groups of URLs. The plugin also supports options for ignoring case or trailing slashes and gives you control over how query parameters are matched, ignored, or passed to the destination.

Advanced matching can go beyond the URL itself. Rules can account for login status, user role or capability, referrer, user agent, IP address, 404 status, cookies, server name, HTTP headers, browser language, or custom WordPress filters. That is useful for specialized migration or routing logic, but it also increases the chance of creating rules that are hard to troubleshoot.

404 monitoring and redirect logs

Redirection can log 404 requests so you can see which missing URLs visitors and crawlers are actually hitting. That is more useful than creating redirects blindly because it helps separate real broken inbound traffic from random bot requests or typo URLs that do not need a permanent rule.

Redirect logs also provide feedback on rule usage. On large or high-traffic sites, logging should be configured carefully because storing every hit can add database volume. The plugin includes controls around logging and cleanup, and you can disable logging entirely if you only need the redirect engine.

Import, export, and migration workflows

Redirection can import redirect data from files, pasted text, WordPress old slugs, and several other redirect or SEO plugins. Current importers include sources such as Simple 301 Redirects, Safe Redirect Manager, Rank Math, Pretty Links, SEOPress, and Slim SEO when those data sources are present.

Export options support moving rules out of the plugin and can generate data for Apache, Nginx, and other supported formats. The 2026 releases expanded import/export with previewing, duplicate handling, settings export, copy-and-paste workflows, and support for _redirects files.

Redirect actions and status codes

For normal URL redirects, the plugin supports standard HTTP redirect codes including 301, 302, 303, 304, 307, and 308. It can also return error responses such as 404, 410, or 451 when content should be marked unavailable rather than sent somewhere else.

Other actions include pass-through behavior and random-post redirects. These advanced options are useful in edge cases, but most SEO migrations should keep rules simple and intentional so future maintenance remains understandable.

Pricing and operating model

Pricing checked: September 26, 2026. Redirection is free. The project does not sell a paid support service or Pro tier. Support is primarily self-service through its documentation and public support channels.

The free model is useful when redirect management is the only requirement. If you already need a paid SEO suite for schema, content analysis, rank tracking, or other features, a built-in redirect manager may reduce plugin count even if the redirect feature itself is not free.

Who Redirection fits

I see Redirection fitting content-heavy sites, ecommerce stores, publishers, agencies, and SEO teams that need a dedicated redirect system with enough depth for large migrations. It is also useful when the people managing redirects should not edit server configuration directly.

For very high-traffic sites, edge or server-level redirects can be more efficient because they execute before WordPress. Redirection can export rules for server use, so a practical workflow is to manage and test rules in WordPress, then move stable large-scale rules to the infrastructure layer when needed.

Trade-offs to consider

Because Redirection runs inside WordPress, requests need to reach WordPress before the plugin can act. Existing files, server rules, caching layers, or another redirect agent can take priority and make a correct-looking rule appear broken.

Advanced regex and conditional matching are also easy to misuse. Keep rules as simple as the migration allows, document groups, and test source and destination URLs before applying broad patterns to a production site.

A practical redirect QA checklist

For a migration, test rules in layers. Start with exact source URLs before introducing regex. Check the response code with an HTTP header tool, confirm the final canonical URL, and verify that important query parameters are either preserved or intentionally discarded. Then test representative URLs from each redirect group rather than assuming one successful rule proves the whole pattern.

After launch, use the redirect and 404 logs to identify missed legacy URLs, but avoid turning every random 404 into a redirect. Redirect pages only when there is a clear replacement or equivalent destination. Removed content with no useful substitute may be better served with a 404 or 410 response than a blanket redirect to the homepage.

Frequently Asked Questions