Skip to content
Front User Submit
Menu

How to Accept Guest Posts on WordPress: A Playbook

By Aleksan Aharonyan ·

You accept guest posts on WordPress by collecting submissions through a form on your own site, holding every one in the Pending post status, and publishing only after you have read and edited it yourself. The writer never needs a wp-admin account, and the finished post carries their name. What follows is the order to build that pipeline in, from the guidelines page to the reply you send on publication day.

Key takeaways

  • Write the guest post guidelines first, then turn each rule into a form field or a form setting, because a rule that lives only in a paragraph gets ignored.
  • Set the form’s post status to Pending so no guest post can reach your front page without your edit and approval.
  • Decide whether guests register on your site or submit with no account at all; the no-account route means no dashboard, no author record, and more spam to filter.
  • Credit the writer with a byline and reply with the live URL, since that reply is what turns one guest post into a regular contributor.

What a guest posting pipeline needs before you accept a single post

A guest posting pipeline is four stages in a fixed order: published guidelines, a submission form that collects the post and the writer’s details, a review step that no submission skips, and a byline plus a reply after publishing. Build them in that order. A form opened before the guidelines exist collects work you then have to reject by email, one writer at a time.

Settle these decisions before the page goes live:

  • The topics you want and the ones you don’t. Name both. “We publish practical WordPress and small-business marketing posts, not crypto or gambling content” saves everyone a wasted draft.
  • Whether you pay. If you don’t, say so on the page. Silence about money attracts pitches you will decline.
  • Who reviews, and how fast. One person, with a turnaround you can actually keep. Two reviewers with no owner means submissions sit in Pending for weeks.
  • Your editing rights. State plainly that you edit for style, length and links, and that you may decline a submission.
  • Rights and originality. The writer confirms the piece is theirs, has not been published anywhere else, and that you may publish and keep it online. For images, they own them or hold a license.
  • Where guest posts land. A category of their own, so readers can find them and you can count them later.

WordPress already provides part of this: the Pending post status, user roles, and accounts. The Pending status only helps if submissions arrive as Pending rather than Published, and that is a setting in your form, not a WordPress default.

Write guest post guidelines your form can actually enforce

Guest post guidelines change what people send only when the form backs them up; a rule that lives in one paragraph and nowhere else is a rule you enforce one email at a time. Write the page, then walk down it rule by rule and ask whether the form can ask for this, limit this, or refuse it.

Cover these on the page, in this order:

  • Subject and audience. Name the categories you accept, and link two posts that show the style you want.
  • Length. Pick a range and state it, with a line about whether you will edit a piece that runs long.
  • Structure. Subheadings, a short intro, no more than a stated number of outbound links, no affiliate links.
  • Images. Who supplies the featured image, what size it should be, and who is responsible for rights.
  • Originality. Not published elsewhere, including the writer’s own site or newsletter.
  • Disclosure. If they drafted with AI, ask them to say so, and decide in advance what you will accept.
  • Editing and decline. What you change, and that you can say no.

Then map each rule to a control. A rule about topics becomes a category field that only offers the categories guests may use, with your news and announcements terms excluded. A rule about images becomes a required featured image upload. A rule about link counts has no field that can enforce it, so it stays a review job and the guidelines need to say it is checked. This mapping is the step that is easy to skip, and skipping it fills your inbox with submissions that break the rules you wrote down.

Build the guest post submission form: fields, word count, images, status

The submission form is your whole intake process, so build it to collect a complete post that arrives unpublished. Order the fields the way a writer thinks: title, category, content, image, then their own details.

Title and category. A Post Title field plus a taxonomy field limited to the sections you accept guests in. Exclude the terms you don’t want filled by outsiders, so nothing lands in the wrong place while you are asleep.

The content editor. Choose one editor per form and name it in the guidelines. A block editor gives you structured output, though pasting from a word processor can bring formatting you clean up later. Markdown suits technical writers and converts to HTML when the post is saved. The classic WordPress visual editor is the most familiar. A plain textarea gives you the cleanest input and the most formatting work. None of these is wrong; the mistake is leaving the choice unstated and getting three of them in one week.

The featured image. Require it if you want images at all, and put the rights sentence in the guidelines. A simple uploader covers most blogs; the WordPress Media Library uploader is a Pro feature if you want writers picking from existing files.

Word count. Do not count on the content editor to enforce a length. Put the range in the guidelines, and if you add a number field (Pro) where the writer states the count, treat it only as a signal you check at review, since a stated number is self-reported.

Post status. This is the setting that matters more than any other. In Front User Submit, a free plugin for frontend post submission and guest posting forms, you set the form’s Post Status to Pending in the post submit settings, so every submitted post waits for you instead of going live on submit.

Redirect and message. Send the writer to a thank-you page that repeats what happens next: you review, you may edit, you reply either way, and here is roughly when.

Guests without wp-admin accounts: account or no account

Guests should never get a wp-admin login; the real choice is between a front-end account on your site and no account at all. Both routes keep the writer out of the dashboard, and both can end in Pending.

Route A: a front-end account. The writer registers through a form on your site, gets the site’s default role, and submits from the front end. Set that default role to the lowest one that can submit, which is usually Subscriber, so a new account can send a post but not publish one. The advantage is a user record, an email address on file, and a front-end dashboard where the writer can fix a draft you send back. The cost is friction, and you have to check what email a new writer receives when they register, then tell them where to set a password; WordPress’s “Lost your password?” page is the usual answer.

Route B: no account at all. Lower friction and no user records to manage. In Front User Submit, guest posting without an account is a Pro feature you enable per form, and the guest posting settings list every option. Pro is the paid tier (plans), with the Professional plan at $9.99 per month. The trade-offs are real: with no account there is no dashboard for the writer to edit from, and notification emails that go to an author have no address to reach, so collect a contact address and reply yourself.

The no-account route also means anonymous submissions. Keep Pending on, and add a captcha field; the plugin’s reCAPTCHA v2 and hCaptcha fields are Pro.

Review the queue: edit, approve or reject a submission

Every guest post sits in Pending until you open it, edit it, and change its status, and that queue is where your blog’s quality is decided. Give the queue a fixed slot in your week rather than dipping into it at random.

  1. Check against the guidelines before you read for pleasure. Topic, length, link count, originality, image rights. For originality, paste one distinctive sentence into a search engine.
  2. Read it as a reader would. Does the opening answer the title? Is anything factually wrong, or lifted from a press release?
  3. Edit in the post editor. Set the featured image and alt text, fix the heading structure, add two or three internal links to your own posts, and set the category.
  4. Decide in one pass. Publish, hold with notes, or decline. If you want changes, leave it Pending and email the writer with a short list. If you decline, give two lines of reason; it takes a minute and writers talk to each other.
  5. Tell the writer. When you publish, Front User Submit can email the author that their post is live and again if it is trashed, set up per form in the notification settings, so nobody has to refresh the site to find out.

Credit the guest author and keep them coming back

Credit is the byline on the published post plus a reply that says when it went live and what you changed. Both are small, and both decide whether that writer sends a second post.

  • The byline. With an account, the post author is that account and the display name is the byline. With no account, add the name at the top of the post or in a custom field (Pro) you print under the title, and use the same format every time so readers can tell a guest post from staff writing.
  • A bio line. One or two sentences, their site, and one social handle if you allow links.
  • What you changed. Say it briefly in the reply. Writers who learn that you edit for structure rather than rewriting them come back.
  • The link and one share. Send the URL on publication day, and share the post once from your own account.
  • An invitation with a shape. Ask for a pitch next time, not a finished draft: two or three sentences and a link to something they have written.
  • A list. Keep a short list of writers you would take again, with their topics and the last date you published them. Sorting by who has delivered beats starting from scratch.
  • Disclosure. If money changed hands in either direction, say so in the post.

A launch checklist for opening submissions

Open submissions only when everything on this list is true, because the first few submissions set what people believe you accept.

Before you announce

  • The guidelines page is live and linked from the form.
  • The form has been tested from a logged-out browser and from a Subscriber account.
  • Post status is Pending on the form, confirmed by submitting a test post and checking the posts list.
  • The admin notification email arrives at an address you read, and not in spam. WordPress sends mail through the site’s own mail function, so test it rather than assume.
  • New accounts get the lowest role that can submit. Nobody outside your team gets Author or Editor.
  • Registration and front-end dashboard pages exist, and you know what a new writer receives when they sign up.
  • Your captcha or other spam gate is active if visitors can submit without an account.

In the first month

  • A named reviewer and a fixed day for the queue.
  • Two reply templates ready: accepted with edits, and declined with a reason.
  • One byline format and one bio format, used every time.

FAQ

Do guest authors need a WordPress account?

Not necessarily. With a form that supports guest posting (Pro in Front User Submit), you can collect posts from visitors with no account at all, or have them register on the front end and never see wp-admin. The account route gives the writer a way to log in and fix a draft you send back; the no-account route is lower friction but needs a captcha and a contact field, because there is no user record to email.

How do I stop spam guest posts?

Keep the form’s post status on Pending so nothing publishes before a person reads it, and add a captcha such as reCAPTCHA v2 or hCaptcha if you accept submissions from visitors without accounts. Then watch patterns rather than individual posts: link-stuffed bios, off-topic text, and rewrites of press releases are the usual signs. A specific guidelines page written by a human also filters out a lot of automated submissions.

Can a guest writer edit their post after it is published?

Yes, if they registered. A front-end dashboard lets users edit their own posts in the same form, and an optional time lock can stop edits a set number of hours after the post was created. If they submitted without an account, they cannot edit, so collect changes by email and make them yourself.