Job pages
One page per role, in your own theme
Each open role gets a full WordPress page at its own address: title, location, salary, description, your consultant and an apply form. It is rendered by your templates, so it looks like the rest of your site rather than like a plugin.
No iframe, and no vendor stylesheet fighting your design.
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
The problem it solves
A board inside a widget is one page pretending to be hundreds
Portals and embedded widgets put every role behind a single address. Candidates cannot link to a role, marketing cannot campaign against one, and search engines see one page where you have three hundred.
Inside a widget
One address for the whole board
- No address to share for a single role
- Nothing for search engines to index per role
- Styling that never quite matches the site
- Candidates sent off your domain to apply
With W3Bullhorn
A real page for every role
- Its own address, on your own domain
- Your theme, your templates, your layout
- Job structured data on every page
- Apply on the page, without leaving your site
What is on the page
The details a candidate decides on
Title, location, salary, job type and the description your consultant wrote, plus the fields you choose to show. Confidential details, such as a client name you are not free to publish, can be kept off the public page while staying in Bullhorn.
- The fields you map, in the order your templates want them
- Confidential fields kept off public pages
- Your consultant on the page, so candidates know who they are talking to
- An apply form on the page itself
Specification
What it supports
What a developer checks before quoting a build.
| Page type | An ordinary WordPress page for each role, rendered by your theme |
|---|---|
| Addresses | One address per role, stable while the role is open |
| Templates | Listing, single job and apply templates, each overridable from your own theme |
| Fields on the page | Title, location, salary, job type and description as standard, plus the fields you map |
| Structured data | Job structured data on every job page, and the page listed in a job sitemap |
| When a role closes | The page is retired rather than left to rot, and the sitemap is updated |
Boundaries
What job pages do not do
-
They are not a design service
Job pages inherit your theme. If you want a bespoke layout, your developer overrides the template, the way they would for any WordPress page.
-
They do not guarantee a ranking
Pages carry the data search engines read. Where a role ranks, and whether it appears in Google’s job results, is Google’s decision.
-
They are not a candidate account
Candidates read and apply without signing in. There is no login on a job page.
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 job pages
Short answers here. Anything else, ask us directly.