Integrations
Built to fit the tools your website already uses
W3Bullhorn connects Bullhorn to WordPress. Around that, it behaves like a well-mannered WordPress plugin: your theme styles the pages, your SEO plugin keeps its job, and your fields stay where your site expects them.
Works and integrates with
The plugins you already run
If it is on your site, the job pages are built to sit beside it rather than argue with it.
- 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
In detail
Editors and page builders
The same four elements — board, search, job details, application — in whichever one you build with. They render through one shared seam, so a page built in any of them shows the same board.
WordPress block editor
Four blocks: board, search, filters and the application form. BuilderElementor
Widgets and dynamic tags for job data. BuilderBeaver Builder
Four modules, in your existing layouts. BuilderWPBakery
The same four elements, for a site built on it. BuilderDivi
Four modules for the Divi Builder.Also integrated
Fields, forms and SEO
Advanced Custom Fields
get_field() answers with Bullhorn data, nothing copied into your database. FormsGravity Forms and other form plugins
Keep the application form you already built in Gravity Forms, WPForms, Contact Form 7, Fluent Forms or Elementor Forms. SEOYoast SEO
Who owns titles, canonicals, sitemaps and job data. SEORank Math
The same split, decided by your rich-snippet setting.Bullhorn and WordPress
The integration everything else depends on
Jobs come out of Bullhorn and appear as pages on your site; applications go back into Bullhorn against the job they were made for.
Bullhorn
Connected through the Bullhorn REST API with your own API credentials. Your consultants keep working in Bullhorn, and it stays the record. CoreWordPress
A plugin on your existing site: job pages rendered by your theme, set up from the WordPress admin and updated like any other plugin.Your fields
Bullhorn fields, in the structure your site already uses
Choose where each Bullhorn field lands in WordPress: sectors and locations as taxonomies you can filter on, other details as custom fields, including the ACF fields your templates already read. Confidential fields stay off public pages.
- Sectors and locations as WordPress taxonomies
- Other details as custom fields, ACF included
- Confidential fields kept off public pages
Your SEO plugin
Job pages your SEO plugin still understands
Job pages are ordinary WordPress pages, so the SEO plugin you already run keeps doing its job. W3Bullhorn adds the job-specific structured data and the job sitemap, without a second set of titles, canonical tags or duplicate markup.
- Job structured data added, not duplicated
- A job sitemap alongside your existing sitemaps
- Titles and canonical tags left to your SEO plugin
One of 412 roles, each on its own URL. Eligibility for Google’s job experience remains Google’s decision.
On a real site
What else it has to live with
-
Your theme
Job listings and job pages are templates that take your theme’s styles, and can be overridden.
Read more: Your theme -
The block editor
Job lists, search and apply as blocks, placed where the design needs them.
Read more: The block editor -
Multilingual sites
Job pages behave like ordinary pages, so a multilingual site can treat them the same way.
-
Your other plugins
No iframe, no second candidate database and nothing sensitive added to public output.
Read more: Your other plugins
FAQ
Questions about integrations
Short answers here. Anything else, ask us directly.