Job listings are the highest-churn content a staffing firm publishes. Requisitions open, fill, get reposted for a second branch and close again, sometimes within days. Without rules, that churn leaves expired pages, duplicate postings and endless filter URLs that waste crawling and dilute the site.
JobPosting fields and expiry handling
Google's job posting documentation requires a title, description, datePosted, hiringOrganization and jobLocation, and recommends validThrough, employmentType, baseSalary and identifier where you have them. Remote roles use the remote-work properties instead of a fake office address. When a job is filled or closed, Google asks that the page be removed, return a not-found status or have its markup and validThrough updated, so a closed req stops appearing in job search. Pay information also matters for compliance: a growing number of states and cities require pay ranges in job advertisements, so the salary field should match what the posting says.
On-domain vs ATS-hosted job pages
Many firms publish jobs through their applicant tracking system, which hosts them on a subdomain or on the vendor's own domain. That can be fine for applications, but links and engagement then build up somewhere other than your main site, and the markup, canonical tags and indexability depend on the vendor's settings. We check what the ATS outputs and, where it makes sense, recommend an on-domain job feed that keeps the apply flow in the ATS.
Controlling filter, search and duplicate URLs
Keyword, radius, shift and pay filters can generate thousands of URLs with the same handful of jobs. Those are kept out of the index with noindex or canonical rules, and only the individual job pages and a small set of useful category pages are left open. The same requisition posted for two branches gets one canonical version unless the roles are genuinely different.
The Indexing API for high-churn listings
Google's Indexing API officially supports pages with JobPosting markup. For a board with many short-lived listings, it can notify Google when jobs are added or removed faster than waiting for a sitemap recrawl. It is worth setting up only once the markup and expiry rules are correct.
What Google for Jobs does and does not do
Google for Jobs mainly brings applicants. It strengthens candidate supply, which helps recruiters fill orders, but job orders come from employer-facing pages, branch profiles and evaluation content. Both are tracked, just not in the same goal.