Skip to content
Front User Submit
Menu

How to Add a Frontend Post Form in Elementor

By Aleksan Aharonyan ·

Elementor can host a frontend post form, but it cannot create the post behind it. Page builders decide how a page looks; a post submission plugin decides what a filled-in form turns into, which field becomes the post title, whether the post publishes straight away and where the author lands afterwards. So a frontend post form in Elementor is two pieces of work: build the form in a submission plugin, then place its shortcode on an Elementor page.

Key takeaways

  • Build the form outside Elementor first, because the fields, the post status and the redirect are settings of the submission plugin, not of the page builder.
  • Set the post status to Pending for any form strangers can reach, so nothing goes live before you have read it.
  • Place the form with a shortcode inside Elementor’s shortcode widget, and check the result on the front end rather than relying on the editor preview.
  • Test twice: once as a logged-in user with the role you plan to give contributors, and once as a logged-out visitor.

What a frontend post form needs before you open Elementor

A frontend post form needs four things settled before design enters the picture: which fields map to the post, who is allowed to submit, what status new submissions get, and what the author sees after submitting. Elementor is not involved in any of the four. It gives you the page and the space around the form.

  • Fields. A post needs a title and content at minimum, and usually a featured image and at least one category. Every field should have a job in the finished post; extra fields become data nobody reads.
  • Who may submit. WordPress roles already decide who can publish. A Contributor can write and edit their own unpublished posts but cannot publish them. A Subscriber cannot publish either. Keep new accounts on the site’s default role and let the form, not the role, decide whether a submission goes live.
  • Post status. WordPress has a Pending status built in. A submission saved as Pending sits in the posts list with a clear label until an editor publishes it.
  • After submit. The author needs to know the submission worked, and you need to know it arrived. That means a success message or a redirect, plus an email to the site admin.

The account side is WordPress’s job too. If you collect registrations, keep a link to the WordPress “Lost your password?” page on the submit page, as a fallback for anyone whose set-password email does not arrive.

Step 1: Build the submission form

The form itself is built in the submission plugin, and Elementor is not involved yet. Open the form builder, add the fields the post needs, and order them the way a person would fill them in.

  • Post Title. A one-line input suits most posts; a textarea suits long headlines.
  • Content editor. Pick one editor per form and stick to it. A block-style editor such as EditorJS gives non-writers structure (paragraphs, headings, lists, images, embeds) without the full WordPress admin. Markdown suits technical authors. The classic WordPress editor (TinyMCE) is familiar to anyone who has used wp-admin. A plain textarea is for short posts only.
  • Featured Image. Letting authors upload an image from the form saves you chasing attachments by email later. Check the upload limit your host enforces before you announce the form.
  • Taxonomies. A category checklist or dropdown keeps new posts inside the sections you already run, which matters more than it sounds: an uncategorised post looks like an orphan on an otherwise tidy blog.

Front User Submit, a free plugin for frontend post submission and guest posting forms, builds this part with a drag-and-drop form builder: you add the Post Title field, choose an editor for the content, then drop in Featured Image and Taxonomies fields. The quick start guide walks through a first form from an empty install.

Step 2: Set the post status, redirect and success message

Three settings decide what a submission becomes: the post status, the redirect, and the message the author sees. Set all three before the form is public, because the defaults may not fit your editorial workflow.

  • Post Status. Pending is the right default for any form the public can reach: the post waits in the posts list until an editor publishes it. Publish suits a form only you or a trusted contributor uses.
  • Save Draft. Allowing the Save Draft button lets a long submission be finished later. It also creates Draft posts you will need to clear out occasionally.
  • Redirect. Staying on the page with a success message works well for a first submission. Opening the new post gives the author immediate feedback when the post publishes right away. A custom URL suits a thank-you page you have built in Elementor.
  • Success message. Say what happens next, for example that the post is waiting for review, so people do not submit twice.
  • Notifications. Turn on the admin email for each form. The author email only makes sense when an author account exists.

The post submit settings page lists every option on that screen, including comment status.

Step 3: Add the form to an Elementor page

Placing the form takes one Elementor widget. Create a page called something like “Submit a post”, edit it with Elementor, drag Elementor’s shortcode widget into a section, and paste the form shortcode with your form’s ID, for example [fe_form id="123"]. Publish the page, then open it on the front end, not in the Elementor editor, because editors render shortcodes inconsistently.

Front User Submit renders each form through that shortcode, so any page builder that can output a shortcode can hold the form. If you build the page in the WordPress block editor instead, the Front Editor block does the same job without typing anything.

Two placement decisions save trouble later:

  • Keep the site header and footer. Use a normal page template rather than a blank canvas one, unless you deliberately want a distraction-free submit page. People need a way back into the site.
  • Link it once. Put “Submit a post” in the main navigation and in the footer. A form nobody finds collects nothing.

If you run several forms, give each one its own page, because the redirect and the success message belong to the form.

Step 4: Style the form so it matches your Elementor design

A form inside a shortcode is not an Elementor widget, so Elementor’s global colors and typography do not reach inside it. What usually styles the fields is your theme, with the plugin’s own design setting sitting on top. That is why a form can look right in a preview and wrong on the live page.

  • Pick the closest built-in design first. Clean is the default and is made to look right on any theme; Simple, Modern and Minimum Style are the other free designs. “Preview on my form” shows a design on your own form before you commit.
  • Set the button color in the form. Elementor’s button styles do not apply to the submit button, so use the per-form color setting instead.
  • Use the per-form custom CSS box for spacing, input borders and label sizes the design does not cover. Keep it small: a dozen lines is easier to maintain than a stylesheet copied from a tutorial.
  • Wrap the shortcode in one container with a readable maximum width. Deep nesting adds padding you then have to fight in two places.

The form designs and display settings docs cover the designs, button colors, message placement and the custom CSS box.

Step 5: Test it as a logged-in user and as a visitor

Test the form twice, with different accounts, before you announce it. Each test checks a different half of the workflow.

The logged-in test. Create a test account with the role you plan to give contributors, so a Subscriber or a Contributor rather than an Author, which can publish its own posts. Log in, fill the form, submit, and check four things:

  • the post exists with the right status, title, content, image and categories;
  • the success message or redirect behaved as set;
  • the admin notification email arrived and its [post_title] and [post_link] variables were filled in;
  • the user dashboard page, [fe_fs_user_admin], lists the post under the correct status tab, and its edit link reopens the post in the same form.

The visitor test. Open the form in a private window. In the free version, a logged-out visitor sees the restricted message you can edit; Pro can show a login form in its place. Submissions without an account need guest posting, which is a Pro feature, and the plans page carries the current prices. Guest posts have no author account behind them, so author emails are not sent for them.

Spam is the other thing to check. Login requirement plus Pending review covers most of it. If you open the form to guests, Pro adds reCAPTCHA v2 and hCaptcha fields to the form.

FAQ

Do I need Elementor Pro for a frontend post form?

No. Elementor’s free version includes the shortcode widget, which is all the page builder has to do here. The submission workflow lives in the post submission plugin, and the shortcode renders the same way in Elementor free and Pro.

Can visitors submit posts without an account?

Only if the submission plugin supports guest posting; in Front User Submit it is a Pro feature. Guest submissions have no author account behind them, so the author cannot log back in to edit the post, and author notification emails have nowhere to go. For an open call for posts that is usually acceptable; for a members’ blog, require login instead.

Where do submissions go before they are published?

Into the normal WordPress posts list with the Pending status, if you set the form that way. Pending posts are not visible to visitors until an editor publishes them, so a review step costs you nothing except the time it takes to read the queue. Leave the admin notification email on so you know when something is waiting.