Skip to content
Front User Submit
Menu

WordPress Post Status: Publish, Pending Review or Draft

By Aleksan Aharonyan ·

A post submitted by someone you do not know should be saved as Pending review, not published. Use Publish when submissions come from people you already trust, and give logged-in members a Draft option when they need more than one sitting to finish. The choice decides where the work sits: with you before the post goes public, or with you after it already has.

Key takeaways

  • Pending review is the safe default for unknown authors: the post is stored, the author is told it went in, and nothing is public until someone with publishing rights approves it.
  • Publishing on submit is only a good trade when you would publish that person’s work unread, because moderation becomes cleanup after the fact.
  • A Draft suits a logged-in author who is not finished, and it needs a place to return to, so it does not work for visitors who submit without an account.
  • Set the status per form rather than per site, because a members’ news form and a guest post form usually want different answers.

What post status should a submitted post get?

Post status is a WordPress field on every post, and it decides who can see the post and what happens to it next. Publish makes it public immediately, Pending review stores it for someone with publishing rights to check, and Draft keeps it private to its author until the author is ready.

The status is only half of the decision, because WordPress roles do part of the work already in wp-admin. A Contributor can write and submit posts but cannot publish them, so their submissions land in Pending. An Author can publish their own posts without anyone looking. Editors and administrators can publish anyone’s. If you hand a stranger the Author role to save yourself a step, you have effectively chosen Publish for them.

Two questions sort most cases:

  1. Would you put this person’s work on the site without reading it first? If yes, Publish is reasonable.
  2. Is the person still writing? If yes, Draft. If no, Pending review.

Everything else is about how much reviewing you can realistically do.

Publish immediately: speed versus risk

Publishing immediately means the form saves the post with the Publish status, so it is live the moment the submitter finishes. The win is speed and goodwill: a member posts a notice and it is public before they close the tab.

It works when the submitter is already known to you: club members, a team of columnists, businesses whose listings you have checked, a school staff room. It also suits content where a mistake is cheap and short-lived, such as an event notice, a lost-and-found post or a classified ad.

The cost arrives later. You trade a review step for a cleanup step: reading posts on the live site, editing them in place, unpublishing the bad ones and explaining to the author why. That is more work per bad post than reviewing it before it went out, and it happens in public. It also means you need spam handling that works without you, such as a captcha field or a login requirement.

There is a quieter cost too. A Pending post is easy to improve before anyone sees it: fix the heading, add a featured image, choose a category. A published post has already been read and possibly shared, so every fix becomes a correction.

A simple check: if you find yourself unpublishing or heavily editing submissions more than rarely, that group of authors should be on Pending.

Pending review: the safe default for unknown authors

Pending review means the post is saved and counted, but not public. It sits in the posts screen until someone with publishing rights opens it and publishes, schedules or deletes it. It is the default answer for any submission from someone you cannot vouch for.

It wins whenever the post carries a byline, appears on the front page, or could embarrass you: guest posts, first-time contributors, community news, anything with a link in the body. It is also the right choice while you are still deciding whether a new writer is any good.

The cost is a queue, and a queue is a promise. Every submission needs a decision, and the author is waiting. Slow review loses contributors faster than rejection does, because silence reads as being ignored. Tell the author what happened: an automatic email when the post arrives and another when it is published covers most of it.

In Front User Submit, a free plugin for frontend post submission and guest posting forms, the Post Status is a per-form setting: set it to Pending and every post that form collects waits for you, while a different form on the same site can publish straight away. The post submit settings also cover the redirect, buttons and success message that go with that choice.

One reassurance: a post held as Pending has no public page, so nothing gets indexed and no feed picks it up while it waits. Holding a post costs you review time and nothing else.

Draft: when authors need to finish later

A Draft is a post its author has not finished. It is private to the author and to editors and administrators, it is not submitted for review, and it does not count as waiting for you.

Drafts win for logged-in members writing something long: a guide, a review, a multi-part story, a listing with photos that still need cropping. They also help when the form is long enough that people will not finish in one sitting.

The catch is that a Draft needs an author account to come back to. A visitor who submits without an account has no dashboard and no way to return, so a Save Draft button on a form open to guests leads nowhere. Drafts only make sense where the form requires login.

The other cost is drift. Drafts go stale quietly because nobody is waiting on them, so you need a way to see them and a reason to nudge the author. If you never open the drafts list, you have built a folder, not a workflow.

Front User Submit adds a Save Draft button to the form, so a logged-in member can park an unfinished post and return to it through the same form. If you use the plugin’s optional time lock, which stops front-end edits a number of hours after the post was created, set it long enough for your writers or leave it off on draft-heavy forms.

Matching the status to the form and the site

Start from the submitter, not the content type. The same article is safe to publish when a staff writer sends it and needs review when a stranger does.

Status What the author sees Your work Fits
Publish Live immediately Review after the fact, fix or remove Known members, notices, classifieds
Pending review Saved, waiting Review before it goes public Guest posts, new contributors, bylined articles
Draft Private, unfinished Nudge and coach Logged-in members writing long pieces

Guest post blog. Pending on every form, no exceptions, and Contributor rather than Author for anyone you have not worked with. When submissions land in a queue you cannot watch all day, the difference between a setup that works and one that stalls is the notification: Front User Submit sends an email to the admin whenever a form collects a post, so the queue announces itself instead of waiting to be checked.

Local directory or classified site. Publish for listings from verified businesses and Pending for free submissions from the public, at least until you know the submitter. Volume matters here: if you cannot review every listing, publishing with a captcha and a report link is more honest than a queue you never clear.

Club or school news site. Publish for a small trusted group, Pending for everyone else, and move people over after a few posts you did not have to fix.

Multi-author magazine. Pending on the way in, Contributor for new writers, and Author only for people whose next post you would publish unread.

Can you change the decision after posts start arriving?

Yes, and you probably will. The status is a setting on the form, not a rule for the whole site, so you can change it for new submissions without touching the posts already in the queue.

What does not change is history. Posts already saved as Pending stay Pending until someone publishes them, and posts already published stay public. If you switch a form from Publish to Pending expecting the backlog to sort itself out, you have only stopped adding to it.

To clear a queue, use bulk editing on the WordPress posts screen: filter to Pending, select the posts you have read, and set their status to Published in one go. Read before you select all, because bulk publishing undoes the point of the review step.

Changing direction is normal both ways. Start with Pending for a new group of authors, watch what they send, then loosen it. If spam gets through, tighten it back and add a captcha. What you should not do is keep a review step you never perform, or give a stranger a role that publishes without review just to shorten your day.

FAQ

What is the difference between Pending and Draft in WordPress?

Pending means the author has finished and the post is waiting for someone with publishing rights. Draft means the author is still working and has not submitted it. Both are invisible to visitors and both can be edited by their author; a Contributor can edit their own drafts and pending posts but cannot publish either.

Should a new writer get the Contributor or the Author role?

Start with Contributor. A Contributor can write and submit posts but cannot publish, so their work lands in Pending review and nothing goes live without you. Move someone to Author only when you would publish their next post without reading it first.

Do pending posts affect SEO?

No. A post held as Pending has no public page, so search engines cannot index it and it does not appear in feeds or sitemaps. What does affect you is time: a writer who waits too long for review usually stops submitting.