A job board has to serve two very different people at the same time: employers want to publish openings quickly, while candidates need listings they can trust. If moderation, expiry, application links, or location data are weak, the board loses value for both sides.
This guide focuses on building a structured, maintainable WordPress job board rather than a large pile of job posts. We will define the job data, employer workflow, moderation rules, application path, and expiry handling before adding advanced filters or monetization.
TL;DR
A job board is a structured listings workflow. Define job fields, employer submission, account rules, moderation, expiry, applications, and duplicate handling before adding filters. WP Job Manager is a common WordPress foundation and provides a front-end job submission form through its job-board workflow.
Who this build fits and what the first version needs
This build fits niche industry job boards, local hiring sites, association career centers, company recruiting portals, and curated opportunity directories. A first version needs structured job fields, search/browse, a job detail page, employer submission or admin posting, moderation, expiry, application method, and a way to report bad or filled jobs.
Job boards look simple until employers, applicants, expired roles, spam, remote locations, and duplicate listings enter the system. WP Job Manager provides the job-listing data model and front-end submission workflow; its documentation explains that the job submission form can be placed on a page and behaves differently depending on account requirements.
What to know before you start
- Define the job fields before building filters: title, employer, location, remote status, employment type, salary where appropriate, category, deadline, and application method.
- Decide whether employers need accounts, whether accounts are created during submission, and whether every employer is manually approved.
- Choose how applications happen: external URL, email, or an on-site application system.
- Set expiry rules and decide whether employers can renew or edit listings.
- Write prohibited listing rules, scam review criteria, and a process for reporting suspicious jobs.
Recommended plugin stack
Plugin choices for this guide: Job-board plugins differ in employer dashboards, submissions, monetization, and search. Compare them in our best WordPress job board plugins roundup. For this walkthrough, we use WP Job Manager as the job-board engine. If the catalog becomes large, compare filtering tools before adding one; this guide uses FacetWP only when advanced filtering is actually needed. For employer or applicant forms, compare the best WordPress form builders; this guide uses Bit Form only where the job-board workflow needs an extra form. For email delivery, compare the best SMTP plugins. For SEO, compare the best SEO plugins; this guide uses Rank Math.
| Role | Choice | Why it fits | Plan / test boundary |
|---|---|---|---|
| Job engine | WP Job Manager | Provides job listing data, archives/search, detail pages, and front-end submission workflow. | Add-ons may be needed for applications, paid listings, resumes, alerts, or advanced features. |
| Filtering | Native filters or FacetWP for advanced needs | Helps users narrow a growing job catalog. | Do not add complex filtering before the field schema is stable. |
| Applications | Bit Form | A practical option when the board intentionally collects on-site applications, including structured fields and file uploads. | Skip it when every application goes to an external employer URL or email. |
| FluentSMTP | Improves employer/account/admin notification delivery. | External sender required. | |
| SEO | Rank Math SEO | Controls metadata, sitemap behavior, and structured-data settings. | Expired and duplicate jobs need intentional handling. |
How to build a job board with WordPress step by step
WP Job Manager works best when you set up the required pages first, then test one employer submission from the front end.
Step 01: Install WP Job Manager and run the setup wizard
Install and activate WP Job Manager. Run its setup wizard and create the recommended pages for job listings, job submission, and the job dashboard.
Check: The Jobs page, Submit Job page, and employer Job Dashboard page all open correctly.
Step 02: Configure job listing settings
Review the WP Job Manager settings for account requirements, listing duration, approval/moderation, categories, job types, and whether expired jobs remain visible. Choose rules before accepting employer submissions.
Check: The settings clearly define who can submit and whether a new job requires approval.
Step 03: Configure the public jobs page
Use the Jobs page created by the setup wizard or add the [jobs] shortcode to the page you want to use. Confirm search/filter controls and the listing card information are useful for job seekers.
Check: A visitor can browse and filter published jobs without logging in.
Step 04: Configure employer submission
Use the Submit Job page with the [submit_job_form] shortcode if it was not created automatically. Submit one job as a normal employer account, fill in the job and company fields, preview it, and submit it.
Check: The employer can submit without WordPress admin access and the job enters the expected status.
Step 05: Moderate and publish the test job
Go to Job Listings in WordPress admin, review the submitted job, edit anything needed, and approve/publish it according to your moderation policy.
Check: The approved job appears on the public Jobs page with the correct company, type, location, and application information.
Step 06: Configure the employer dashboard and expiry
Use the Job Dashboard page with [job_dashboard]. Log in as the employer and confirm they can see their listing, edit it if allowed, mark it filled, and understand when it expires.
Check: The employer can manage only their own jobs and can close a filled role without contacting an administrator.
Step 07: Test the complete job-seeker path
Open the job board logged out, search for the test job, open the listing, and complete the application action you configured. Then expire or mark the job filled and verify the public state changes correctly.
Check: A job seeker can discover and apply to an active job, while filled/expired jobs no longer look open.
What to know before launch
Job boards attract spam and scams because a listing can move a candidate off-site. Moderation is part of the product. If you store resumes, applications, salary expectations, or demographic information, privacy and retention rules become more important. Do not collect applicant data unless the board actually needs to process it.
Mistakes to avoid
- Using free text for every field. Location and job type filters become inconsistent.
- Leaving expired jobs looking active. This damages trust and can create search-quality problems.
- Publishing employer submissions without fraud checks. New boards are attractive spam targets.
- Duplicating the same job each time it is renewed. Update or intentionally repost with canonical/expiry strategy.
- Collecting resumes when applications are external. Avoid storing applicant data you do not need.
Best practices for a stronger site
- Start with one niche where you can judge listing quality.
- Require enough company information for applicants to assess legitimacy.
- Use consistent job types and normalized locations.
- Let users report a job and make the report route visible on the listing.
- Review expired, duplicate, broken-application, and suspicious listings on a schedule.
Launch checklist
- Job fields and allowed values are documented.
- Employer account/submission states work as intended.
- New listing moderation and rejection flow is defined.
- Search and filters work with real sample data.
- Application links or forms work on mobile.
- Expired/filled jobs show the correct public state.
- Spam/scam reporting is available.
- Metadata, canonicals, sitemap inclusion, and JobPosting data are reviewed.
Operational ownership and maintenance
A job board needs ongoing moderation and expiry cleanup. Assign someone to review new employers, suspicious listings, broken application links, duplicate jobs, and reports from candidates. Build a routine that checks old listings before they quietly become stale. If employers can edit their own jobs, log or review meaningful changes to company identity, application destination, compensation, and location because those edits can change the risk profile of an already approved listing.
How to confirm the first version works
Test the board as an employer, applicant, moderator, and logged-out visitor. Submit a job, review it, publish it, search and filter for it, open the application path, mark it filled or let it expire, and confirm the public state changes. Then submit a duplicate or suspicious listing and verify the moderation process. If accounts are optional, test both logged-in and logged-out submission behavior because WP Job Manager can behave differently depending on account settings.
Conclusion
A trustworthy job board is built around clean data and moderation. Get fields, employer identity, expiry, and application handling right first. Advanced filters and monetization can come after the listings are reliable.
FAQs
Is WP Job Manager free?
The core WP Job Manager plugin provides the basic job-board workflow. Additional capabilities such as applications, paid listings, resumes, or alerts may involve extensions.
Should employers create accounts?
Accounts make editing and managing listings easier, but they add onboarding friction. Choose based on whether employers need self-service and how much moderation you require.
What should happen to expired job posts?
Stop presenting them as open. You can keep a useful expired page, redirect when appropriate, or remove it depending on content value and replacement options. Keep structured data and sitemaps aligned with the real status.
Should a job board collect resumes?
Only if the board is intentionally handling applications and can protect, retain, and delete applicant data responsibly. External-application boards often do not need to store resumes at all.
