Google for Jobs is free. Google doesn't sell placement in its job search. It reads JobPosting structured data from a job's own page, on your careers site or a job board that publishes it. Add the required fields, take expired jobs down, and let Google crawl the page. Google decides what appears.
By Dev Rishi Khare, former machine learning engineer at Amazon (search and recommendations) and Synopsys
Is Google for Jobs really free?
Yes. You don't pay Google to include a job in its job search. Google finds eligible job pages through ordinary crawling or a crawl request from the site that published them.
Free distribution matters when sponsored listings consume a hiring budget before the right applicants arrive. Employers describe that problem in direct terms.
A staffing and recruiting agency owner wrote, "Even using the lowest-budget approach, we average around $800/month on [Indeed]." In the same September 2026 discussion, the owner reported, "Today I got a notice that one of our jobs now requires a $12/day minimum to sponsor. Again, some people may still think that is cheap, but going from $5/day to $12/day is a 140% increase."
Another small staffing company owner wrote in September 2026, "I own a small staffing co and have been spending with Indeed for years. This year I'm already on track to spend 15k which is highest ever."
Those are individual reports, not general pricing data. They still show why organic visibility has value. A job that qualifies for Google for Jobs can receive another source of exposure without a sponsorship charge from Google.
Free doesn't mean automatic. Your page must meet Google's technical and content rules, remain accessible to its crawler, and describe a genuine open position. Google makes the final inclusion and ranking decisions.
What are the two ways onto Google for Jobs?
You have two routes.
Publish each job on your own careers page
Create a separate page for every open role. Add JobPosting structured data that describes the visible job accurately, then make the page available to Google.
This route gives you control over the job description, application method, employer presentation, and removal of closed roles. If you're setting up that destination, it helps to understand what a careers portal is before choosing a platform.
A dedicated page is different from a list of vacancies. Google expects the structured data on the page for one specific job, not on a search results page containing several jobs.
Use a job board that participates
A participating job board can publish the required markup on your behalf. You should still check the resulting job page. The displayed details need to match the structured data, the page must remain open to Google, and applicants must have a way to apply.
A board's paid sponsorship product is separate from eligibility for Google's organic job search. Paying a board doesn't buy placement from Google.
What does Google require in a job posting?
According to Google's Job posting structured data documentation, fetched by the SEO desk on October 18, 2026, every eligible job posting needs these required properties:
titledescriptiondatePostedhiringOrganizationjobLocation
The values must describe the job shown on the page. Don't place one location in the visible description and another in the markup. Don't mark a general careers page as though it were a single vacancy.
Fully remote jobs require different location handling. Google specifies jobLocationType: TELECOMMUTE together with applicantLocationRequirements. The latter tells Google where applicants may work, such as a country or region. Calling a role remote in the title doesn't replace those fields.
Google also recommends several properties that can give it a fuller account of the opening:
validThroughbaseSalaryemploymentTypedirectApply
Recommended doesn't mean disposable. For example, validThrough gives the posting a clear closing point. Once that date passes, either remove the job page, remove its JobPosting markup, or update the date if the role genuinely remains open.
Write the visible copy before the markup. A job description generator can help you prepare the role description, but you should review every requirement, location rule, and compensation detail before publishing.
Why isn't my job showing on Google?
Start with the page itself. Most checks concern placement, accuracy, access, or expiry.
Check where the markup appears. Put JobPosting data on the individual job page. Don't add it to a page that lists several vacancies.
Check every required field. A missing
title,description,datePosted,hiringOrganization, orjobLocationcan make the page ineligible.Compare the markup with the visible job. The structured data must match what a visitor reads. Fix conflicting titles, locations, dates, and employer details.
Remove expired vacancies. A past
validThroughdate signals that the opening has closed. Leaving stale roles online creates a poor applicant experience and may breach Google's job posting policies.Provide a working application route. A job page that describes a role but gives the visitor no way to apply doesn't meet the expected experience.
Remove login barriers. Google needs to read the job page, and a prospective applicant needs to see the description without signing into your hiring system.
Confirm that Google can crawl the page. Review robots rules, page status, canonical tags, and indexing settings. A public page can still be blocked by a technical instruction.
Check regional availability. Google's documentation lists supported regions that include Bangladesh, India, Pakistan, the United Kingdom, North America, Latin America, and others. Availability isn't universal.
Inspect changes made during an ATS move. New URLs, accidental indexing blocks, missing markup, and closed pages can reduce visibility. If traffic changed after a migration, review why applications dropped after an ATS switch alongside the technical checks above.
Google's tools can validate markup, but valid syntax alone doesn't promise inclusion. The job and page must also comply with Google's content policies.
How long does it take to appear?
Google doesn't promise a fixed publication window. Its documentation says "it may take several days after publishing a page for Google to find and crawl it".
You can help discovery by including the job URL in your sitemap and keeping its lastmod value accurate. The date should reflect a meaningful page change, not an automated daily refresh.
When a job closes, update Google promptly. Remove the page or its JobPosting markup, or make sure the validThrough value reflects the closure. A sitemap update can help Google find that change.
Repeated submissions won't guarantee faster inclusion. Google's systems decide when to crawl a URL and whether the job qualifies to appear.
Does apply by email count as a way to apply?
It can. Google's directApply guidance includes instructions that tell a candidate to email the employer. The job page still needs a clear application method and an accurate description of what happens next.
Keep the process specific. State what the applicant should send, which address they should use, and any information required in the subject or message. Test the address before publishing the job.
Email applications can be practical for a small team, but routing matters once several jobs are open. Separate addresses or job codes help you identify which vacancy an application belongs to. They also reduce the manual work of sorting resumes from a shared inbox.
The application route doesn't determine whether Google will include or rank the job. It gives visitors a valid way to respond after they open the listing.
How does Curriculo handle Google for Jobs?
Curriculo provides a public free careers page for your open roles. Every job you publish is structured for Google for Jobs, so it can appear in Google's job search.
Use your own domain for your careers page, free on Starter. Share your job link or careers page anywhere, including LinkedIn.
Every job also gets its own application address in the format [email protected]. That gives applicants a direct email route and helps connect incoming applications with the correct opening.
Google still decides whether a page appears and where it ranks. Curriculo doesn't promise inclusion, position, applicant volume, or a hire. If you're comparing the wider cost and feature tradeoffs, review these free ATS options.
Frequently asked questions
Is Google for Jobs free for employers?
Yes. Google doesn't charge an employer to appear in Google for Jobs. It finds job pages that use eligible JobPosting structured data, either on an employer's careers site or through a participating job board. A board may sell sponsorship separately, but that payment doesn't buy placement from Google. Inclusion and ranking remain Google's decisions.
How do I post a job on Google for Jobs?
Publish a separate, crawlable page for the role and add JobPosting structured data. Include title, description, datePosted, hiringOrganization, and jobLocation. Make sure the visible page matches the markup and provides a working way to apply. You can also use a participating job board that handles the markup.
Do I need a job board to appear on Google for Jobs?
No. You can publish jobs on your own careers page if each role has a dedicated page with valid JobPosting structured data. The page must be open to Google's crawler, show a genuine vacancy, and let visitors apply. A participating job board is an alternative when you don't manage the markup yourself.
Why did my job disappear from Google for Jobs?
Check whether the role expired, the validThrough date passed, the page became blocked from crawling, or required fields changed. Google may also remove a posting that no longer follows its job content policies. Correcting the page can make it eligible again, but Google doesn't guarantee that it will return or keep its prior position.
Can remote jobs appear on Google for Jobs?
Yes. Google's documentation says fully remote jobs should use jobLocationType: TELECOMMUTE and include applicantLocationRequirements. The second property identifies where the employer accepts applicants. The visible description should state the same location limits. Marking a role as remote in its title or prose alone doesn't replace the structured data.
Is the Google Jobs API free?
Google's Indexing API is a crawl hint that asks Google to crawl job posting pages. It isn't a paid job listing service or a way to buy placement in Google for Jobs. Using the API doesn't guarantee that Google will index, display, or rank a job posting.