One source of truth
The desk, candidate page and job schema read the same record. Fewer copies to drift out of date.
Give each live role a clear page and application route. Keep it aligned with the desk, including when the vacancy closes.
The owner enters the vacancy facts once. Required fields and dates are checked before publication.
Owner, candidate and engine-room views read the same published record.
The public role, application route and machine-readable feed follow that shared state.
A filled or expired role leaves active results and stops accepting applications, including a stale application already open.
The owner enters the vacancy facts once. Required fields and dates are checked before publication.
Illustrative vacancy data. The working demo stores synthetic records in your browser and submits no real applications.
The desk, candidate page and job schema read the same record. Fewer copies to drift out of date.
One shareable page per role, readable without a login and usable on a phone.
Closed roles leave active results and stop applications, with a clear recovery if someone was already applying. When a vacancy closes, the website should know covers how that status stays aligned with the public page.
Schema describes the real vacancy and hiring employer. Salary and application details come from approved facts.
Open the jobs demo and follow one fictional vacancy through the three views. Vacancy and application records stay in your browser, with a synthetic CV and a simulated application queue.
Choose a vacancy and check its title, employer, location and closing date. The publish checks show what is missing from an incomplete draft.
Find a published role, open its details and try the application with the supplied fictional information. Then close the role in Owner and see how the candidate view changes.
Look at the fixture feed states, event history and example job data. The examples let you inspect the behaviour without connecting your agency's ATS.
These are fictional vacancies. The demo sends no real applications and publishes no live job markup. Your production feed, candidate data handling and application destination are scoped separately.
Correct markup supports eligibility for job results. The search engine controls crawling, indexing and display.
Publish accurate role pages, then observe their visibility.
The demo uses fictional vacancies, stays outside search and submits no real applications.
Live jobs board guide price: £1,999.
Scope, VAT, connections and running costs confirmed in writing. See pricing and terms.
A board normally sits inside a wider recruitment website build, and an agency opening a new desk or region should plan both together.
Job schema, Google for Jobs boundaries, and who remains the source of truth.
Each real vacancy gets structured data that describes the same facts as the public page: the role, hiring employer, dates and application route. This site sells that system; it is not itself a jobs board.
Correct markup supports eligibility. Google decides crawling, indexing and display. We do not promise appearance or ranking.
No. The ATS, or the agreed owner record, stays the source of truth. The public page follows that record, including when a role closes.
We agree the application route before contract. Writing back into the ATS depends on what that connector actually supports.
Purchase options transfer ownership under the written agreement. Hosting, connections and running costs are confirmed in writing. The guide price is £1,999.
Try the candidate view, then close a vacancy and see what changes.