Getting started

Before you begin

Three things, none of which take long to check.

The licence and the AI account are separate things and stay separate. We bill the licence. Your provider bills you directly for what you generate, at their own prices, with no margin added by us.

1. Install and activate

Upload the plugin and activate it. You will land on Settings with a short checklist.

2. Connect a provider

A new install starts on Google Gemini, which has a free tier. Paste a key and press Test. If you would rather use something else, the provider list is grouped into those with a free tier and those needing a funded account.

One thing worth knowing before you choose: on Gemini's free tier, Google may use what you send to improve its products. Their paid tier does not. That is fine for your own site and worth paying to avoid on client work under confidentiality.

3. Add topics

Topic Manager takes a list. Each topic can carry its own category, language and structure. Nothing is written yet — the queue is just a queue.

If the queue is empty, Content History will say "Nothing to do" rather than report an error. That is not a fault; it is the schedule running and finding no work.

4. Generate

Generate Post writes one article and leaves it as a draft. Read it, edit it, publish it if you want it. Nothing publishes on its own unless you change the default status.

Next: configuring AI providers, cost and run ceilings, and approvals, revisions and undo.

Reading the first draft

Read it as an editor rather than as a reviewer of the software. The questions worth asking are whether the piece says anything your site has not already said, whether the claims in it are ones you are willing to stand behind, and whether it sounds like you.

That last one is the usual reason a first draft disappoints. A model given a thin brief writes generically because it has nothing else to go on. Filling in the business profile and giving a topic its own structure changes the output more than switching model does.

Before you leave anything running unattended

Everything above is manual: you press a button, one article appears as a draft, nothing goes live. The moment you schedule generation or hand work to an agent, two settings stop being optional.

Set run ceilings so a job that decides it needs one more step cannot keep deciding that indefinitely. At minimum give it a step count and a spending limit, because a ceiling left at zero means no limit of that kind rather than a cautious default.

Turn on approvals if you want a person between the draft and the site. Every change an agent makes is recorded before it happens and can be put back afterwards, but approving first is cheaper than undoing later.