Post one job to 50+ job boards in a click. Start free. →
POST A JOB
Google for Jobs is not a posting destination - it's a search experience that indexes job listings from other sources. You get on it by adding JobPosting structured data to a careers page or by using an ATS that syndicates to it.
Updated May 24, 2026Google for Jobs launched in 2017 as an enhanced search experience that aggregates job listings from across the web. It's free for both employers and candidates. Unlike Indeed or ZipRecruiter, Google does not host job listings on its own platform - it indexes them from third-party sites that publish in a structured format Google understands.
There are three ways to appear in Google for Jobs: post on a major board that already syndicates (Indeed, LinkedIn, Glassdoor, ZipRecruiter all do), use an ATS that publishes structured data and submits to Google's Indexing API (most modern ATSs including ParsleyHR), or self-host the listing on your own careers page with JobPosting schema markup and a job-postings sitemap.
6 steps, around 10-15 minutes start to finish.
Three routes lead to Google for Jobs: (1) post on a major syndicating board like Indeed or LinkedIn - they push to Google automatically; (2) use an ATS that publishes structured data and pings the Indexing API for you; or (3) self-host on your careers page with JobPosting schema. Most small businesses pick routes 1 or 2.
On your careers page, embed JSON-LD JobPosting schema for each role. Required fields: title, description, datePosted, validThrough, hiringOrganization (with name and logo URL), jobLocation, and either baseSalary or a clearly-stated 'compensation not disclosed'. Optional but recommended: employmentType, qualifications, responsibilities, and applicantLocationRequirements for remote.
Google requires a separate sitemap entry that lists your active job postings, with the lastmod date reflecting the most recent post or update. Submit this sitemap in Google Search Console under Sitemaps.
Add your domain to Google Search Console, verify ownership, and submit your job-postings sitemap. For faster indexing on new posts, use the Indexing API to ping Google immediately when you publish a new role. The API is meant specifically for JobPosting and LiveStream content.
Search Google with your role's title plus location (e.g. 'line cook brooklyn'). If you're in, you'll appear in the Jobs box (the boxed widget at the top of the SERP). You can also check Search Console under Performance > Search Appearance > Job Posting for click and impression data.
Google for Jobs ranks fresh posts higher. Edit the description or update validThrough on long-running roles every 14 days to signal freshness. When you fill the role, set the job's status to 'closed' and remove it from your sitemap - leaving filled jobs live tanks your domain's job-posting trust score.
| Tier | Price | What you get |
|---|---|---|
| Google for Jobs indexing | $0 | Free, always. Google doesn't charge employers or job boards for inclusion. Your costs come from whatever channel you use to publish (your ATS, your careers page hosting, or a paid job board if you go that route). |
Google for Jobs is a free search feature. You only pay for the publishing tool you use to feed it.
Drop this into the Google for Jobs description editor and replace the bracketed fields. Tuned to the formatting Google for Jobs renders cleanly.
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "JobPosting",
"title": "[JOB TITLE]",
"description": "<p>[Full HTML description - responsibilities, qualifications, benefits.]</p>",
"identifier": {
"@type": "PropertyValue",
"name": "[COMPANY NAME]",
"value": "[unique-job-id]"
},
"datePosted": "2026-05-24",
"validThrough": "2026-06-24T23:59",
"employmentType": "FULL_TIME",
"hiringOrganization": {
"@type": "Organization",
"name": "[COMPANY NAME]",
"sameAs": "https://[your-domain.com]",
"logo": "https://[your-domain.com]/logo.png"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"streetAddress": "[123 Main St]",
"addressLocality": "[City]",
"addressRegion": "[State]",
"postalCode": "[ZIP]",
"addressCountry": "US"
}
},
"baseSalary": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": {
"@type": "QuantitativeValue",
"minValue": [X],
"maxValue": [Y],
"unitText": "HOUR"
}
}
}
</script>Yes. Google does not charge to be indexed in Google for Jobs. The only cost is whatever publishing channel you use to feed Google - which can also be free (your own careers page) or paid (Indeed sponsored, ZipRecruiter, etc.).
No. Google for Jobs is an index of listings from across the web, not a posting destination. You publish on a third-party board (Indeed, LinkedIn, ZipRecruiter, etc.) or on your own careers page with JobPosting structured data, and Google pulls the listing from there.
If you post on a board that already syndicates (Indeed, LinkedIn, Glassdoor), typically within hours. If you self-host with structured data on a new domain, expect 2-7 days for first indexing. Subsequent posts on the same domain index faster once Google trusts the source.
Only if you're self-hosting. If you use an ATS that publishes structured data (ParsleyHR does this automatically) or post on a major board, no developer is needed. The DIY path - editing your site's HTML to add JobPosting JSON-LD and creating a job-postings sitemap - usually requires technical help on the first pass.
The three most common causes: (1) structured-data validation errors visible in Search Console; (2) missing required fields (datePosted, validThrough, hiringOrganization with logo, baseSalary or 'compensation not disclosed'); or (3) the domain is too new and Google hasn't built trust yet. Test your markup at search.google.com/test/rich-results.
Yes. ParsleyHR automatically publishes JobPosting structured data on your careers page, maintains the job-postings sitemap, and pings Google's Indexing API on every new post. You get indexed without writing a line of JSON-LD.
Google for Jobs aggregates from everywhere. Posting on Indeed, LinkedIn, and your own careers page (via ParsleyHR) means Google sees the role from three sources - which Google reads as authority.
