September 2, 2026 · 7 min read
Leaving Yoast Without Losing Your Titles
You spent years getting two thousand titles right, and one careless import can undo it before you've finished your coffee. We show you every value before it writes, so the switch costs you nothing you didn't choose to spend.
You didn't write two thousand title tags by hand so a plugin could overwrite them on install. Somewhere in that pile is an afternoon lost to a single character, the breadcrumb separator, checked against every template on the site until it finally stopped looking wrong. And somewhere in the redirect rules there's a 301 still doing quiet work, from a page you renamed back in 2019, still catching traffic from a link nobody controls anymore.
That's not a small inheritance to hand a new plugin, and the fear that comes with handing it over is the reasonable one, not the paranoid one. A tool built to win new business fast has every reason to make a switch feel instant, one click, welcome aboard, and instant is exactly where a title tag goes quietly missing. We'd be afraid too, in that position, so we built this the way we'd want it built if we were the ones switching: slow at the one moment that matters, and quiet everywhere else.
What You See Before Anything Writes
We import settings from five other SEO plugins, Yoast, Rank Math, SEOPress, AIOSEO and The SEO Framework,, and every one of those five importers shows you a preview before a single value lands in the database. Titles, descriptions, redirect rules, robots settings: the whole list shows up before you confirm it, in the same screen format every other fix in this plugin uses, because we didn't want an import to work any differently than everything else we ship. A plugin that changes titles without asking permission first is doing exactly what a plugin claiming to fix your SEO problems for you would do, and that isn't the plugin we set out to build.
You keep every title you wrote by previewing it before a byte writes, and you get any of it back by rolling it back after. We don't run anything on activation and we don't run anything on a schedule; the import runs when you click the button, on a screen built to be read before it's trusted.
The Rollback, If You Change Your Mind
Settings export keeps its own revisions, so a migration you regret a week later isn't a support ticket, it's a rollback. We built the same rule into every fix this plugin applies on its own, an llms.txt file, a meta description, a redirect rule, each stored with a way back, and we made reverting any one of them a single click.
The Page You Renamed
Rename a published page and we can record a visible, removable 301 from the old address, off by default, on the moment you want it. The redirect stays live for as long as you leave it, and it comes off the day you decide it's stopped earning its keep. We don't think a slug change should cost anyone traffic an address already earned, including the traffic still finding the page renamed back in 2019.
When Two Plugins Fight Over Your Head
Run two SEO plugins at once and they'll fight over the page's head output, meta tags, canonical links, JSON-LD, and the usual casualty is duplicated markup nobody asked for. So we made takeover a switch flipped on purpose, not something that happens the moment a second plugin activates. Until it's flipped, we'd rather stay silent on the front end than win that fight badly: with a competitor plugin already owning the head and takeover off, we print nothing at all, so exactly one plugin's tags stay live at a time, by choice, never by accident.
What Doesn't Come With You
An importer moves settings, not history. Redirect logs, 404 hits, an old plugin's own revision trail all stay with the tool that recorded them, because they were never ours to export. We can only read what the plugin you're leaving actually stored in a format we recognize: a heavily customized setup with hand-edited database rows outside that schema can fail to come across whole, which is exactly what the preview screen exists to catch before anything writes. That's not a hedge; it's a boundary worth stating in one sentence instead of finding out from a support ticket. We'd rather admit that limit here than let a preview screen discover it for the first time on a live site.
Yoast, Named Because That's Where Most People Start
We name Yoast in the title of this post for one reason: by its own installed base, 10 to 13 million active sites, it's the largest plugin in the category (Capterra, Yoast SEO), so it's the most common place this exact move starts from. Nothing about the preview-and-rollback approach is specific to Yoast, though, and we built it that way on purpose. The same five importers, the same confirmation screen and the same settings-export rollback apply whether the plugin you're leaving is Rank Math, SEOPress, AIOSEO or The SEO Framework, because we'd rather build one rule five times than build a shortcut for the plugin everyone happens to be leaving.
The Week After You Switch
Install the plugin, run the importer, review the preview, confirm it. Your titles are the ones you wrote. The redirects still redirect. The schema still validates. Nothing about the front end looks different to a visitor that afternoon, because nothing was supposed to: the whole job of a migration is to be invisible to everyone except you, the one person who knows what used to be there.
The visible part comes later, when something the old plugin never had gets switched on: a citation scorecard showing whether ChatGPT names your business, or a schema type from the 657 in the index the plugin ships with. That's the actual reason to switch, and it only matters once the boring part, the titles, the redirects, the settings you already got right, has come across without you having to redo any of it.
Why We're Telling You This
We want you switching to us, obviously, so weigh that before weighing anything else in this post. But the preview-before-write rule and the rollback trail hold whether you switch this month or never: check any importer against those two things before you hand over two thousand title tags that can't be gotten back.
The boring part is the whole point of this post, titles, redirects, robots settings, the breadcrumb separator you already got right, all coming across untouched. It comes across so the visible part can start. We'd rather earn the switch by being boring first, so the interesting work, the citation scorecard, the schema coverage a rival plugin never measured, has somewhere solid to land. Read what a plugin can actually measure, or see how the category stacks up on the AI question. If you want the customer's version of this same checklist, we wrote that one too.
Import your settings, keep every title you wrote, and see what changes once the boring part is finished. Try the importer, or start with the free scorecard first. We look forward to making the switch as boring as it should always have been, and to whatever you decide to do next.