Skip to content
Front User Submit
Menu

How to Sell Job Postings on WordPress: A Playbook

By Aleksan Aharonyan · · Updated

You sell job postings on WordPress by putting a WooCommerce product between the employer’s form and the published listing: the employer submits the job, pays at checkout, and the listing only goes live when the order is paid. That chain has four parts, a job post type, an employer submission form, a product the form is linked to, and a post status that changes on payment. Build them in that order and a listing can travel from checkout to published without you touching it.

Key takeaways

  • Give job listings their own post type before you build the form, because the archive template, the form fields and the employer dashboard all follow from it.
  • Link the submission form to a WooCommerce product so the post is saved as a draft and only takes the form’s post status when the order is Processing or Completed.
  • Set the form’s post status to Pending while employers are new, and move to Publish once you trust them: payment filters out spam, review filters out poor quality.
  • Give employers a front-end dashboard so they can see and edit their own listings, and decide up front what “closed” means.

What a paid job board needs before you build anything

A paid job board needs six things decided before any form is built: where a job is stored, who can submit one, which fields a listing carries, which product it is tied to, what status it holds at each stage, and who can change it after it goes live. Each decision constrains the next one, so changing your mind later usually means rebuilding rather than adjusting.

  • Storage. A job is not a blog post. It needs its own post type so the single template can show salary, location and closing date in a fixed place, and so the archive can be filtered by category and location without touching the blog.
  • Submitters. Employers can have accounts (they register on the site, then submit) or not (guest posting). Accounts are what make editing, renewing and closing possible later.
  • Fields. Job title, company, location, salary, description, category, closing date. Decide which are required before you build, because required fields are your first spam filter.
  • Product. One WooCommerce product per listing type or tier.
  • Status. Draft while unpaid, Pending or Publish once paid.
  • Editing. Who can edit, for how long, and what “closed” means.

Write those down. The rest of this playbook is the build.

Create the job post type and the employer submission form

A job listing belongs in its own post type, registered with job as the slug, so WordPress gives you a job archive at /jobs/ and a single job template your theme can style. Custom post types are a Pro feature of Front User Submit, so this is the first point where the plan decision matters: on Free, listings have to use one of WordPress’s built-in post types, and a category is what marks them as jobs.

Front User Submit, a free plugin for frontend post submission and guest posting forms, builds the employer-facing form with a drag-and-drop builder: you add fields in the order you want them, set which are required, and place the form on a page with a shortcode or the Front Editor block.

A workable field list for a job form:

  • Post Title for the job title, as a single line.
  • Text for the company name, required.
  • Text for the location, or the Google Map field if address search and a map on the listing matter to you.
  • Number or a Select field for the salary, depending on whether you want a free figure or fixed bands.
  • Date for the closing date, so you know when to take the listing down.
  • Taxonomy for the job category, restricted to your own list so employers do not invent categories.
  • EditorJS or TinyMCE for the description, with the toolbar and media buttons you are willing to allow.

The field types beyond the free set are Pro, and the business listing form checklist walks through which ones this kind of form actually needs.

Test the form as a logged-out visitor before you go further. You want to see what an employer sees, including the restricted message if you have not opened submission to people without accounts.

Connect the form to a WooCommerce product

Paid submissions run through WooCommerce: you create a product, link a form to it, and the listing is only published after the order is paid. In Front User Submit this is a Pro feature, and the payments settings cover the product link and what happens to the post at each order status.

Order of work:

  1. Create the product in WooCommerce. A virtual product with no shipping, priced at what one listing costs. Give it a name an employer recognises at checkout (“Single job listing, 30 days”), because that is what shows on the order.
  2. Link the form to the product. In the form’s payment settings, choose the product. One form, one product.
  3. Submit a test listing and pay. Use a payment method in test mode. Check that the post exists as a draft before payment and that it changes status when the order reaches Processing or Completed.
  4. Check the emails. The admin notification for a new submission and the author notification should both arrive. They use the normal WordPress mail function, so if nothing arrives, the site’s mail setup is the problem, not the form.

That draft-to-paid transition is the point of the whole setup. Before payment the employer has a draft nobody can see; after payment the post gets whatever status the form is set to. If the order is abandoned, the draft stays a draft, and you can clear those out on a schedule.

Pro is a paid plan. Professional, the entry plan, is $9.99 per month or $95.88 per year for one site, with a 3-day free trial, and the plans page lists the rest. If you only wanted a free board, the guide to paid post submissions with WooCommerce covers the smaller version of this pattern.

Decide the price: per post, bundles or featured listings

Set the price from your market, not from a formula: what a local employer already pays for a job ad elsewhere is the number you are competing with, and the work you put into review and editing is what justifies sitting above the cheapest option. The plugin does not decide any of this. It charges per submission, through the product linked to the form.

Three structures that fit without extra machinery:

  • One price per listing. One form, one product, one status. This is the fastest thing to run and the easiest to explain on the page. Most new boards should start here and add tiers only when employers ask.
  • Tiers. Standard, plus a tier with a logo field or a longer description. Build a second form for the second tier, linked to its own product, with the extra fields the price pays for. Two forms that differ only in price will confuse employers, so make the difference visible in the fields.
  • Featured listings. Sell a higher-priced product whose form adds a default term in the job category taxonomy, for example “Featured”. The theme can then style that term differently in the archive, and no extra plugin is needed to mark the listing.

Bundles and recurring billing are a different problem. Front User Submit charges for one submission per order, so if you want to sell five listings up front or bill employers monthly, the credit or subscription layer has to live in WooCommerce and sit above the form. Decide whether you need that before you advertise it, because retrofitting it is more work than choosing it now.

What happens to a listing between checkout and publish

Between checkout and publish a listing holds one of three states: Draft when it is unpaid or saved unfinished, Pending when it is paid but waiting for you, and Publish when it is live. The form’s post status setting decides what the paid version becomes, and the post submit settings explain that alongside the redirect and the success message.

Two settings do most of the work here:

  • Post status. Start with Pending for every employer. Move to Publish only for employers you have dealt with before, or when the moderation check flags nothing. AI moderation is a Pro feature and holds flagged posts as Pending or Draft; if the AI provider is down, the post saves as usual rather than failing.
  • Redirect after submit. Opening the new post is the obvious choice and the wrong one while listings are Pending, since the employer lands on a page the public cannot see yet. Redirect to the employer dashboard or a thank-you page that explains the review instead.

Also decide what an unpaid draft is worth. WordPress keeps it, the employer may come back to it, and nobody else can see it. You can let those sit, since they cost you nothing until they are paid for.

Let employers edit, renew and close their own listings

Employers manage their listings from a front-end dashboard rather than wp-admin: the [fe_fs_user_admin] shortcode renders a page with Publish, Pending and Draft tabs, plus edit and delete icons for each post. Front User Submit creates that page on activation, and the user dashboard settings explain the tabs and what each role can do.

Editing happens in the same form the employer submitted with, so the fields stay consistent. The form’s edit post settings include an optional time lock that stops edits a number of hours after the post was created. That is useful for a closing date that should not move, and awkward for an employer who needs to fix a typo two weeks later. Pick one and say which on the confirmation page; letting users edit their posts from the frontend goes deeper on the trade-off.

Deleting is where role settings bite. New users get the site’s default role, usually Subscriber, and Subscribers cannot delete posts. Contributors can delete their own unpublished posts, Authors their own posts, but Authors can also publish, which you should not hand to anyone who pays. The practical answers are to add a capability with a role-editing plugin so employers can delete their own published listings without gaining publish rights, or to treat “closed” as something you manage and let employers set a closing date instead.

Renewal is the same submission again: the employer fills the form, pays, and the new listing takes the form’s status. Keep the old one as an archive rather than editing it back to life, so the board’s history stays honest.

Keep junk and spam listings out before they go live

Spam on a paid board is rare but not gone, and the defences stack in a useful order: a required account, required fields, a captcha, payment, then review. Each one removes a different kind of bad listing, and none of them alone is enough.

  • Require an account. Registration is a small barrier and it gives you an email address and a person to ban. Front User Submit ships login and registration forms, so employers never need to see wp-admin.
  • Require the fields that matter. A post with no company name and no closing date is not a job ad, and a required field is easier to enforce than a rule you police later.
  • Add a captcha. Cloudflare Turnstile, hCaptcha and reCAPTCHA v2 fields are free and sit next to the submit button, once per form.
  • Keep Pending on. Payment filters out most automated junk, but it does not filter out a badly written ad or an employer who ignores your categories. Pending is where you catch those, and it costs you a minute per listing.
  • Never hand out a role that can publish. Employers should be able to submit and edit their own listings and nothing else. If a role editor is part of your setup, check exactly what it adds before you assign it.

When the board grows past the point where you read every listing, review is the first thing people automate. Do it with the same care you would give a comment queue: a rule you can state, and a person who can overrule it.

FAQ

Do I need WooCommerce to charge for job listings?

Yes. In Front User Submit, paid submissions are built on WooCommerce: you create a product, link a form to it, and the listing is published after the order is paid. That keeps payment methods, taxes and receipts in WooCommerce, where they are already handled, instead of inside the submission form.

Can employers post a job without creating an account?

Guest posting is free and lets visitors submit without registering, but guest posts have no author account, so the employer cannot come back later to edit, renew or close the listing, and no author emails are sent for them. For a paid board that is usually the wrong trade. Requiring an account costs the employer a minute and gives them a dashboard.

What happens if someone pays but the listing should not go live?

If the form’s post status is Pending, the paid listing waits for you, and you can hold or reject it before anyone sees it. Refunds and order notes are handled in WooCommerce, outside the submission form, so the employer’s order record stays the source of truth for what they paid.