Quick answer
To show live job listings on your website, find out what your recruitment software offers (an embeddable widget, a job feed or an API), then embed its jobs board or pull each vacancy into its own page on a schedule. Give every job its own URL, mark it up for Google and remove it when the role closes.
The usual starting point is a careers page that someone updates by hand. A care provider in Norwich posts roles on its recruitment system, then a manager remembers, a week later, to copy them onto the website. Closed jobs linger, new ones appear late, and applicants ring about vacancies that were filled a month ago. Syncing the two fixes that, and it is less work than most people expect.
You can also have this done for you: our custom business software service is available from £1,499.
Step 1: check what your recruitment software offers
Every applicant tracking system (ATS) handles this differently, so begin with its help pages or account manager. You are looking for one or more of these:
| Option | What it is | Effort | Control over look and search |
|---|---|---|---|
| Hosted careers page | A jobs page on the provider’s own web address | None | Low; visitors leave your site |
| Embeddable widget | A snippet that shows the jobs list inside your page | Low | Medium; styling options vary |
| Job feed (XML, JSON or RSS) | A file listing all open roles, updated automatically | Medium | High; you build the pages |
| API | Programmatic access to jobs, and sometimes to applications | Medium to high | Highest; two-way possible |
Ask too whether feeds and API access are included on your plan, whether there is a limit on how often you can request data, and whether the feed includes everything you want to show, such as salary, location, contract type and closing date.

Step 2: choose embed or import
An embedded widget is quick and stays current by itself, but the jobs usually live inside the widget rather than as pages on your site. That limits how well individual vacancies can be found in search and how closely they match your design.
Importing jobs from a feed or API means a small piece of code on your website fetches the open roles on a schedule and creates or updates a page for each one. It takes a developer to set up, but each vacancy becomes a proper page on your own domain, styled like the rest of the site and eligible to appear in Google’s job search features. If you hire regularly, importing is usually worth it. Our comparison of no-code and custom development helps if you are weighing an automation tool against a coded solution.
Step 3: give every job its own page
A single careers page with a long list is fine for browsing, but each vacancy should also have its own page with a stable address. That page should carry the full job description, location, pay, hours, contract type, closing date and a clear apply button.
Write job pages in plain, inclusive language. The government’s guidance on preventing discrimination in recruitment covers wording to avoid in job adverts, and it applies to your website exactly as it does to a jobs board.
Step 4: mark up each job for Google
Google can show vacancies in its job search experience when the page carries structured data. Google’s job posting documentation sets out the rules:
- The required properties are the date posted, the description, the hiring organisation, the job location and the title.
- The title should be the job title only, without codes, dates or the company name.
- The markup belongs only on the page for a single job, never on the listing page.
- Remote roles can use applicant location requirements instead of a job location.
The vocabulary itself is published at schema.org. Generating it automatically from the feed means every imported job is marked up correctly without anyone touching code. If your vacancies are not appearing at all, our guide to a website not showing on Google covers the wider checks.
Step 5: remove closed jobs promptly
This is the step most sites get wrong, and it matters. Google says expired job postings must be dealt with in one of three ways: set the valid-through date in the past, remove the page so it returns a not-found or gone status, or remove the job markup from the page. Leaving expired jobs marked up can lead to a manual action against the site.
Your sync should therefore do three things on every run:
- Create pages for new roles in the feed.
- Update pages whose details have changed.
- Close pages for roles that are no longer in the feed, either by marking them closed with no job markup or by removing them.
Google also offers an Indexing API for job pages, which asks it to recrawl a page sooner than a sitemap would, including when a role is removed. It is worth adding if you hire in volume.
Step 6: decide where people apply
There are two common patterns. The simplest is an apply button that sends candidates to the recruitment system’s own application form for that job, so CVs and answers land straight in your ATS. The more integrated option is an application form on your own site that submits to the ATS through its API.
Either way, CVs are personal data. Keep them in the recruitment system rather than in website email inboxes, use HTTPS, and link your privacy notice from the form. An on-site form also needs testing like any other; as our guide to a contact form that is not working explains, a silent failure loses people without anyone noticing.
Step 7: set the schedule and monitor it
For most small and medium employers, syncing every hour or a few times a day is plenty. Check the provider’s request limits before going more often. Then add simple monitoring:
- A log of each sync: how many jobs were added, updated and closed.
- An alert if the feed cannot be reached or returns nothing, so a temporary error does not close every job on your site.
- A monthly spot check that the website matches the ATS.
That safeguard in the second point is important. A sync that treats an empty response as “all jobs closed” can wipe your careers section overnight.
What it costs
Embedding a widget costs little beyond styling. Importing from a feed or API, with a page per job, structured data and closing logic, is a defined development job. Our API Development and Integration service starts from £499 and every project is scoped before work starts. If your careers section is part of a wider rebuild, a Custom WordPress Website is £499 one-off for up to 8 pages, with larger builds quoted in writing. See all prices on our pricing page.
Get the UK Website Project Brief Template (free)
A two-page template for briefing any UK web designer: sitemap, integrations, audience and deliverables. Cuts revision rounds in half.
No spam. UK GDPR compliant. We only use your email to send this resource, unless you tick the box to hear from us.
Frequently asked questions
Can my recruitment software update my website automatically? +
Usually, yes. Most applicant tracking systems offer an embeddable jobs widget, a job feed or an API. A widget updates itself but keeps jobs inside the widget. A feed or API lets a small piece of code on your website create and update a page for each vacancy on a schedule, styled like the rest of your site.
Should each job have its own page? +
Yes, if you want vacancies to be found in search. Google's job posting markup must only be used on a page for a single job, not on a listing page. A separate page per vacancy also gives room for the full description, pay, location and closing date, and a clear apply button.
What happens if closed jobs stay on my site? +
Applicants waste time on roles that are filled, and Google treats expired job postings that are still marked up as a policy problem that can lead to a manual action. Your sync should close or remove pages for roles no longer in the feed, and remove the job markup or set a past closing date.
How often should job listings sync? +
Every hour or a few times a day is enough for most employers. Check your provider's request limits before syncing more often. Add an alert for when the feed cannot be reached or returns nothing, so a temporary error does not accidentally close every vacancy on your careers page.


