Features
Everything W3Bullhorn does, in one place
From the job page a candidate reads to the application your consultant picks up in Bullhorn. One plugin, on your own WordPress site, with no iframe and no separate service to wire up.
Reporting to the commercial director on a £40m mixed-use scheme in the city centre. Two-stage interview, car allowance, immediate start available.
Jobs on your site
Your roles, as pages on your website
-
Job pages in your theme
Job listings and job pages built from your templates, and overridable like any template.
Read more: Job pages in your theme -
Sectors and locations
Bullhorn categories and locations become filters, each with its own address.
Read more: Sectors and locations -
Search and filters
Keyword search and filters candidates can share, bookmark and link to.
Read more: Search and filters -
Always current
New and changed roles appear on the site; closed roles come off it.
Read more: Always current
Applications
Every application, into Bullhorn
-
Apply on your site
An apply form on the job page, in your theme, with no account to create.
Read more: Apply on your site -
Delivered to Bullhorn
Against the job the candidate applied for, with the CV attached.
Read more: Delivered to Bullhorn -
Confirmations and notifications
A confirmation for the candidate, a notification for the recruiter.
Read more: Confirmations and notifications -
Consent and privacy
Consent recorded with the application, CVs held privately until delivered.
Read more: Consent and privacy
Found in search
Job pages built for the way candidates search
Every job page carries job structured data and is listed in a job sitemap, which is what job search engines read. Filtered views are real pages with their own addresses, so the searches that matter in your markets can be found too.
- Job structured data on every job page
- Job sitemaps kept up to date
- Closed roles leave the listing and the sitemap, and say so on the page
One of 412 roles, each on its own URL. Eligibility for Google’s job experience remains Google’s decision.
Your data, your structure
Choose which Bullhorn fields appear, and where
Sectors and locations become filters, other details become fields on the page, and confidential ones stay off public pages altogether. Changed from the WordPress admin, without code.
- Bullhorn fields mapped to your WordPress structure
- Confidential fields kept off public pages
- Changed from the admin, without code
Admin and sync
A connection you can watch
The status screen shows the last run, the next run and what changed. Run history keeps what happened, errors are reported in plain language, and WP-CLI is there for resyncs and scheduled maintenance.
- Sync status and run history in the WordPress admin
- Plain-language errors, and an alert when a run fails
- WP-CLI for resyncs and scheduled maintenance
| Started | Result |
|---|---|
| 09:14:02 | 34 changes |
| 09:09:01 | No changes |
| 09:04:00 | 3 submissions |
Building your site
For whoever builds and runs the website
-
WordPress blocks
Job lists, search and apply as blocks in the editor.
Read more: WordPress blocks -
Works with your theme
Templates take your theme’s styles, and any template can be overridden.
Read more: Works with your theme -
One build per client
The same plugin on every Bullhorn client site you run.
Read more: One build per client -
No second database
Bullhorn stays the record; the website is not a parallel candidate store.
Read more: No second database
Works and integrates with
- WordPress block editor
- Elementor
- WPBakery
- Divi
- Beaver Builder
- Gravity Forms
- WPForms
- Contact Form 7
- Fluent Forms
- Yoast SEO
- Rank Math
- All in One SEO
- SEOPress
- ACF
FAQ
Questions about features
Short answers here. Anything else, ask us directly.