Export and import settings

What it is

Settings import / export moves your plugin configuration in and out as a JSON file — the fast way to clone a setup onto another site, or to keep a copy before a big change.

The export covers configuration only: Brand Context, Writing DNA, default title and description variants, SEO templates, language defaults, which providers are on and which models they use, social and Organization data, LocalBusiness (NAP) details, llms.txt content, rotation settings, enabled post types and taxonomies, image and Vision settings, and the rest of the same family.

Alongside them travel your Q&A sets, if you leave the Include Q&A sets checkbox ticked — it is on by default and shows how many sets this site has. Each set goes out with its pairs, its options and the page it is attached to, and the page reference travels as a slug, not as an ID, because IDs do not survive a move between sites. This matters more than it sounds: Q&A sets are content, not options, so before this they were the one thing an export left behind.

Operational data is deliberately left out — usage counters, SEO snapshots, credits, license state — and so are secrets. API keys live in a separate registry and are exported only if you explicitly ask for them, so a normal settings export is safe to move between your own sites without carrying credentials around.

Where to find it

AISA → Utility, the Settings import / export card. The Database cleanup card, further down the same page, carries the warning that belongs with it: deleting the plugin data on uninstall deletes your Q&A sets too, so export them first — with a link straight back to this card.

Requirements & tier

Free, with the administrator capability (manage_options). Nothing is sent anywhere: the file is generated and downloaded by your browser, and the import reads the file you choose.

How to use

On the source site open AISA → Utility → Settings import / export.
Decide about the two checkboxes: Include API keys (off by default — tick it only if the file stays private) and Include Q&A sets (on by default).
Press Export settings (.json) and keep the file.
On the destination site, in the same card, choose the file. If it contains Q&A sets, pick what happens to the ones already there: Skip sets that already exist, matched by title, which is the default, or Replace them with the ones in the file.
Press Import settings and read the summary: how many settings were restored, and for the sets how many were imported, how many skipped and how many came in without a page.

A set whose page does not exist on the destination site is imported all the same and reported as “without a page”: you attach it to a page later, and nothing is silently lost.

Questions people ask

Are my API keys in the export? Not unless you tick the box. Provider keys and other secrets live in a separate registry and stay out of a normal export.
Will importing settings overwrite my SEO? No. This card handles configuration, not per-post SEO. For the content itself use SEO data backup / restore.
What happens to a Q&A set that already exists on the destination? Whatever you choose at import time: skipped by title, which is the default, or replaced by the version in the file.
How does a set find its page again on another site? By slug. Both sides of the link are reconnected, the set to the page and the reference inside the page back to the set — otherwise the page would still point at a set that no longer exists and would render empty.
Can I use this to set up a client site quickly? Yes. Export from a configured site, import on the new one, and Brand Context, templates, defaults, provider settings and Q&A sets are there in one step.
I am uninstalling the plugin — what should I save first? Export the settings with the Q&A sets included, and create an SEO backup. With “remove all plugin data on uninstall” enabled, the sets go with everything else.

Backup and Restore SEO
Q&A / FAQ generator with FAQPage schema
Migrate SEO between plugins