JobAdder
website integration
JobAdder website integration connects JobAdder to your recruitment website so that job ads posted in JobAdder appear on your site and applications come back into JobAdder against the right job, tagged with their source. JobAdder offers four routes: its hosted CareersPage, a JavaScript widget, an XML job feed, or its API.
Your JobAdder jobs, on your own site
- 01
Live jobs on your own site
Jobs you publish in JobAdder appear on your website automatically, with keyword, location, sector and salary search and filters, and a page of their own for every job.
- 02
Google for Jobs markup
Each job page carries JobPosting structured data. Google requires it on the same page as the job description candidates read, on the most detailed page possible, and not on search-results pages.
- 03
Applications straight back into JobAdder
Applications and registrations create or update the candidate record, attach the CV, link the candidate to the job where JobAdder supports it, and record the source so you can see which jobs and channels work.
- 04
Job alerts
Candidates can sign up for alerts by keyword, location or sector and are emailed when matching jobs go live.
- 05
Expiry and unpublishing
When a job is filled or unpublished in JobAdder, it comes off your site. Google asks for expired jobs to be removed from the page, marked with a past validThrough date, or returned as 404 or 410.
How JobAdder integration works technically
Based on JobAdder's own published documentation, linked below. Vendors change their APIs and access rules, so we confirm the details with JobAdder before every build.
- 01Four ways to show jobs
- JobAdder's help centre lists four: a hosted CareersPage you link to, a JavaScript widget you embed, an XML job feed your developer builds pages from, and direct integration with the JobAdder API for “ultimate control”.
- 02XML job feed
- JobAdder sends an XML file of your job ads, either uploaded to your FTP server (JobAdder says SFTP isn't supported) or posted over HTTP to a URL your developer creates. Each job includes an apply section with the email address applications go to and a unique application form URL.
- 03API
- JobAdder's API lets developers pull and push data, and JobAdder says developers need experience of OAuth2 authentication. JobAdder Support creates your job board and job portal and shares their IDs; the developer then contacts api@jobadder.com and receives instructions once a JobAdder admin confirms they are building the integration. Applications use the job applications endpoints in JobAdder's API documentation.
- 04Source tracking
- JobAdder says it tracks every applicant back into JobAdder with automatic source tagging.
- 05What the agency needs to request
- Decide which of the four options you want, then contact JobAdder Support. For a feed you'll supply server details or a URL to post to; for the API, Support sets up the job board and portal and your developer applies to the API team.
Four ways to connect JobAdder to your website
| Option | Cost model | Design freedom | SEO control | Data flow | Lock-in |
|---|---|---|---|---|---|
| JobAdder CareersPage or widgetJobAdder hosts a branded CareersPage you link to, or gives you a JavaScript widget to embed. JobAdder itself says the CareersPage “does not offer a lot of customisation”. | Set up through JobAdder Support | Low: JobAdder's template or widget styles | Limited: jobs sit on JobAdder's page or inside a script | Applications handled by JobAdder | Tied to JobAdder |
| Off-the-shelf pluginWordPress plugins exist that import JobAdder jobs as pages on your site through the JobAdder API or feed. Check how each one handles applications, expiry and Google for Jobs markup before you buy. | Plugin licence plus your website build | High, within your CMS theme | Good if jobs render as pages on your domain | Depends on the plugin: some send candidates to JobAdder's own application form | Tied to the plugin |
| Recruitment website platform with a connectorAccess Volcanic, for example, documents a JobAdder integration: jobs publish to the website, and candidates either finish applying on JobAdder or apply on the site through a custom app that Access says is chargeable. | Monthly platform fee, often on a fixed-term contract, plus set-up | Medium: within the platform's templates and modules | Medium: on your domain, within what the platform allows | Jobs in; applications via JobAdder's form or a paid app | High: site, jobs and integration sit with the platform |
| Custom integration in your own site (what we build)We build job search and job pages on your domain from JobAdder's feed or API, with JobPosting markup, and send applications back to JobAdder against the right job with CV, source and consent. | Scoped to your requirements; included in our 5-page website offer | Full | Full: every job is an indexable page on your domain | Two-way, mapped to your fields and rules | Low: you own the site and the code |
Third-party products are named only where the vendor's own documentation (linked above) describes the integration. TRG Digital is independent and not a JobAdder partner.
How a JobAdder integration project runs
Audit what you have
We look at how jobs reach your site today, what happens to an application, and where candidates and Google see your jobs.
Get API access
Your JobAdder admin requests API access from the vendor, and nothing is built until it is confirmed. Tell JobAdder Support you want the XML feed or API option. For the API, Support creates your job board and portal IDs and a JobAdder admin confirms your developer with the API team.
Map the fields
We agree which ATS fields drive titles, filters, salary, location and the Google for Jobs markup, and how applications map back.
Build job search and job pages
Search, filters and a fast, indexable page for every job on your own domain, with JobPosting structured data.
Connect applications and registrations
Forms write to JobAdder: candidate created or updated, CV attached, source recorded, consent captured.
Handle expiry
Unpublished and filled jobs leave the site and Google; old job URLs return the right status.
Test with live jobs
We publish, edit and close test jobs, submit test applications and check every record in JobAdder before launch.
Launch and monitor
We watch the sync, Google Search Console job reports and application volumes after launch.
What we'll need from you
- An JobAdder admin who can request or approve API access
- Your list of job fields to show (title, salary, location, sector, job type, consultant)
- How you want applications recorded: new candidate, update existing, source value
- Your privacy notice and the consent wording you use today
- A handful of live test jobs we can publish and unpublish
What goes wrong, and how to avoid it
- Iframes and embedded widgets
- Jobs shown inside an iframe live on someone else's page. Google says JobPosting data must be on the same page as the job description the candidate reads, so an embedded list usually gives you no Google for Jobs listings and no search value on your own domain.
- Jobs on an ATS subdomain
- Hosted careers pages often sit on the vendor's domain or a subdomain. Candidates still find the jobs, but the search visibility builds up on that address rather than your website.
- Duplicate candidate records
- If every application creates a new candidate, your database fills with duplicates. Match on email (and phone where you can) and update the existing record instead.
- GDPR and consent capture
- The ICO says you must give people privacy information at the time you collect their data. Link your privacy notice on every form, record what the candidate agreed to and when, and send that record to the ATS with the application.
- Expired jobs left live
- Jobs that are filled but still marked up confuse candidates and break Google's rules. Make sure unpublishing in the ATS removes the job or its markup from your site.
- Field mapping left to defaults
- Sector, location and job type values in the ATS rarely match your website's filters out of the box. Agree the mapping before build, not after launch.
A 5-page recruitment website with job pages and integrations included, worth up to £4,999, is free with any SEO package from £299 a month (12-month minimum term). Additional pages are priced on requirements.
It connects JobAdder to your recruitment website so job ads posted in JobAdder appear on your site and applications come back into JobAdder against the right job, tagged with their source.
JobAdder lists four: its hosted CareersPage, a JavaScript widget, an XML job feed that your developer builds pages from, and direct integration with the JobAdder API.
The XML feed is simpler: JobAdder sends your jobs to your server and each job carries an application URL. The API gives more control, including submitting applications directly, but needs a developer experienced with OAuth2 and approval from JobAdder's API team.
Usually not much. Jobs loaded by a script or hosted on JobAdder's CareersPage don't give your own domain an indexable page per job, and Google wants JobPosting markup on the same page as the job description.
Choose your option, contact JobAdder Support, and give them what that option needs: for a feed, your server details or a URL to post to; for the API, Support creates the job board and portal, and your developer contacts api@jobadder.com once your admin confirms them.