Let an AI chat maintain thousands of pages, while you approve every change
Copywriters, SEO specialists and editors ask an assistant to fix, update, translate and compare content. Content Review scans the whole site and holds every change as a proposal. You see the difference, apply or reject it, and roll it back if it was wrong.
- Pro package only
- Nothing changes by itself
- Works with any AI chat that can send a request
- Scan report
- Proposals
- Changes view
- Roll back
- Translation checks
Too much content, too many hands, too little control
Too many pages to check by hand
A site with thousands of pages, posts, products and documentation pages. Nobody knows which have an empty description, no picture or a missing translation. A manual audit takes weeks and is out of date the day it ends.
Everyone uses a chat, nobody has a process
A copywriter, an SEO specialist and an editor each fix text in an AI chat and paste the answer into a live page. You want to see what changes, accept or reject it, and go back if it was wrong.
Translations drift
The original was edited and the translations were not. Or an article exists in one language only, on a site that has many.
A page looks broken
After an import or an editor mistake: code printed on the page, blocks that no longer open, strange long dashes everywhere.
Many people, one article
A team of many people and several tools suggest changes to the same article, and the changes overwrite each other.
Find what needs work across the whole site
It reads pages, posts, products and docs in batches and keeps the report, so a big site does not have to be checked in one visit. You get a list that you can hand out to the team.
- An empty excerpt, an empty SEO description (Yoast, Rank Math, SEOPress and Baza Helper fields) and no featured image, except for pages
- Missing translations and translations older than the original (Polylang, WPML or Baza Helper translations)
- Long dashes on the page, the dash that machine-written text likes
- Filters by problem and by language, 20 per page
Ask in a chat, approve here
A copywriter, an SEO specialist or an editor asks their AI chat to fix, update or translate content. The assistant sends the change over a secure connection (an application password of a user who may edit others' posts). The change waits as a proposal, and the page stays as it is.
Each proposal is a card: the title, the kind, the language, the fields it changes, the size, the reason and the source. It can change the title, the text, the excerpt, the SEO description, the featured image, or create a new article as a draft.
- "Changes" shows a difference with a few lines around each change
- "Apply", "Reject", "Choose image" and "Queue translations" on every card
- "Apply all" applies the waiting proposals, oldest first, so an original exists before its translations
- A proposal can change a part of an article: add after a heading, append, prepend or replace a text. Several proposals for one article work together
And back again
Every applied change keeps the values it replaced, in the journal. "Roll back" restores them, and a new article is moved to the trash.
If you edited the same fields after the proposal was made, "Apply" refuses and offers to apply anyway. Your work is not overwritten.
- The journal lists every applied change
- "Roll back" refuses in the same way if the article changed afterwards
Update and translate in every language, in step
The scan finds missing translations and translations older than the original. "Queue translations" hands an original article to the translation queue of the plugin, with the services you connect.
A proposal of the kind "link" ties existing articles together as translations of one another.
- Judged from the default-language post (Polylang, WPML or Baza Helper translations)
- A new article is made as a draft with its language and its translation link
Broken pages found early
After an import or an editor mistake a page can print code or lose blocks. The scan checks the block markup of every page.
- Unpaired block comments and attributes that are not valid
- Block names nobody registered, and loose HTML between blocks
- Old content that is not in blocks
- Text that lost its escape characters, so the page prints raw code
The same content, with a safety net
| Without Content Review | With Content Review |
|---|---|
| You audit pages by hand | One scan lists the problems |
| Everyone pastes chat answers into live pages | Every change from every chat waits as a proposal in one list |
| You see the new text only after it is live | You see the difference before anything changes |
| A wrong edit means searching for the old text | The journal keeps it and "Roll back" restores it |
| Edits overwrite each other | Apply refuses when the page changed since |
Made for sites with a lot of content and a lot of people
A site with a huge catalog or documentation
You get a report of what to fix, let an assistant prepare the changes page after page, and approve each one without a manual audit.
A team of many people
Copywriters, SEO specialists and editors each work in their own chat. The changes wait in one list with a count in the header, and a journal shows what was applied.
An agency that handles content for clients
Proposals, the journal and Roll back give you a record of the changes made on each client site.
What it needs, and what it is not
The Pro package
Content Review is in the Pro package only. Nothing changes until you press "Apply".
An application password
Each person or script connects with the application password of a user who may edit others' posts, from any AI chat that can send a request. A Setup screen explains how and checks the site.
A multilingual site for translation checks
The scan and the proposals work without it. The translation checks and links work with Polylang, WPML or the translations made by Baza Helper.
What it is not
- It is not an assistant: it does not write text. It receives proposals from the assistant or script you connect and makes applying them safe.
- It does not change anything on its own. The scan only reads, and a proposal changes a page only after "Apply".
- Whether the block editor accepts a block's markup cannot be seen on the server. The report finds structural problems, not every editor quirk.
Questions before you start
Does it change my pages by itself?
No. The scan only reads. A proposal changes a page only after you press "Apply".
Which assistant can I connect?
Any assistant or script that can send an HTTP request with an application password. The site owner chooses it; no specific product is promised.
What if I edited the page after the proposal?
"Apply" refuses and offers to apply anyway, so your edit is not overwritten by accident.
Can I undo a change?
Yes. The journal keeps the values that were replaced, and "Roll back" restores them. A new article is moved to the trash. It refuses if the article changed afterwards.
Does it work on a site with one language?
The scan and the proposals do. The translation checks and links need a second language, from Polylang, WPML or the translations made by Baza Helper.
Can many people on my team use it at once?
Yes. Each person connects an assistant with the application password of a user who may edit others' posts. Every proposal shows its source, all waiting proposals are in one list, and several proposals for one article work together.
How big a site can it handle?
The scan reads in batches and keeps its report, so it does not have to finish in one visit. We do not promise a number of pages.
Is my content sent anywhere?
The tool itself sends nothing out. The assistant you connect reads and sends through your own site, and the site owner chooses that assistant.
Let your whole team use AI without the risk
Content Review is a Pro tool, included in the Pro, Plus and Agency plans.
