SEOWrench

You can keep them installed, and SEOWrench will not fight them: while another SEO plugin is active, SEOWrench emits no tags at all. It keeps reading and reporting, and the import screen stays available. To have SEOWrench write your tags, deactivate the other plugin. SEOWrench never does that for you — that is your decision, not ours.

Yes. The import copies into our fields and never touches the original, so the Rank Math data is still there. The import screen has an "Undo this import" button that removes only what came from that plugin and is still identical to it — anything you edited afterwards stays.

Yes, and it takes one click. SEOWrench → Settings → Import ends with "Take it with you": a CSV of every SEO title and meta description on the site, with the address of each page. Nothing is changed or removed — the file is a copy. Your titles and descriptions are also stored in ordinary WordPress post meta, not in a private table, so they stay in your database whatever you decide to run next.

AIOSEO stores its data in its own database table instead of post meta. SEOWrench detects it and stays read-only: it analyses and reports, but does not import from it or write over it. Reading another plugin's private table from the outside breaks on its first update.

Values that use the other plugin's template variables (like %sep% or %%sitename%%) are left behind and counted on screen. Those are instructions for that plugin's engine, not text — copying them as-is would print the percent signs on your page.

GEO — generative engine optimisation — is about whether AI assistants can read your site and use it in an answer. This plugin measures the readable part of that, and says which part it cannot see. Locally: which of the thirteen AI crawlers your robots.txt allows, whether /llms.txt answers, how much schema each content type has, what reaches your sitemap, and what is set to be indexed. From the outside, with the audit: a GEO score for the whole site, and what is left of each page with JavaScript off, which is how the crawlers read it. What it will never tell you is that any of this makes an AI cite you — nobody can measure that from a plugin.

No, and they are kept apart on purpose. The SEO side is about being found and ranked by a search engine. The GEO side is about being readable and usable by an AI assistant, which fails for different reasons — a page built entirely in JavaScript can rank and still leave an assistant with nothing to read. Both come from our own rules, measured on your pages, never from a model's opinion.

Most of the time, nowhere: the title and the description are written on your own server, from your own page. Your content travels only when the page has no text for that to work with, or when you ask for a focus keyword — then, on that click and only while your account is connected, what goes is plain text: the title, an excerpt of the page, the headings, the slug and the terms. Never the page HTML, and never in the background.

The tags are written from data already in memory when the page is built. The analysis screens run only in the dashboard, for logged-in users. Visitors trigger nothing.

The 200 most recently modified ones, and the screen says so. An unbounded scan would freeze the dashboard on large sites.

Nothing in the plugin stops working. Titles, descriptions, social tags, the import, the sitemap controls and every analysis screen keep running exactly the same — the limit applies only to how often the audit service runs.