Skip to content
W3Bullhorn
W3Bullhorn

Bullhorn WordPress Integration

The Bullhorn WordPress integration, built as a plugin

W3Bullhorn connects Bullhorn to your WordPress website. Your open roles become real pages on your own domain, and every application goes back into Bullhorn against the right job, with no custom integration to build or maintain.

Installs on your existing WordPress site and theme.

What it is

A Bullhorn integration your website owns

W3Bullhorn is a WordPress plugin. It connects to your Bullhorn account, reads the roles you choose to publish, and turns each one into a normal WordPress page with its own address, template and job structured data. Your consultants keep working in Bullhorn; nobody has to touch the website to put a job live.

Candidates search, read and apply on your pages, not inside a frame from another domain. When someone applies, the application goes back into Bullhorn against the job they applied for, with their CV attached.

In practice

  • Works with your theme. Job pages use your templates, with sensible defaults when you want them.
  • No iframe, anywhere. Job content is part of your own pages, in your page source.
  • Your URLs. Every role has its own address on your domain.
  • Your analytics. Views, searches and applications measured in your own tools.

How it works

Connected once, then it runs

Set up from the WordPress admin. After that, Bullhorn and your website stay in step without anyone re-typing a job.

  1. Set up

    Connect Bullhorn

    Add your Bullhorn API credentials in the plugin settings.

  2. Configure

    Choose which jobs appear

    Publish the roles you want on the website, and decide how they look.

  3. Bullhorn → site

    Jobs become pages

    New, changed and closed roles are reflected on your site.

  4. Site → Bullhorn

    Applications go back

    Every application arrives in Bullhorn for your consultants to work.

The job page

One page per role, with the job data search engines read

Each role gets a full page in your theme: title, location, salary, description, your consultant and an apply form. Every job page carries job structured data and is listed in a job sitemap.

  • Job structured data on every job page
  • Closed roles leave the listing and the sitemap, and say so on the page
  • Apply on the page, without leaving your site

Google for Jobs and job SEO

Applications

Every application goes back to Bullhorn

Candidates apply on the job page. The application arrives in Bullhorn against the right job, with the CV attached and the candidate’s consent recorded.

  • CV attached to the candidate in Bullhorn
  • Consent recorded with the application
  • A confirmation for the candidate, a notification for the recruiter

How applications reach Bullhorn

Field mapping

Your Bullhorn fields, your WordPress structure

Choose which Bullhorn fields appear on the page and where they go in WordPress: sectors and locations as filters, other details as custom fields, confidential ones kept off public pages.

  • Sectors and locations as filters
  • Confidential fields kept off public pages
  • Changed from the admin, without code

Compare

Ways to integrate Bullhorn with WordPress

Searchers weigh the same options: an automation tool, a custom build, Bullhorn’s own portal, or a dedicated plugin. They differ in who owns the pages and who maintains the connection.

Capability W3Bullhorn Automation tool (e.g. Zapier) Custom integration Bullhorn career portal
What you get
Each role as its own page on your domain Yes Via automations If built One page
Job pages in your theme Yes Basic posts If built No
Applications back into Bullhorn Yes Separate automation If built Yes
Who maintains the connection Maintained as a product You, per automation Your developers Bullhorn
A comparison of approaches, not a review of named products. Zapier and Bullhorn are trademarks of their owners.

Who it is for

Built for the people who own the board

FAQ

Questions about the integration

Short answers here. Anything else, ask us directly.

What does a Bullhorn WordPress integration do?

It connects your Bullhorn account to your WordPress website, so the jobs in Bullhorn appear as pages on your site and applications made on the site arrive back in Bullhorn.

Do I need Bullhorn API access?

Yes. W3Bullhorn connects through the Bullhorn REST API, so your Bullhorn account needs API access enabled. Your Bullhorn account manager can confirm it.

Does it replace the Bullhorn career portal?

Yes. It does the same job on your own website, listing roles and taking applications, with each role on a page of its own instead of inside a portal.

Can we use it instead of Zapier?

Yes. Instead of building and maintaining separate automations for jobs and applications, W3Bullhorn handles both between Bullhorn and WordPress as one plugin.

Do we need a developer to set it up?

Not for the core set-up, which is done from the WordPress admin. Developers can override templates when a design needs it.

Will it work with our theme?

Yes. Job listings and job pages use your theme, so the job board looks like the rest of your site.

Put your Bullhorn jobs on your own website

See W3Bullhorn working with your own Bullhorn jobs, on a short call with a specialist who knows Bullhorn and WordPress.

Book a demo How it works