JobPosting Schema for Careers Websites: Guide and Examples

JobPosting schema is the structured data that tells Google, and any other system reading your page, exactly what a job is: its title, description, location, date posted, employer and more. Add it correctly to every job page on your careers website and your vacancies become eligible for Google’s job search experience, with your logo and job details. Add it carelessly and it can cause errors or even a manual action. This guide shows what to include and how.

This guide is part of our work on AI and search visibility. It sits under our hub on GEO and AEO for careers websites and complements the ultimate SEO guide for careers websites.

• Key takeaways
• What JobPosting schema does
• Required and recommended fields
• How to add it
• A complete example
• Field by field tips
• Mistakes to avoid
• What 14 careers websites include
• Making it easier
• FAQ
• Related reading
• Sources

What JobPosting schema does for your careers page

JobPosting is a type from schema.org, the shared vocabulary for structured data. On a job page, you add it as a block of JSON-LD, a small piece of code in the page that labels the facts: this is the job title, this is the employer, this is the place. Google says structured data on job pages makes your postings “eligible to appear in a special user experience in Google Search results”, with your logo and job details, and lets job seekers filter by criteria such as location or job title.

It is also simply good hygiene for any system that reads your site. A labelled fact is easier to extract than a sentence buried in a paragraph. That makes it useful for AI search too, even though Google is clear that its AI features need no special schema; see our guide to GEO and AEO for careers websites for the full picture.

JobPosting schema for your careers page: required and recommended fields

These are the properties in Google’s documentation, with how many of the 14 job pages we checked carried each one in the page source.

Source: Google Search Central JobPosting documentation; Happydance check of 14 live job pages, 31 October 2026. Careers websites are not named in the table.

How to add JobPosting schema

1. Use one JobPosting per job page. Google says to place JobPosting structured data only on pages dedicated to a single job, not on list pages.
2. Put it in the page source. JSON-LD in the HTML that arrives from the server is readable without running scripts, so every crawler can see it.
3. Match the visible page. The job title, location, salary and every other value in the markup must appear on the page. If a copy of the job exists at another URL, use canonical URLs.
4. Test it. Validate with the Google Rich Results Test, then deploy a few pages and use the URL Inspection tool in Search Console to see how Google reads them.
5. Keep Google informed. Submit a sitemap with accurate lastmod dates. Google also recommends the Indexing API for job posting URLs, because it prompts Googlebot to crawl sooner.
6. Expire jobs on time. When a job closes, populate validThrough with a past date, remove the page or add a noindex; Google warns that delay may result in a manual action.

A complete JobPosting example

This example uses placeholder values and follows Google’s documented format. It includes the five required fields and the most useful recommended ones.

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Software Engineer",
  "description": "<p>Full description: responsibilities, qualifications, skills, hours.</p>",
  "datePosted": "2026-10-01",
  "validThrough": "2026-12-01T23:59",
  "employmentType": "FULL_TIME",
  "identifier": { "@type": "PropertyValue", "name": "Example Co", "value": "R-12345" },
  "hiringOrganization": {
    "@type": "Organization", "name": "Example Co",
    "sameAs": "https://www.example.com", "logo": "https://www.example.com/logo.png" },
  "jobLocation": { "@type": "Place", "address": { "@type": "PostalAddress",
    "streetAddress": "1 Example Street", "addressLocality": "London",
    "postalCode": "EC1A 1AA", "addressCountry": "GB" } },
  "baseSalary": { "@type": "MonetaryAmount", "currency": "GBP",
    "value": { "@type": "QuantitativeValue", "minValue": 70000, "maxValue": 85000, "unitText": "YEAR" } },
  "directApply": true
}

For a fully remote role that may be done anywhere in one country, Google’s documentation uses applicantLocationRequirements with a country, plus "jobLocationType": "TELECOMMUTE", and the description must clearly say the job is 100% remote.

Field by field tips

Mistakes to avoid

• Markup that does not match the page. Google’s example: a job title on the page that differs from the title property, or salary in the markup that is not shown on the page.
• Using name instead of title. Google says the two are not interchangeable.
• Leaving closed jobs live. Expired jobs that remain accessible are a flagged error and may lead to a manual action.
• Putting JobPosting on list pages. Use it only on pages dedicated to a single job.
• Adding an estimated salary. Only the employer’s actual salary is allowed.
• Keyword stuffing titles and descriptions. It is against Google’s job posting content policies and does nothing for readers.
• Hiding it behind scripts. Keep the JSON-LD in the server HTML so that every crawler can read it.

What 14 careers websites include in their JobPosting markup

We read the JSON-LD on a live job page for each of the 15 careers websites in our best careers sites of 2026 ranking, all built on Happydance. 14 carry JobPosting markup in the page source, and the fifteenth adds it once the page renders. Every one of the 14 includes the full required set and, in addition, employment type and a unique job identifier.

The core is strong everywhere. A few careers websites go further, and each is verifiable on the live site:

• Coupa includes baseSalary and remote location fields in its JobPosting markup. Visit the careers website.
• Veterans United and Johnson and Johnson include a validThrough date, so the closing date is machine readable. Veterans United and Johnson and Johnson.
• Dropbox includes remote work fields (applicantLocationRequirements and jobLocationType). Visit the careers website.
• SAP declares directApply as true on the job page we checked. Visit the careers website.

Making it easier: where Happydance helps

Maintaining correct JobPosting markup across thousands of jobs is a job for software, not spreadsheets. On Happydance, the platform automatically generates metadata, schema markup and HTML and XML sitemaps, with structured schema and AI-ready metadata as part of its AI discoverability. The Job Description Genie and the content grader (80 criteria, with bias detection) help keep the visible job content strong and complete, which is what the description field must reflect. The analytics dashboard then shows how candidates arrive.

Explore the AI careers website platform and the SEO Concierge Service, which includes technical optimisation of schema markup, or audit your careers website to see how your job pages measure up.

JobPosting schema: frequently asked questions

Related reading

Sources

• Google Search Central, Job posting (JobPosting) structured data: developers.google.com/search/docs/appearance/structured-data/job-posting
• Google Search Central, AI features and your website: developers.google.com/search/docs/appearance/ai-features
• schema.org, JobPosting: schema.org/JobPosting
• Happydance check of 14 live job pages with JobPosting markup in the page source, from the 15 careers websites in best careers websites of 2026, 31 October 2026.