The job
Where the Claude blog post validator fits
Between finishing a draft and putting it in the CMS there is a gap where nothing checks anything. The draft is in a doc, the SEO tools want a live URL, and the plugin that would have stopped you only works once the post is inside WordPress. This fills that gap: paste the draft, read the review, fix it, then publish.
The review is generated on our server, so the draft leaves your browser. Budget accordingly: 5 runs per rolling 24 hours, 12,000 characters each, with an optional instruction of up to 300 characters. For a weekly publishing rhythm that is enough for a structure pass, a prose pass and a final look.
The loop
How to validate a blog post in three steps
Run it once the draft is complete, not while you are still writing it.
- Step 1
- Paste the draft with its headings. Keep the heading markers in, because structure is half of what you are asking about.
- Step 2
- Name the worry in the instruction box. "Does the intro deliver what the title promises?" gets a usable answer; an empty box gets a general one.
- Step 3
- Copy the review out and work through it in your editor. Then do the CMS checklist separately, because the two passes cover different things.
Split the work
The text checklist and the CMS checklist
PublishPress Checklists is the best public inventory of what people actually check before hitting publish, and running down its list makes the split obvious. Some items live in the words, some live in the post record.
- In the draft, so reviewable here
- Heading order and a single top-level heading, title and excerpt wording, section length and balance, repeated paragraphs, whether the opening arrives at the subject.
- In the CMS, so not reviewable here
- Featured image, its alt text and caption, image dimensions, internal and external link counts, tags and categories. PublishPress checks these where they live.
- On the live page, so not reviewable here
- Page speed, Core Web Vitals, mobile usability, schema and indexing. The Apify and AIOSEO audits start from a URL for exactly this reason.
- Neither, until you look
- Whether the links resolve. Nothing on this route fetches a URL, so a link in your draft is text and stays unverified.
Long pieces
Reviewing a post that does not fit in one run
The box stops at 12,000 characters and the counter above it shows characters and words as you paste, so you know before you run out. A long guide needs a plan rather than a truncation.
The approach that works: paste the headings plus the first sentence of each section as run one, which answers the structural question cheaply. Then spend the remaining runs on the two or three sections you are least happy with. Reviewing every section in full is rarely what a draft needs, and it is not what the allowance is for.
In practice
Fitting a validation pass into a publishing schedule
The allowance resets on a rolling 24-hour window rather than at midnight, which matters if you publish in batches. Five runs used at four in the afternoon are back by four the next afternoon, so a two-post day is workable and a five-post day is not.
Nothing is stored between runs. There is no history, no saved draft and no account, so the review exists in the result pane until you copy it out. Get into the habit of pasting it into the document you are editing before you run anything else.
The objection
Why the blog post validator gives no score
The URL auditors give you a number. Apify's blog post SEO check returns columns headed URL, Score, Title, Issues and Words. A number is satisfying and it is also not an instruction: nothing in a score tells you which paragraph to cut.
This returns sentences instead, which are slower to read and faster to act on. It also means there is no pass or fail state to game, and no threshold that a mediocre post can be edited just over. If a review says the third section repeats the second, that is either true of your draft or it is not, and you can check in a few seconds.
Where it stops
What this blog post validator does not cover
No URL input, no crawl, no site audit, no broken link check. No schema, no Core Web Vitals, no indexing status, no keyword volume and no competitor data. No WordPress, Yoast or Rank Math integration, and no ability to block a publish the way PublishPress can when a task is set to Required.
It also does not rewrite the post, does not check plagiarism and will not tell you what an AI detector will report about it. Those are separate jobs, and a validator that claimed all of them would be claiming something no text box can do.