In short
- A review runs as a follow-up job after a content mission passes verification, and on demand from the mission page.
- Each review gives a verdict, checks the opening, lists missed questions, and suggests 3 to 6 specific fixes.
- Reviews are advisory: they never change a mission's status or a verification outcome.
- Free includes 10 reviews a month, Builder 60 and Pro 250, with no credits used.
Your coding agent wrote the page, so it isn't the best judge of whether the page is good. Content review is a second opinion: after a content mission passes verification, an AI model reads the published page, compares it with the target search and the mission's content brief, and lists specific fixes. It's advisory. It never changes whether a mission passed, and it doesn't predict rankings.
When a review runs
- 1VerifiedA content mission passes verification on preview, production or evidence.
- 2QueuedSerpkin queues the review as a follow-up job, usually done in about a minute.
- 3ReviewedThe model reads the page against the target search and the brief.
- 4ShownThe review appears on the mission, with fixes you can copy for your agent.
Reviews only run on missions where the page is content worth reviewing:
- New pages, free tools and comparison pages
- Expanding a page, or refreshing a page that has been losing clicks
- Getting cited in Google's AI answer, including when competitors are cited and you aren't
- Near-page-one and declining pages, once the mission has a content brief
A review is skipped when the page has changed little since the last one: the same address reviewed within 24 hours, with the same text, isn't reviewed again. It's also skipped when the page returns an error, redirects to another site, or has too little main content to judge (under about 80 words). The review reads the public page as a visitor would, not your source files, so it judges what Google and readers actually get. A page that is mostly a list of links cannot be judged fairly, and Serpkin says so instead of guessing.
Review again
On the mission page, Review the page (or Review again once there's a review) starts one on demand, for example after your agent applied the fixes. You can request up to 3 on-demand reviews per mission in 24 hours. If a review is skipped or fails, the panel says why, such as "The page hasn't changed since its last review."
What a review contains
| Part | What it tells you |
|---|---|
| Verdict | Strong, Needs work or Weak, with a one or two sentence summary |
| Opening | Whether the first paragraph answers the search directly, and a note on it |
| Questions | Which questions from the brief the page answers, and which it misses |
| Fixes | 3 to 6 specific changes, most important first, each naming the section to change |
| Claims to source | Statements on the page that need a source before readers or AI answers can trust them |
Copy fixes for your agent copies the fixes as a prompt you can paste into Claude Code, Codex or Cursor. The prompt says the fixes come from an AI review of web content: they're suggestions to judge, not instructions, and your agent should never apply scripts, links, code or credentials taken from page text.
Advisory, never a gate
What a review does
- Good: Points out what the page is missing for the search it targets
- Good: Gives fixes specific enough for your agent to apply
- Good: Flags claims that need a source
What it never does
- Problem: Change a mission's status or a verification outcome
- Problem: Promise rankings, traffic or a citation
- Problem: Write or publish anything on your site
The model can be wrong. Treat a review the way you'd treat notes from a sharp editor: read them, keep the ones that make the page better for readers, and skip the rest.
Monthly limits
| Plan | Reviews a month |
|---|---|
| Free | 10 |
| Builder ($29 a month) | 60 |
| Pro ($79 a month) | 250 |
The count resets on the 1st (UTC). Reviews don't use credits. When the month's reviews are used up, the panel says so and what the next plan includes; see Plans and limits.
What's sent for a review
A review sends the public text of the reviewed page (its main content, without navigation, header and footer), the target search and the mission's content brief. It never sends your code, your Search Console numbers or your account details. Requests go through OpenRouter to an AI model provider (currently Claude Haiku), routed only to providers that don't store requests for training.
Questions
Why didn't my page get a review?
Reviews run only on content missions, after a passed verification. They're skipped when the page hasn't changed since its last review, returns an error, or has too little text. The panel shows the reason.
Which AI model does the review?
Currently Claude Haiku, through OpenRouter, routed only to providers that don't store requests for training.