The redirect manager WordPress deserved from the start.
Redirecting handles 301s, 302s, and everything in between — full regex support, 404 tracking, and a request-interception architecture built for speed. It does what every redirect plugin does, faster, with cleaner code and a data model designed to grow.
| Source | Target | Type | Hits |
|---|---|---|---|
| /old-pricing | /pricing | 301 | 2.4K |
| /blog/(.*)regex | /articles/$1 | 301 | 18K |
| /shop/* | /store | 302 | 964 |
| /promo-2023 | 410 Gone | 410 | 311 |
The popular alternatives were built for an older web.
They were written for an older PHP and carry that weight. Redirecting is built for PHP 8, designed around a modern WordPress stack, and assumes your redirect data belongs somewhere more useful than a local database table.
JSON columns instead of serialized strings — queryable, portable, and honest about its data.Everything a redirect plugin should do.
Exact matches and full PCRE regex. 404s as events. Analytics, syncing, and alerting wired in from day one — not bolted on later.
Redirect management
Create and manage redirects without touching server config. Exact URL matching and full PCRE regex with capture-group substitution in target URLs.
404 tracking
Every 404 is logged as an event. View, filter, and bulk-resolve them straight from the admin interface — no guessing what's broken.
Automated 404 fixing
Redirecting analyzes 404 patterns and suggests — or automatically creates — redirect rules. No manual triage queue to work through.
Analytics
Hit counts, last-access timestamps, and traffic trends per redirect. Designed to sync outbound to your analytics platform of choice.
Log syncing
Redirect and 404 events are queued for external sync. Push to PostHog, a time-series store, a webhook endpoint, or anything that accepts JSON.
Alerting
Define webhook endpoints; Redirecting emits the events and you wire up the rest. Works with Slack, PagerDuty, n8n, or any HTTP target.
Built for engineers who read the source.
A modern stack, a sane schema, and a documented REST API. Here's exactly what's under the hood.
Redirecting hooks at plugins_loaded — earlier than the template_redirect
hook where most redirect plugins fire. WordPress is initialized, but the full query and theme
setup haven't run yet. It's the safest early hook that still works reliably across hosting environments.
Roadmap A must-use plugin path is planned for installations that need to intercept before any regular plugin code runs.
Four tables. No serialized PHP.
Source URLs stored as VARCHAR(2048); action configuration as native JSON columns (MySQL 5.7+ / MariaDB 10.2+). Every log row carries a synced_at column and joins a sync queue from day one.
Match on more than the URL.
Redirect or refuse.
Every admin action is an endpoint.
All admin functionality is exposed under /wp-json/redirecting/v1/. The React admin interface is its only consumer; every endpoint requires the manage_options capability and WordPress nonce authentication.
A real app, not a settings page.
Server state via TanStack Query, validation via Zod, bundled with Vite.
- Composer-managed autoloading
- No legacy compatibility shims
- Typed properties & enums throughout
Free and open source.
Grab it from the WordPress.org directory, or pull the ZIP from GitHub. No license keys, no tiers, no upsell.
WordPress.org
The easiest path. Install and auto-update directly from your WordPress admin, or download the packaged release.
Download from WordPress.orgGitHub
Read the source, file issues, send PRs, or pull the latest ZIP from the release page. Built in the open.
Download ZIP from GitHub- Upload the
redirectingdirectory to/wp-content/plugins/ - Activate it via the WordPress plugin screen
- Navigate to
Tools › Redirecting
Or install directly from the WordPress admin plugin search.