Guest posting with or without a user account
By Aleksan Aharonyan ·
Guest posting works with or without a user account, and the decision comes down to whether your writers come back. Without an account, a visitor fills in a public form and you review the result: the barrier is as low as it gets, and every submission arrives from someone you cannot identify beyond the email they typed. With a WordPress account, each writer gets the Contributor role, logs in, submits, and can edit their own work afterwards while a real user profile stays attached to the post.
Key takeaways
- Guest posting without an account removes the login step, but you take on all the identity checking and every correction goes through you.
- Give guest writers the Contributor role rather than Author, and set the form’s post status to Pending: a Contributor cannot publish from wp-admin, and the form setting covers front-end submissions.
- Accounts pay off for repeat contributors and anyone who needs to edit after submitting; open forms pay off for one-off pitches, contests and community submissions.
- Decide per form, not per site, so a news blog can run an account form for columnists and a public form for first-time contributors.
What actually changes when a guest post has no user account
Without an account, the submitted post has no WordPress user behind it: no profile, no real byline, and no way for the writer to log in later and change the text. The post itself, with its title, body, categories and featured image, is stored exactly as it would be otherwise.
Three things follow from that.
The first is identity. With an account, WordPress knows who wrote the post. Without one, the byline is whatever your site puts there, and the only contact detail you have is what the form collected. Ask for a name and an email address in the form itself, even when the person does not need an account, so you have someone to reply to when you want a revision or a bio.
The second is control. A logged-in writer can be trusted with an edit screen because you can see who they are and remove their access if it goes wrong. An anonymous submitter cannot, so every revision passes through you.
The third is email. WordPress sends nothing to someone who has no account, and a plugin cannot email an account that does not exist. Notifications to the writer are a feature of the account route, not the anonymous one.
Option 1: guests submit without registering
A guest form is a page with a submission form on it, open to anyone who visits. In Front User Submit, a free plugin for frontend post submission and guest posting forms, this is one setting per form: turn on Enable Guest Post and the form accepts posts from visitors who are not logged in. The setting is Pro, and the guest posting settings cover it together with the message (or, with Pro, the login form) you can show instead to logged-out visitors.
When it wins. Contributors who arrive once. Someone who found your site through a search, answered a call for pitches, or wants to send a single article does not want to create an account first. A registration form is one more thing to complete before a stranger can send you work, and some of them will not finish it.
What it costs. You do the checking. Spam defense has to come from the form and the queue: set the post status to Pending so nothing publishes on submit, and add hCaptcha or reCAPTCHA v2 (both Pro) if the form is public and indexed. You will also handle more email, because a correction means the writer writes to you and waits.
What you get back. The lowest barrier you can offer and a form you can drop on any page, including a landing page for one specific call for posts.
Option 2: guest authors get a Contributor account
A Contributor account is a WordPress user with the Contributor role. A Contributor can create and edit their own posts but cannot publish them, so in wp-admin their work always waits in the Pending queue. A front-end form saves new posts with its own post status, so set that to Pending as well.
When it wins. Writers who come back. A columnist, a club member, or a business owner who updates the same post every season benefits from logging in, and you benefit from knowing exactly who they are. An account also gives them somewhere to track their own work, which is the difference between “I sent something and never heard back” and a submission they can see. The free user dashboard shortcode [fe_fs_user_admin] lists a writer’s Publish, Pending and Draft posts with edit and delete icons, and the plugin creates that page on activation.
What it costs. Registration friction and account admin. Front User Submit’s registration form gives new users the site’s default role and, since version 5.2.5, emails them a link to set their password, the same email the WordPress registration page sends. Make sure your site’s mail actually arrives, and keep the WordPress “Lost your password?” page linked for anyone who misses it. If you want every registrant to become a Contributor, WordPress’s new user default role setting decides that. If you would rather approve people first, leave the default role alone and change it after a first accepted submission.
One practical snag: WordPress does not let Contributors upload files to the Media Library by default, so test the featured image step with a real Contributor account before you announce the form. Even with the role in place, set the form’s post status to Pending as well, because a front-end form saves new posts with the form’s status whatever the writer’s role.
Comparing the two
| What changes | No account | Contributor account |
|---|---|---|
| Who can submit | Anyone who reaches the page | Registered users only |
| Where the post waits | Pending, if you set it | Pending, if you set it; the role also blocks publishing in wp-admin |
| Editing after submit | You edit for them | They edit from the front-end dashboard |
| Byline and author archive | No user profile behind the post | Real author, real archive page |
| Email to the writer | None from WordPress or the form | The form can notify on submit, publish or trash |
| Repeat contributors | Recognized by the email they typed | Recognized by their account |
Moderation. Accounts do more of the work for you, because the role blocks publishing from wp-admin and you can see a submission history per user. Without accounts, the whole weight sits on the post status, a captcha field and your own review. If your volume is high, the account route saves time you would otherwise spend deciding whether a stranger is serious.
Credit. Accounts give a real byline and a working author archive, which matters if you promise contributors a profile or a backlink. Anonymous posts are credited in the text, not in WordPress.
Email. With an account, the form can email the writer when a post is submitted, published or trashed, so you are not the only channel of communication. Guest posts submitted without an account send no author email at all, because there is no author account to send to.
Repeat contributors. A writer with an account can come back, edit a draft, and see what happened to their last post. A writer without one has to introduce themselves again every time. If the same three people send you an article every month, give them accounts.
Which option fits which kind of site
A guest-post blog
Run two forms if the blog takes both. One public form, no account, post status Pending, plus a captcha field, handles pitches and one-off articles. A second form for columnists who have already published with you can require login and let them edit their own drafts. Many editorial sites end up here because the arrival of a new writer and the retention of a regular one are different problems.
A community site or club news site
Give people accounts. Members come back to post meeting notes, match reports and announcements, and they will want to fix a typo the next morning. The front-end dashboard does more for them than any thank-you page, and a Pending form keeps the queue in your hands.
A directory or listings site
Accounts, if the same owner updates their entry more than once, because the account is the only lasting link between the business and the post. Without it you are matching submissions by memory and email address. Note that Front User Submit handles post submission rather than directory records; if your listings live in a dedicated directory plugin, that plugin’s own submission flow decides this question for you.
Setting either one up, step by step
- Build one form per route. Add a Post Title field, a content editor (TinyMCE, EditorJS, Markdown or a plain textarea, all free), taxonomy fields for categories or tags, and a Featured Image field. Save the form and place it with
[fe_form id="123"]or the Front Editor block. - Set the post status to Pending. This is the single most important setting for either route: you set the form’s Post Status to Pending, so every submission waits for you whether or not the writer has an account. The post submit settings also cover the button text, redirect and success message.
- Choose where the writer lands. Do not redirect to the new post when it is Pending, because the visitor cannot see it. Keep them on the page with a thank-you message, or send them to a short page explaining what happens next.
- Turn on notifications. Email the admin on every submission, and for the account route also email the author on submission, publication and trashing.
- For the no-account route, enable guest posting. Enable Guest Post is a Pro setting; the plans show what Pro includes. Add hCaptcha or reCAPTCHA v2 while you are there, since a public form with no login is the one bots find first.
- For the account route, decide how people get the Contributor role. Either set the new user default role in WordPress, or keep the default and promote writers by hand after a first accepted post. Do not hand out Author or Editor to people you have not worked with.
- Set the edit time lock. If writers can edit their own posts, the time lock stops changes a set number of hours after the post was created. It only applies to the account route, since anonymous writers have nothing to log in to.
How to check it worked. Open the form in a private window while logged out: on the guest route it should accept a submission, and the post should appear under Pending. On the account route the same window should show your restricted message (or the login form, with Pro). Then log in as a test Contributor, submit a post, confirm it appears in the dashboard as Pending and that the edit screen opens, and try to publish it from wp-admin. It should not be possible.
FAQ
Can a guest author edit their post after it is published without an account?
No. Editing from the front end requires a logged-in user, so a writer with no account has to ask you for changes. If revisions are likely, that is a strong argument for giving the writer a Contributor account before the first post goes live.
Should guest authors be Authors or Contributors?
Contributors. The Contributor role can create and edit their own posts but cannot publish them, so their work waits in Pending until you approve it. The Author role can publish without review, which means one careless or malicious submission goes live immediately.
What stops spam when guests submit without an account?
Two things working together: a captcha field on the form and the Pending post status, so nothing appears on the site before you read it. The captcha (hCaptcha or reCAPTCHA v2) keeps automated submissions out of your queue in the first place, and in Front User Submit it needs Pro, like guest posting itself.