The structured-data playbook that gets your job ads into Google's jobs box, so high-intent candidates find your roles first.
30-day free trial. No setup fees, no long-term contracts.
The channel most recruiters miss
When a candidate types a job title into Google, the first thing they see is not a job board. It is the enriched jobs box Google builds from structured data it reads across the web, including from careers pages like yours. Land there and your role shows up in front of active searchers at the exact moment they decide to look, with no per-click bill.
Here is the catch that trips up most teams: eligibility is not a matter of great copy or a big spend. It is decided by JobPosting structured data on a page Google can crawl. Get the fields right and the posting can appear. Miss one required field and it never shows, no matter how good the ad reads. This guide walks the exact markup, the page requirements, and the mistakes that keep job ads invisible, then shows how to ship rankable postings at scale.
Why it is worth winning
When someone searches "warehouse jobs near me" Google shows an enriched jobs box at the top of the results, ahead of the paid board listings. A posting that qualifies lands in front of high-intent searchers without a per-click bill.
People type a job title into Google when they are ready to look right now. Ranking there puts your role in front of active candidates the moment they decide to search, not days later in a newsletter.
Google can index the posting directly from your own domain. That means the click goes to your branded application, keeps the candidate in your funnel, and never rents your traffic back to you.
Eligibility is decided by structured data on the page, not ad spend. Mark up the posting correctly and it can appear. Miss a required field and it never shows, no matter how good the copy is.
Anatomy of a rankable job ad
Each open role needs its own indexable page that Googlebot can reach without a login or a form wall. A branded Apply Here page per role is the cleanest way to give every posting a real, permanent home on your own domain.
The structured data has to describe exactly what a human sees. If the schema says one salary and the page shows another, Google flags a mismatch and drops the listing. Generate the markup from the same source as the copy.
Most job searches happen on a phone. The page must load quickly, read cleanly on mobile, and carry an accurate datePosted. Stale or slow pages lose to fresher, faster competitors in the same jobs box.
The JobPosting checklist
Mark up the required fields to be eligible. Add the recommended ones to win the click. Make the markup match the visible page every time.
title description datePosted hiringOrganization jobLocation jobLocationType baseSalary employmentType validThrough identifier A worked example
Below is an illustrative JobPosting block for a single warehouse role at one location. Notice that every value would also appear in the visible page text, the date is real and recent, and the salary carries a currency and a unit. This is example markup, not live data.
{
"@context": "https://schema.org",
"@type": "JobPosting",
"title": "Warehouse Associate",
"description": "<p>Full job description, responsibilities, and how to apply...</p>",
"datePosted": "2026-02-18",
"validThrough": "2026-03-20",
"employmentType": "FULL_TIME",
"identifier": {
"@type": "PropertyValue",
"name": "ATS Mako",
"value": "REQ-4821"
},
"hiringOrganization": {
"@type": "Organization",
"name": "Your Company",
"sameAs": "https://yourdomain.com",
"logo": "https://yourdomain.com/logo.png"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"streetAddress": "1200 Distribution Way",
"addressLocality": "Columbus",
"addressRegion": "OH",
"postalCode": "43201",
"addressCountry": "US"
}
},
"baseSalary": {
"@type": "MonetaryAmount",
"currency": "USD",
"value": {
"@type": "QuantitativeValue",
"minValue": 42000,
"maxValue": 52000,
"unitText": "YEAR"
}
}
} The playbook
Ranking starts with a real page Google can crawl. Publish each opening on a dedicated Apply Here page on your own domain, with your logo, colors, and a simple resume submission flow. One role, one URL, no board in between.
Title, description, datePosted, hiringOrganization, and jobLocation are non-negotiable. A single missing required field makes the posting ineligible. Standardize the fields so no recruiter can publish an incomplete ad.
Never advertise ten cities on one page. Google needs a distinct posting and postal address for each site. Per-location Apply Here pages give franchises and multi-brand operators a clean posting for every office.
The recommended fields decide whether you win the click. A visible salary range, an employmentType filter match, and a validThrough date make the listing richer, more compliant, and cleaner when the role fills.
Run every posting through Google's Rich Results Test and keep an eye on the Search Console job-posting report. Fix warnings before candidates ever see the page, not after the role sits invisible for a week.
Ranking is only half the win. When the candidate clicks through, pull them straight into one pipeline, fire an on-brand first touch, and answer fast. Speed after the click is what turns a Google impression into a hire.
Avoid these
If Googlebot cannot reach the posting without submitting a form or signing in, it cannot index it. Every role needs a public, crawlable URL. A gated careers portal is invisible to Google for Jobs.
Leave out datePosted, jobLocation, hiringOrganization, title, or description and the listing is disqualified with no warning to the candidate. Required means required, and one gap sinks the whole posting.
Bundling several cities onto a single ad confuses the location signal, so none of them rank well. Split them. Each city gets its own posting and its own full postal address.
When the markup claims a salary, title, or location the visible page never shows, Google treats it as a mismatch and drops the listing. The structured data and the human-readable copy must agree.
Expired jobs that stay indexed become ghost postings. They frustrate candidates, hurt your standing, and can get your postings demoted. Set a validThrough date and expire roles the day they fill.
Ship rankable postings at scale
Google can only rank a job it can crawl. ATS Mako gives every opening its own Apply Here page on your own domain, with your logo, your colors, and a simple resume submission flow. One role, one URL, no board in between and no traffic rented back to you.
For franchises and multi-brand operators, per-location pages keep each posting clean: one role and one full postal address at a time, exactly how Google wants multi-location hiring structured. Update your template once and it deploys everywhere.
Ranking is only half the win. When a candidate clicks through from Google, they land in one pipeline where a status-triggered first touch and two-way SMS keep them engaged, so a search impression turns into a conversation and a hire. From first touch to offer letter, fast, automated, and on your brand.
Frequently asked
Branded, crawlable job pages with the structured data built in, plus instant follow-up the moment a candidate clicks.
Designed for speed. Built for scale.