WordPress editorial workflow: a checklist for submissions
By Aleksan Aharonyan ·
A WordPress editorial workflow for submitted posts is one fixed sequence of checks that every guest post and member post goes through before it appears on the site. WordPress already supplies the parts that decide who can do what, such as roles, the Pending post status, revisions and the media library; the checklist supplies the judgment WordPress cannot. Here is the order to run the checks in, what to look at in each one, and how to record the decision so the next submission gets the same treatment.
Key takeaways
- Run the six checks in the same order every time, because a queue judged differently each day produces posts of uneven quality and authors who cannot tell what is expected.
- Set the form that collects submissions to the Pending post status, so no post reaches the front end before a person has read it.
- Give submitting members the Contributor role rather than Author, so WordPress itself enforces review even when you are in a hurry.
- Email the author with the decision and the one thing to do next, because silence is the fastest way to lose a contributor.
What belongs on a checklist for submitted posts?
A checklist for submitted posts covers only what actually goes wrong when someone else writes the post: formatting that breaks the theme, missing or unlicensed images, links you would not have chosen, spam, an unclear status, and an author who never hears back. It is not a style guide and not a full copy-edit. Copy-editing can wait; the checklist is about whether this post can go on your site, and who decides.
The order matters as much as the items. Each step is cheaper than the next and rules out work later: there is no point checking an author’s links if the post is spam, and no point choosing a status before you have read the body. The decision sits second to last, and the email to the author comes after it.
Two principles keep the checklist honest. Write down what “good” means for each step, so a second reviewer reaches the same answer. And treat every submission the same way regardless of how it arrived: by email, as a shared document, or through a front-end form on the site.
Step 1: Check the title, slug and formatting
The title, the slug and the body formatting are the first check, because they are the fastest things to fix and the most visible when they are wrong.
Start with the title. It should say what the post is about, not tease it. Cut trailing punctuation, fix capitalization, and make sure it does not read like a sentence copied from the first paragraph. If it is very long, shorten it now: WordPress builds the slug from the title, and a long sentence makes a slug you will want to change.
The slug is the URL. WordPress generates it and usually gets it close enough; trim it if it is unwieldy. Do not change a slug after the post is published, because every existing link to it breaks.
Then the body. Text pasted from a word processor or a cloud document carries inline styles, spans and odd spacing. Use the editor’s paste-as-text option or clear the formatting before you start. Check the heading structure: section headings should be H2 and H3, with no second H1 inside the body, since the theme already prints the title as the page’s main heading. Look at lists, quotes, embeds and code blocks in the preview rather than the editor, because that is where they break.
If posts arrive through a form, the editor you offer in that form decides how much of this you do. A Markdown editor or a plain text box produces clean markup with almost nothing to strip out; a full visual editor gives authors more freedom and gives you more to clean.
How to tell it worked: preview the post at a narrow width and on the front end. If the title wraps sensibly, no heading looks like a page title, and nothing has leftover styling from another program, step 1 is done.
Step 2: Confirm the featured image, categories and tags
The featured image, the categories and the tags are the second check, because they decide how the post appears in your archive and whether a reader can find it again.
The featured image needs three things: it exists, you have the right to use it, and it fits your theme’s archive layout. A wide image cropped to a narrow thumbnail can lose the subject, so look at the archive page, not just the post. Add alt text that describes the image.
For categories, choose one primary category that matches where the post lives on the site. Categories are structure, so adding a new one should be a deliberate decision, not a side effect of a submission. For tags, reuse the tags you already have, check the spelling against the existing list, and keep the number small. Tags are for retrieving related posts, not for repeating the title’s keywords.
If a taxonomy field in your submission form shows nothing, the cause is usually a form setting rather than a WordPress problem: terms may be excluded from the field, or terms with no posts may be hidden.
How to tell it worked: open the category archive the post now belongs to. The post should appear there with an image that makes sense at that size and a tag list you would have chosen yourself.
Step 3: Review links, credits and disclosure
Links, credits and disclosure are the third check, because a submitted post is the most common way a site ends up pointing at something its owner would not have chosen.
Open every outbound link. Check that the destination is the site the anchor promises, that the page still exists, and that you are willing to be associated with it. Read the anchor text: it should describe the destination, not repeat the target keyword, and not say “click here”. More than a handful of outbound links in a short post is a reason to look closely at why they are there.
If any link is paid, sponsored or an affiliate link, mark it the way the search engines your site relies on ask you to, and put the disclosure near the top of the post rather than at the end.
Credits come next. Guest posts need a byline, a one-line bio and, if your site uses them, a photo. If the author cites a study or a report, check that it exists and that the post describes it accurately. A citation you cannot verify is a reason to hold the post, not to publish and fix it later. Disclosure also covers how the post was made: if your site asks authors to declare that text was generated with AI, read the declaration before you publish.
How to tell it worked: you can explain every link, name and claim in the post without looking anything up again.
Step 4: Run moderation and spam checks before publishing
Moderation and spam checks come fourth, because the cheapest time to reject a post is before it is published, indexed or announced.
Look for the signals that repeat: a brand-new account, a bio that is only a link, a topic unrelated to the rest of the site, a body that reads like a rewritten product page, several links to one commercial domain, or text addressed to the editor instead of the reader. Search one distinctive sentence to see whether the post has already been published elsewhere. If the same submitter has sent posts before, read the older ones: a pattern tells you more than a single post does.
Captchas and review solve different problems. A captcha stops bots from filling in the form and does nothing about a person who writes a plausible but promotional post. Review stops the person and does nothing about a flood of automated submissions. Decide which one you actually have before you add tooling.
If you want the first pass automated, Front User Submit, a free plugin for frontend post submission and guest posting forms, includes AI moderation on its Pro plan: each new post is checked against spam, abuse and rules you write, and a flagged post is saved as Pending or Draft instead of going live. The AI moderation guide (Pro) explains how to write those rules, and the plans and prices page lists the paid options.
How to tell it worked: the post you approve survives a week on the site without a spam comment, a takedown request or an email from a reader who followed a link you would not have followed yourself.
Step 5: Choose the post status: Publish, Pending or Draft
The post status is the fifth check, because Publish, Pending and Draft are decisions about the post, and WordPress treats each one differently.
A Draft is a post that is not finished or not submitted; only people who can edit it will see it. The Pending post status means the post has been submitted and is waiting for a decision; it appears in the pending list in the admin, and a logged-in author with the Contributor role sees it in their own post list. Publish means live, and Scheduled and Private exist for posts that go out later or stay internal.
Use the statuses like this: publish when the post passed steps 1 to 4 and you made only small fixes yourself; send it back when the author needs to rewrite something, and say what; hold it as Pending when a claim needs a second opinion or when you want to look again with fresh eyes. Do not leave a post in Pending for weeks, because a queue nobody empties teaches authors to submit elsewhere.
In Front User Submit you set the form’s Post Status to Pending, so every post collected through that form waits for you instead of appearing on the site the moment it is submitted; the post submit settings cover the status, the redirect after submission and the success message. Use a form that publishes on submit only for authors you already trust.
How to tell it worked: every post in the pending list has a reason to be there, and none has been sitting there since before your last review session.
Step 6: Notify the author and record the decision
Notifying the author and recording the decision is the last step, because an author who hears nothing assumes the worst and stops submitting.
Send one short email per post. Say what you decided, why in a sentence, and what happens next. An author whose post needs work should come away knowing the one change that matters, not a list of twelve. Keep three templates ready: published, needs changes, and not a fit for this site. The third is worth writing carefully, because a clear no costs you nothing and a vague one costs you your reputation with contributors.
Record the decision where the next editor will find it. The status is already a record, but add who reviewed the post, when, and what was asked for. If your site pays for posts, record the payment at the point where the post is accepted rather than where it is submitted.
Front User Submit sends the admin an email when a post is submitted, and the author an email when their post is submitted, published or trashed, with placeholders such as [post_title] and [post_link]; the email notification settings are set per form, so the guest form and the member form can send different messages. Guest posts have no author account, so no author email is sent for them, and you reply to those yourself.
How to tell it worked: the author’s next submission arrives, and it needs fewer fixes than the last one did.
FAQ
Should a submission go to Pending or Draft when it needs changes?
Send it back as a Draft if the author still has work to do, and keep it as Pending if you are the one who has to decide. A Draft tells the author the post is theirs to finish; Pending tells them it is with you. Mixing the two is the most common way authors lose track of what is expected of them.
What WordPress role should submitting members have?
Give members who submit posts the Contributor role. Contributors can write and submit posts for review but cannot publish them, so the role enforces your workflow even when the checklist does not. The Author role can publish its own posts, which is fine only for people you would publish without reading, and Subscribers cannot create posts in wp-admin at all.
Can I automate moderation and stop reading every submission?
You can automate the first pass, not the decision. A captcha keeps bots out of the form, and content checks can flag posts that look like spam or break your rules, but anything that carries your site’s name still needs a person to approve it. Automate what filters out the obvious, then spend your reading time on what is left.