[00] Subset Redirects, Guide
What happens to your redirects when you cancel Yoast Premium
Where Yoast SEO Premium keeps your redirects, how to export them before the subscription ends, and how to move them into a free redirect plugin.
- Published
- Fix uses
- Subset Redirects (free)
- Reading time
- 4 min
What changes when Premium ends
The redirect manager is part of Yoast SEO Premium, not the free Yoast SEO plugin. Yoast’s page on expired subscriptions (opens in a new tab) says that “without renewal, your Premium features and updates will stop”, and it lists the redirect manager among the features a renewal keeps.
Yoast’s help centre doesn’t say exactly when redirects you already have stop being served. If you uninstall Premium and keep only the free plugin, the code that serves Yoast’s PHP redirects is gone. Every old URL you redirected then returns a 404 until something else handles it.
Cancelling doesn’t end things on the day you click. Yoast’s cancellation page (opens in a new tab) says the subscription stays active for the rest of the period you’ve paid for. Use that time to move the redirects.
Where Yoast keeps your redirects
Yoast SEO Premium stores redirects in the WordPress options table, not in a table of its own. Yoast’s developer docs name wpseo-premium-redirects-export-plain and wpseo-premium-redirects-export-regex as the options used to work out redirect destinations (opens in a new tab).
The Subset Redirects importer reads the full list from wpseo-premium-redirects-base, which holds each redirect’s source, target, type and format. Older versions of Yoast Premium used wpseo-premium-redirects, and the importer falls back to it when the newer option is empty.
The WordPress plugin handbook (opens in a new tab) tells developers to remove options when a plugin is uninstalled, not when it’s deactivated. Deleting Premium can run its uninstall routine, so import before you delete the plugin, and keep a database backup until you’ve checked the result.
If you used the web server redirect method
Yoast Premium can serve redirects from PHP (the default) or from the web server. On Apache, Yoast’s redirect manager page (opens in a new tab) says it updates your .htaccess file. Its httpd config help (opens in a new tab) describes the other setup, where it writes the rules to wp-content/uploads/wpseo-redirects/.redirects and your server config includes that file.
Rules in those files are read by the server, not by WordPress. After you move to another plugin, look for Yoast’s rules in .htaccess or the include file and decide whether to remove them, so one place manages each redirect.
Export a copy while Premium is active
Yoast Premium can export your redirects to a CSV file. Yoast’s import and export help (opens in a new tab) puts it under Yoast SEO → Tools → Import and Export, and the feature needs Premium.
Download the CSV before your subscription ends. It’s a plain record of every redirect, and you can open it in a spreadsheet to check the import later. Subset Redirects doesn’t need it, because its importer reads Yoast’s data from the database.
Move them into Subset Redirects
Subset Redirects is free, and importing from Yoast SEO Premium is part of the free plugin. Yoast Premium doesn’t need to be active for the import, as long as its data is still in the database.
- Install and activate Subset Redirects.
- Go to Subset → Redirects → Import & Export.
- Under Import from another plugin, click Yoast SEO Premium. The link shows how many redirects it found.
- Read the preview, then click Import.
Nothing is saved until you click Import. A redirect whose source already exists in Subset Redirects is skipped, so running the import twice is safe.
With WP-CLI, do a dry run first, then the import:
wp subset redirector redirect import-from yoast --dry-run
wp subset redirector redirect import-from yoast
The dry run prints how many redirects it would add, skip or reject, with a warning line for each one it can’t bring over.
What the importer changes
Subset Redirects offers 301, 302 and 410. The importer maps Yoast’s types like this:
| Yoast type | Imported as |
|---|---|
| 301 | 301 |
| 302 | 302 |
| 307 | 302 |
| 308 | 301 |
| 410 | 410 |
| Any other | Not imported |
A 307 or 308 keeps the request method, which matters for forms and APIs but not for page visits. Status codes explains the difference.
Regular expression redirects aren’t imported. The preview lists each one with the reason, so copy those sources out before you finish. Pro adds wildcard and regular expression redirects if you need to recreate them.
Yoast ignores the query string when it matches a plain redirect, so imported redirects are set to Ignore query string. A request for /old-page?ref=mail still redirects.
Yoast’s developer docs say Premium creates a redirect automatically (opens in a new tab) when a URL changes. Subset Redirects adds one when a post’s, page’s or term’s slug changes, and it’s on by default.
Test the redirects after the switch
Test the busiest old URLs first. Enter a path in the Test a URL box on the Redirects tab and click Test to see which redirect matches and where it goes. From WP-CLI:
wp subset redirector redirect test /old-page
To check what a browser receives, request the old URL without following the redirect:
curl -sS -o /dev/null -w '%{http_code} %{redirect_url}\n' https://example.com/old-page
You should see the status code and the new address. If you still get the old result, a page cache or CDN may be serving a stored copy, and your browser remembers 301s, so test in a private window.
Leave the 404 Log running for a few weeks after the switch. Any URL you missed shows up there with a hit count, and you can add a redirect for it from the log. Getting started covers the log and the rest of the plugin.