Feature · Review
Every draft opens on the article, with the rules it still fails beside it.
seodraft opens a post on the article as it would ship, and editing is a mode you enter from there. A column on the right holds the last rules run, split into errors and advisories, and the plan your agent committed to before writing a word. The card below is the set of length limits those rules apply, read from seodraft's gate configuration.
7 days free, no card needed. Then $5/month if you subscribe.
What is an AI content editor?
An AI content editor is the review step where a person reads a draft a model wrote and decides whether it ships. The work is checking: that the title and description fit their limits, that the article answers the question it was written for, and that every claim traces back to something the business knows first-hand.
seodraft gives that step a screen. Your agent writes over MCP, the deterministic rules run on the saved draft and store what they found on the post, and the screen shows you the article, the failed rules and the brief. The approve button calls the same function as the MCP tool your agent would call, so the browser and the agent can never mean two different things.
What the review screen shows
- The article first
- A post opens on the preview, as the file would ship, and editing is a mode you switch into.
- The canonical fields
- Title, description, date, tags, TL;DR and the FAQ pairs as fields, with the body in Markdown.
- Errors and advisories
- An error blocks approval. An advisory is reported and left to your judgement.
- A draft opened cold
- The last run's findings stay on the post, so the failed rules are listed before you check anything.
- The plan panel
- The brief the agent committed to: angle, evidence with its status in your bank, outline, SERP questions and image slots, read-only.
- Export from the header
- Markdown with frontmatter, or one HTML file, downloaded whenever you want the article out.
The limits the rules apply
- Title
- 60 characters
- Description
- 160 characters
- TL;DR
- 100 to 400 characters
- FAQs
- 3 minimum, answers up to 500 characters
- Thin content
- under 500 words, advisory
Frontmatter checked
- title
- description
- date
- updatedDate
- image
- tags
- draft
- tldr
- faqs
How a draft reaches approval
A draft reaches the approve button in three steps, and each one is recorded on the post.
- 1
The agent writes and checks. It saves the body over MCP and runs the rules, which store their findings on the post.
- 2
You read what the rules found. The findings sit next to the article, and any edit clears them so the list always describes the body on screen.
- 3
You approve. The button stays disabled while an error stands, and approving marks the post ready and delivers it when a repository is configured.
What it costs
Reviewing costs nothing on top of the $5/month plan. The rules run as code in your workspace, the screen calls no model, and neither the check nor the export touches your DataForSEO balance.
Questions about reviewing a draft
Short answers on editing by hand, what blocks approval and what three failed checks mean.
- Can I edit the draft myself?
- Yes. Edit mode gives you the fields and the Markdown body. Saving raises the post version, clears the stored findings and moves the post back to writing, so the rules run again on what you wrote.
- What happens after two redrafts?
- The third failing check moves the post to failed and records the rules it broke. You reopen it from the same screen, and the useful next move is handing the finding to your agent.
- Does approving publish the article?
- Approving marks the post ready and, when a git destination is configured, writes a file with draft: true into your repository. Publishing happens in your CMS, by you.
Related
- CMS delivery · Where an approved draft lands in your repository.
- E-E-A-T evidence · The first-hand pieces an article has to carry.
- AI slop checker · The prose rules, run on any text you paste.