Elementor
Build your job board where you build everything else
If your site is built in Elementor, your job board should be too. W3Bullhorn adds widgets for listings, job pages, search and applications, and dynamic tags for the Bullhorn fields behind them, so a designer lays out job pages the same way they lay out any other page.
Nothing is registered on a site that does not run Elementor.
What it is
A designer’s job board, not a developer’s
Most Bullhorn job boards give an Elementor site two bad options: a shortcode that ignores your design system, or a developer every time the listing needs changing. Neither is how the rest of the site gets built.
The widgets put job data inside Elementor’s own editor, with Elementor’s own controls. The dynamic tags make a Bullhorn field available anywhere a tag can go, so a heading, a button or a styled block can show the job’s title, location or salary without anyone writing a template.
What you get
Four widgets and five dynamic tags
-
Job List
Your open roles as a listing, with paging that counts correctly.
-
Job Detail
The role itself: description and the fields you have chosen to show.
-
Job Search and Filters
Keyword and location search that stays on the page it sits on.
-
Job Application
The application form, delivering into Bullhorn like any other.
Dynamic tags
Bullhorn fields anywhere a tag can go
Five tags make job data available to Elementor’s own widgets: job title, job field, job custom field, job description and job link. Put the job’s location in a styled heading, the salary in a badge, or the apply link on a button you designed — without a template override and without a developer.
- Job title, field, custom field, description and link
- Your own Bullhorn custom fields, where you have enabled them
- Works with Elementor’s own styling controls
- Job pages designed as Theme Builder templates
Why this is safe to hand a designer
One data path, and a field a designer cannot accidentally publish
A builder integration is where plugins usually leak. This one is built so that it cannot. The widgets and tags do not read the database themselves — they ask the same part of the plugin your job pages already use, so there is no second route to drift out of step. And a field is only offered to a designer if you have enabled it: the tag picker lists nothing else, and the choice is checked again when the page renders, so a field nobody enabled prints nothing even if its name is typed in by hand.
- Widgets and tags read through the plugin, never the database directly
- Only the fields you enable are offered, and the check is repeated at render
- Draft and private jobs stay hidden from anyone who cannot already edit them
- Job content is escaped in the editor exactly as on the front end
A privately owned main contractor in Leeds is hiring a senior QS to take commercial ownership of a £40m mixed-use scheme through to practical completion, reporting to the commercial director.
- Five years’ post-graduate experience with a main contractor
- Valuations above £5m run without supervision
Specification
What it supports
The detail a developer or a design lead asks before committing to it.
| Widgets | Job List, Job Detail, Job Search and Filters, Job Application |
|---|---|
| Dynamic tags | Job title, job field, job custom field, job description, job link |
| Designing job pages | Through an Elementor Theme Builder template for the single job, which is what gets shown to visitors |
| Listing and paging | The listing reads its window from the plugin, so page counts and ordering match the rest of the board |
| Field visibility | Only fields enabled in the plugin are available to widgets or tags |
| When Elementor is absent | Nothing is registered and nothing loads. The integration is detected, not assumed |
| Licensing | The display side carries no licence check, so job pages keep rendering regardless of licence state |
Worth knowing
Two things to expect when you build it
-
Job pages are built as Theme Builder templates
You design the single-job layout as a Theme Builder template rather than by opening an individual job in Elementor. A job is synced from Bullhorn, so editing one job’s layout by hand is not how the board should be built — the template applies to every role.
-
Do not put two application forms on one page
The job page configuration can already include an application section. If your template also carries the Job Application widget, you get two forms. Switch one of them off.
W3Bullhorn is an independent product. It is not affiliated with, endorsed by or sponsored by Bullhorn, Inc. Bullhorn is a trademark of its owner.
FAQ
Questions about the Elementor integration
Short answers here. Anything else, ask us directly.
Keep reading