Check a draft before you publish it

ContentBeginner~3 min

Before you start

A connection bound to a user who can edit the draft, since reading a draft that is not public needs edit access to that item. You need the post or page ID, which is the number in the editor's address bar. The abilities listed above must be switched on in the Abilities tab; every ability starts off.

The last minute before you hit Publish is when the small things show up. A title that will be cut off in search results. A post filed only under the default category. A featured image with no alt text, or a link that goes to a draft preview. None of it is hard to fix, but you have to notice it first.

This prompt reads one draft and notices for you. It reports and recommends. It does not touch the post.

The prompt
Check draft [post ID 482] before I publish it. Read only: do not edit it, do not
publish it, and do not change anything else.
Read the post, using the raw block markup for its content. If it is a page,
read it as a page. Then report on each of these, as pass, or fix with the exact
text involved:
1. Status: is it still a draft or pending, or already live?
2. Title: its length in characters. Flag it if it is empty, or if it is likely
to be cut off in search results (roughly over 60 characters).
3. Categories: is it in at least one, and is it filed only under the default
category?
4. Featured image: is one set, and does it have alt text?
5. Headings: any skipped levels (an H2 followed by an H4), any empty heading,
any H1 inside the body.
6. Links: list every link. Flag empty links, bare # links, plain http links,
and links to this site's own preview or draft URLs. You cannot open URLs, so
do not say any link works.
7. Images in the content with no alt text.
8. Leftovers: lorem ipsum, TODO, XXX, or notes in square brackets.
9. Length: a rough word count.
End with a verdict: ready, ready after small fixes, or not ready. List the
fixes in the order I should do them.

Why this is safe to run

The abilities behind this prompt read a single post or page by ID. They return the title, status, categories, featured image and content, and the prompt tells the agent to change none of it. Publishing is a separate ability with its own capability gate, and nothing in this prompt calls it.

Two honest limits. The checks on links and headings come from reading the markup, so they catch structural problems and miss everything that needs a live request. And the excerpt is left out on purpose, because the read cannot say whether one was written. Treat the verdict as a second pair of eyes, not as sign-off.

Already connected? Skip the paste. Ask your agent for the “check a draft before you publish it” recipe and give it the post ID, and it runs the same reads on your own site.

How it works

  1. Read the draft with its raw block markup and confirm it is still a draft or pending.
  2. Check the title length, the categories and the featured image with its alt text.
  3. Check the heading structure and every link in the content.
  4. Look for images with no alt text and for leftover placeholder text.
  5. Give a verdict of ready, ready after small fixes, or not ready, with the fixes in order.

Questions

Does it check that the links work?
No. The abilities read the post, they do not open URLs. The prompt checks the links it can judge from the markup, such as empty ones, bare # links, plain http, and links to this site's own preview URLs, and it is told not to claim any link is alive.
Why is there no excerpt check?
The post read returns an excerpt whether or not anyone wrote one, because WordPress builds an automatic one when the field is empty. The agent cannot tell a written excerpt from an automatic one, so a check would pass every post.
Does it cover my SEO plugin's title and description?
Not in this prompt. It stays with what a stock WordPress post holds. If you run a supported SEO plugin, your agent has a separate read for that plugin's fields, and you can ask for it as a second pass.