Careers Website SEO Study 2026: how 60 large employers set up Google for Jobs

We crawled the careers websites of 60 large employers, rendered in Chrome, and checked 25 SEO and structured data points against Google's JobPosting documentation. This study shows what is in place, what is missing and how to fix it.

• Summary
• Test method
• Results
• Happydance subgroup
• Fix list
• Limitations
• FAQ

Executive summary

1. We crawled the careers websites of 60 large employers (the home page and one job page each, rendered in Chrome, on 30 October 2026) and checked 25 SEO and structured data points against Google's JobPosting documentation.
2. 49 of 60 job pages (82%) carried JobPosting markup, and 43 of 60 (72%) had every property Google requires. 45 of 60 (75%) delivered the markup in the initial HTML, without needing JavaScript.
3. The recommended properties were much less common: employmentType on 73% of sites, directApply on 48%, validThrough on 18% and baseSalary on 17%.
4. 26 of 60 job pages (43%) had no H1 in the initial HTML, and only 25 of 60 (42%) kept the job page title tag within 60 characters.
5. Basics were mostly in place: all 60 job pages returned HTTP 200, 58 of 60 had no noindex tag and 53 of 60 had a canonical tag. Sector differences were small (complete markup on 67% to 75% of sites in every sector group).
6. Separate subgroup, clearly labelled: the 8 Happydance careers websites we tested passed a median of 12 of 12 foundation checks against 10 of 12 for the 60-site sample, and 6 of 8 passed all twelve against 6 of 60.
7. This is a technical audit of what is on the page. It does not measure rankings, indexation counts or traffic, and it covers one job page per site.

Test method

• Sample: the same 60 large employers as the Careers Website Speed Report 2026 (a convenience sample across 14 sectors and four regions), plus the 8-site Happydance subgroup reported separately.
• Pages: each site's home page and one job page, chosen and validated automatically.
• Rendering: Chrome with JavaScript on, five seconds after the DOM loaded, plus a second pass with JavaScript off to read the initial HTML.
• Structured data: JSON-LD parsed including nested graphs and lists. JobPosting required properties checked against Google's documentation: title, description, datePosted, hiringOrganization and jobLocation with addressCountry (or a fully remote job with applicantLocationRequirements).
• Recommended properties checked: validThrough, employmentType, baseSalary, directApply, identifier and jobLocationType.
• Crawlability: robots.txt read for Googlebot rules on the job URL and for a sitemap declaration; noindex and canonical read from the rendered page.
• Lighthouse SEO scores come from the same runs as the Speed Report (mobile, medians of three runs).

Results: how top employers set up careers website SEO

The core checks

Crawl and indexing basics were largely sound. The gaps were in the details that help a job page be understood: 18% had no JobPosting markup, 43% had no H1 in the initial HTML, and 58% had a job page title tag over 60 characters, which search results may truncate.

JobPosting schema: required and recommended properties

Of the 49 sites with JobPosting markup, 43 (88%) had every required property. In five of the six sites with incomplete required markup, the gap was a missing addressCountry in the job location. Google says JobPosting belongs on single-job pages only; none of the 60 sites placed it on the home page.

Google recommends validThrough and a way to retire expired jobs, and recommends baseSalary and directApply where they apply. Few employers set them, which is the clearest opportunity in the data.

Sector view

Happydance subgroup (labelled, separate)

The 8 Happydance careers websites we tested are reported here separately and never mixed into the 60-site figures. Happydance publishes this study and has an interest in the result.

The subgroup is small and consists of Happydance builds, so it shows what these 8 sites measured, not what every Happydance site will measure. Appendix A lists every check, including those where the subgroup passes fewer sites.

Careers website SEO fix list

1. Put JobPosting markup on every single-job page and nowhere else. Check it matches the visible page.
2. Include every required property: title, description, datePosted, hiringOrganization, and jobLocation with addressCountry (or applicantLocationRequirements for fully remote jobs).
3. Serve the markup and the H1 in the initial HTML, not only after JavaScript runs.
4. Add validThrough, and remove or update the markup when a job closes. Google says expired jobs need a past validThrough or removal.
5. Add employmentType, identifier, directApply and baseSalary where they apply.
6. Use one H1 per page and a unique job title tag within about 60 characters.
7. Add a canonical tag pointing to the job page's own URL.
8. Declare the sitemap in robots.txt and keep job URLs crawlable.
9. Consider Google's Indexing API for job URLs, as Google recommends, and keep a sitemap too.
10. Validate in the Rich Results Test and watch URL Inspection and Search Console after changes.

Frequently asked questions

Related reading

Sources

• Google Search Central, Job posting (JobPosting) structured data: developers.google.com/search/docs/appearance/structured-data/job-posting
• Original data: Happydance rendered crawl of 68 careers websites, 30 October 2026. Anonymised data published with this study.

Appendix A: all checks

The twelve foundation checks were set as the core indexing, JobPosting basics, title and meta checks. They exclude salary, directApply, validThrough, title length and a few others that are less widely adopted or optional.