Your redirects shouldn’t have to wait for WordPress
Auto Redirects for Kinsta turns every slug change in WordPress into a real 301 in your Kinsta server configuration. Free, and it stays out of your way.
Most redirect plugins work the same way. WordPress boots, PHP runs, the database gets queried, a rule matches, and only then does the visitor get sent somewhere else. All that work happens to serve a page you didn’t want to serve in the first place.
Kinsta can handle it in one step, at the server, before a single line of PHP runs. This plugin makes that happen automatically.
Download the plugin (free)The problem
What a WordPress redirect actually costs
Rename a page from /services/ to /what-we-do/ and WordPress will handle it. Eventually. Here’s what happens behind the scenes:
- Someone requests the old URL.
- WordPress boots completely. Core, plugins, theme, database connection.
- Nothing matches, so WordPress starts preparing a 404.
- Only then does
wp_old_slug_redirect()fire, run an extra query against the postmeta table, and issue the 301. - The browser starts over with a second request.
You paid for a full page render just to throw it away. Redirect plugins step in a little earlier in that cycle, but the principle holds. PHP runs, the database gets queried, and rules get matched on every single request, including the ones that were never going to redirect anyway.
The same request on Kinsta
- Someone requests the old URL.
- Nginx matches the rule and returns a 301.
No PHP. No database. No 404 in between.
One thing worth being precise about, because it’s easy to get wrong: these rules live in your Kinsta server configuration, not in Cloudflare. The request still travels through Kinsta’s network to reach the server. What it skips is WordPress itself, which is where the cost was.
Why this matters
Nothing has to boot. A server-level redirect skips the entire WordPress startup. No plugins loading, no theme, no database connection, just a response.
Zero weight on the pages that don’t redirect. Database-driven redirect plugins check their rule table on every request your site receives. Server-level rules never reach PHP at all, so they cost your site nothing the rest of the time.
Cleaner crawling. Googlebot follows redirects. The faster they resolve, the more of your actual content gets crawled in the same window. Slow, PHP-rendered redirects are a quiet tax on your indexing.
Nothing slips through. A 301 passes ranking signals. A redirect you forgot to make passes nothing. The plugin catches slug changes the moment they happen, including from Quick Edit, which is exactly where they tend to go unnoticed.
PHP workers stay free for real work. After a migration or a restructure, redirect traffic can eat a real share of your workers. Moving that to the server frees them up for actual page requests.
How it works
- Connect once. Paste your Kinsta API key and Environment ID. Not sure which UUID you need? Paste your full MyKinsta site URL and the plugin pulls it out for you. Test the connection with one click.
- Work the way you already do. Edit a page, change a slug, hit update. Quick Edit counts too. The plugin spots the change and creates the matching 301 in Kinsta.
- Manage it all from WordPress. Every Kinsta redirect rule you have, including the ones you added by hand in MyKinsta, shows up in a native WordPress list table. Search, sort, edit, bulk delete, export.
Auto Redirects for Kinsta – Features
Automatic redirect creation Every published slug change becomes a server-level 301. No checklist to keep, no pages forgotten.
Full management inside WordPress Add, edit, search, sort, paginate and bulk delete your Kinsta rules without leaving wp-admin.
Bring your old redirects along The plugin finds the legacy _wp_old_slug entries your site has collected over the years and converts them to Kinsta rules, one at a time or in bulk. Your existing redirects get faster without you rebuilding them by hand.
Built like a native WordPress screen List tables, screen options, bulk actions, pagination. The same components core uses, so there’s nothing new to learn.
CSV export Take your full redirect map with you, to a spreadsheet, a client report or an audit.
Optional fallback Want to keep WordPress’ own slug redirects running as a safety net? Switch it on. It’s off by default, since skipping that path is the whole point.
Debug logging when you need it Detailed API logging you can turn on to troubleshoot and turn off again in one click.
Who it’s for
- WordPress sites on Kinsta: agencies, publishers, shops
- Anyone in the middle of a migration or a restructure, where redirect volume adds up fast
- Teams where editors rename pages and nobody tells the developer
- Sites where Core Web Vitals sit on someone’s KPI list
Good to know
We’d rather tell you now than have you find out after installing.
Kinsta only. This plugin talks to the Kinsta API. On other hosting there’s nothing for it to talk to.
You need an API key. You’ll find it in MyKinsta under Company Settings, API Keys. Read access isn’t enough, since the plugin writes redirect rules.
The rules live in Kinsta, not in your database. That’s the point, but it also means deleting a rule here deletes it there.
Query strings aren’t supported. Kinsta’s redirect rules can’t match on query parameters. They do get carried across to the destination, so /old-page/?utm_source=newsletter still arrives with its parameter intact. If you need a rule that matches on a parameter, Kinsta’s support team can add a custom rule for you.
These are origin rules, not edge rules. They run on your Kinsta server, not as Cloudflare Page Rules. The gain comes from skipping PHP and the database, and it doesn’t depend on your CDN setup.
FAQ
What does it cost? Nothing. It’s free and released under GPL v2 or later.
Where do I download it? Right here. [link] It’s also submitted to the WordPress.org plugin repository, so once it’s approved you’ll be able to install it straight from your WordPress admin. [link]
Does this replace my redirect plugin? For slug changes and straightforward 301s on Kinsta, yes, and it removes the per-request database lookup that comes with database-driven redirect plugins. If you’re running complex conditional rules, keep the specialist tool alongside it.
What happens to the redirects I already made in MyKinsta? They show up in the plugin’s list and you can manage them there. Nothing gets overwritten.
Will my existing WordPress redirects stop working? Not unless you say so. The WordPress Redirects tab shows every legacy entry and you decide which ones to convert. There’s also an optional fallback setting if you’d rather keep the native ones running.
Does it work with Quick Edit? Yes. Quick Edit is where slug changes usually slip past unnoticed, so it was built in from the start.
Does it slow down the admin? The plugin calls the Kinsta API when you save a slug change or open the redirect screens, never on front-end page loads. Your visitors don’t wait for an API call.
Who made this? Creative Passenger. We build and maintain WordPress sites on Kinsta ourselves, and this plugin exists because we got tired of managing redirects in two places.