Content
Review: why nothing publishes automatically
The step where you approve content before it goes live, and what your options are.
Open this in the portal →You are the final step
Every piece of content the AI writes goes to Review first. Nothing goes live without a human having seen it. This is not an extra hurdle for form's sake, but the core of how we handle AI content.
Your three choices
Per draft you can:
- Approve — the piece is agreed, but not yet published
- Approve and publish — agreed and live at once
- Reject with a reason — back to the drawing board, with your note attached
The first time you publish
The very first time you set something live, we ask you to confirm it explicitly. After that you know how it works and it goes without the extra step.
Test mode
If you have no connection to your website (CMS) yet, publishing runs in test mode: you see how it would go, but nothing changes on your real site. That way you can try the flow calmly.
More than just articles
In Review you don't only approve texts. A proposal to change a URL passes here too (see Redirects), as do drafts to get mentioned by other sites.
And automatic approval?
That is possible, but off by default. Only if you set a threshold yourself does the AI approve pieces under strict conditions. Do nothing, and every draft waits for you.
Suggesting a change instead of making it
In Review you can change a text in two ways.
Edit changes the draft directly. What you save is in the text straight away.
Suggest a change proposes a change without touching the draft. That helps when you want to put something forward, or when you want to look at your own proposal again before deciding.
To make a suggestion:
- Open the draft and click Suggest a change.
- Select the text you want changed in one of the fields, such as Page title / H1, Short description, Long description, Meta title or Meta description.
- Type your suggestion and add a short reason if you want to.
- Click Add suggestion.
While a suggestion is open, nothing about the draft text changes.
If an error or dropped connection means the create cannot be proven, your selected passage, replacement and reason stay in the form. You can retry the same suggestion without typing it again. An unchanged retry is not stored as a second suggestion if the first request actually committed in the background.
The quality check
Under every draft there is a quality check. It looks automatically at things like the length of your meta title, whether your keyword appears in the text, whether the headings run logically, and whether there are claims that need a source.
For each point you see whether it is fine, whether it needs attention, or whether it is not measured. Not measured does not mean something is wrong. Some points, such as whether the text fits your brand, are judged later by a person or by AI; those deliberately stay on not measured rather than us pretending they passed.
Points needing attention come first, because that is what you can act on.
When the check is out of date
If you change the text, or accept a suggestion, the previous check no longer applies. You will see clearly that the check is out of date and why. The old result stays visible, because it is usually still largely useful, but it is not presented as if it were current.
Click Check now to run it again. That changes nothing about your text and publishes nothing; it only looks again.
The list before you publish
At the bottom there is a short list with four topics: tone and brand, claims and sources, search intent and structure, and practical value. That list summarises what we could check automatically.
It is not an approval, not a legal or medical review and not a fact-check. What you publish remains your responsibility.
Reading a suggestion
Every suggestion shows Before and After underneath each other, with the surrounding text included, so you can see which passage it is about. The changed word is struck through in red under Before and shown in green under After.
Above that you see who made the suggestion, which field it belongs to, and its status. At the moment, suggestions are made by you and your colleagues in Review.
- Open: not decided yet.
- Applied: the suggestion was accepted and is now part of the draft.
- Declined: you turned it down. The text did not change.
- Base changed: the text has since been edited, so this suggestion no longer fits.
Accepting and declining
Accept applies the suggested text to the draft. That counts as an ordinary edit: the content optimisation score no longer describes the new text, so it reads Not scored yet until you score it again.
Decline leaves the draft unchanged. You can add a short reason.
Accepting is not the same as approving, and not the same as publishing. An accepted suggestion is still a draft: you approve it yourself afterwards and publish it as a separate step. Accepting a suggestion also changes nothing about your brand guidelines or your product data.
If someone else changed the text in the meantime
When several people work on the same text, a colleague may change something while your screen still shows the older version. If you then save or accept, it is refused and you see a message next to the button you clicked.
In that case nothing is saved, so your colleague's work is not lost. Refresh the page, look at the current text, and make your change again.
Suggestions are kept
A suggestion you make is stored. You can refresh the page, close the tab or carry on later on another device: your open suggestions will still be there.
So you do not have to finish a review in one go. Make suggestions when it suits you and decide on them later, including together with a colleague.
An accepted suggestion is ordinary text in the draft from that moment on.
If your connection drops while you are accepting or declining, refresh the page and look at what is there. What you see is what has been saved. If you then click the same button again on the same suggestion, that decision is not taken twice.
What happens to your credits when you reject
If you paid for the draft with credits, you get them back the moment you reject it. The message tells you how many.
This happens exactly once per draft. If you click twice, or you and a colleague reject at the same time, the credits are returned once and the second message names no amount.
If the article came out of your monthly allowance, nothing was charged, so nothing comes back. The allowance slot itself is not freed up.
If the draft came from the queue, your balance does not change. The rejection still happens.
Please note: a draft whose credits you got back cannot be restored from the Archive afterwards. Otherwise rejecting, getting the credits back and then restoring would be a free article. If you still want to try, generate a new version. You pay for that one again.