JobPosting Structured Data Guide
JobPosting structured data is a machine-readable description of a real vacancy page. It should clarify visible facts, not act as a hidden advertisement or replace a complete candidate experience.
Where JobPosting markup belongs
Add JobPosting data only to the detail page for one genuine, currently available job. Do not place it on category results, general careers pages, employer profiles, training offers or pages that do not let a candidate understand and pursue the vacancy.
The page must remain publicly accessible to permitted users and its visible content must match the structured fields. Search providers apply their own policies and decide eligibility.
Core fields and consistency
A practical record includes the title, description, datePosted, validThrough, hiringOrganization and jobLocation, or the correct remote-work representation. Recommended fields such as employment type, identifier, salary and applicant location requirements should be supplied only when accurate and visible where policy requires.
Use ISO-compatible dates and a consistent timezone. Avoid promotional titles, placeholder employers, invented salary information and boilerplate descriptions shared across unrelated roles. The canonical URL should be the final public vacancy page.
Validation and publication in EdgeOrigin
The Schema Expiry Manager accepts editor-provided JSON-LD, checks required fields and corrects url and mainEntityOfPage to the published canonical route. It requires a physical job location unless jobLocationType represents telecommute work.
The current interface is a structured-data workflow attached to CMS posts, not a complete recruitment database. Editors must still build the visible job page and verify every fact before publication.
Expiry, removal and indexing notifications
After validThrough reaches the end of the configured website day, EdgeOrigin stops emitting the active job schema. Editors must also close the application path and choose whether the public page explains closure, redirects or returns an appropriate removal status.
The optional SEO Toolkit can send tenant-authorized Google Indexing API notifications for eligible job changes. A notification is a discovery request, not proof of indexing or ranking. Continue monitoring the public page and provider reports.
EdgeOrigin publishes practical website guidance grounded in current platform capabilities. We do not promise search rankings. Product details and external search tools can change, so verify requirements that are critical to your business.