Redirection
View on WordPress.orgScores higher than 99% of indexed plugins
About
Manage 301 redirects, track 404 errors, and improve your site. No knowledge of Apache or Nginx required.
Security History
What It Does
Redirection lets you create and manage 301, 302, and 307 redirects from a WordPress admin screen, with no need to edit .htaccess or nginx config files manually. It also logs 404 errors on your site so you can spot broken links and route them to working pages. Regex-based matching, logging, and conditional redirects give you a fair amount of control without leaving the dashboard.
Who It's For
Site owners running content-heavy WordPress sites who frequently rename URLs, migrate pages, or delete old posts and need to redirect traffic without touching server config files. It is also a solid fit for publishers who want to monitor 404s and clean them up as part of routine SEO maintenance.
Who Should Skip It
Anyone on a fully static site, a single-page landing page, or a headless WordPress setup that does not change URLs will not need this plugin and adds unnecessary database overhead. Developers who already manage redirects through nginx, Apache, or a CDN like Cloudflare will also get more value from configuring rules at the server or edge layer.
The Bottom Line
Redirection is the default choice for most WordPress users who want a GUI for redirects and 404 monitoring, and its install count plus recent update history back that up. Its main weakness is the mediocre support resolution rate, so if your site relies on complex redirect rules you should be comfortable troubleshooting on your own or via community forums. For typical content sites, this is a safe, well maintained pick scoring 88.92 out of 100.
Related Plugins
Pick this if you also need a full SEO suite including sitemaps, schema, and on-page optimization, and you only want one plugin doing the heavy lifting.
Pick this lighter alternative (300,000 installs) if you want simple redirect management without the 404 logging and regex depth of Redirection.
Pick this if you only need to redirect users after submitting a Contact Form 7 form, since general redirects are out of its scope.
Pick this if you want a similar feature set with a smaller install base, though you trade the maturity and community size of the original Redirection.
Pick this if you simply need to point individual pages or posts at a different URL without setting up broader site-wide redirect rules.