Job Posting Schema: Get Your Hiring Pages Into Google Jobs Results

JobPosting schema makes your open roles eligible for Google for Jobs. Required properties, implementation steps, and freshness rules for service businesses.

# Job Posting Schema: How Service Businesses Get Hiring Pages Into Google Jobs Results Service businesses are hiring constantly — technicians, dispatchers, drivers, office staff — and most of them post open roles on a careers page that Google barely notices. Meanwhile, competitors with properly marked-up job postings show up in a prominent Google Jobs results box with the company logo, salary range, and a direct apply link. The difference is not budget or brand. It is a small block of structured data called JobPosting schema, and any business can add it in an afternoon. ## What JobPosting schema is Schema markup is a standardized vocabulary that tells search engines what a page means, not just what it says. JobPosting schema tells Google: this page describes a specific open job, here is the title, here is where the work happens, here is the pay range, and here is how to apply. When Google understands a posting, it can include it in Google for Jobs — the dedicated job-search experience that appears above regular results for hiring-related searches. A plain-text careers page forces Google to guess which parts are job titles, which are locations, and whether the role is even still open. Markup removes the guesswork. Pages with valid JobPosting schema are eligible for the enriched Jobs display; pages without it are not, no matter how well written. ## Why it matters for service businesses specifically Service businesses hire locally and urgently, which is exactly where Google for Jobs shines. When someone searches for technician or dispatcher roles near them, Google prioritizes postings with complete structured data: clear location, employment type, and pay information. National job boards already do this well, which is why they dominate hiring searches. A local company with correct markup can appear right alongside them — often with an advantage, because Google favors nearby results for local-intent job searches. There is a second benefit owners overlook: trust. A posting that shows a real pay range, a real address, and a direct apply path converts far more applicants than a vague "call for details" ad. Technicians comparing offers notice which employers are transparent. For broader context on getting found locally, see our guides to [Google Business Profile optimization beyond reviews](https://seodone.ai/blog/google-business-profile-optimization-beyond-reviews-map-pack) and [how service businesses show up in AI search results](https://seodone.ai/blog/google-ai-overviews-how-service-businesses-show-up-in-ai-search). ## The properties Google actually needs A valid job posting needs a core set of required properties. The job title must be the actual role — not marketing copy. The hiring organization needs a name and ideally a logo. The job location must be a real address for on-site roles; for roles performed at customer sites across a service area, use the business address plus a clear description of the service area in the posting text. The description itself should be the full role description in HTML, and the posting needs a publication date. Beyond the required fields, several recommended properties dramatically improve performance. Salary information with a stated range is the single biggest click-through driver on job results — postings with pay shown consistently attract more applicants. Employment type (full-time, part-time, contractor), a valid-through date showing when applications close, and direct-apply instructions all strengthen the listing. An identifier unique to each posting helps Google track the role across reposts. ## Implementation, step by step First, give every open role its own dedicated page with its own URL. Google indexes jobs as individual pages — a single careers page listing six roles in plain text cannot carry six separate JobPosting blocks effectively. One role, one page, one markup block. Second, add the structured data as a JSON-LD script in the page head. JSON-LD is Google's preferred format: it sits apart from the visible content, so it cannot break your layout, and it is easy to validate and update. Keep the visible page content and the markup consistent — the title, location, and description in the markup must match what applicants see on the page. Mismatches are one of the most common reasons postings get dropped. Third, validate before publishing. Run every posting through Google's Rich Results Test and fix all errors. Warnings for missing recommended fields are worth fixing too, especially missing salary data. Recheck the page after any site update or redesign — templates change, and markup silently breaks more often than anyone expects. ## Keeping postings fresh and honest Google actively polices job markup quality, and stale postings are the fastest way to lose eligibility. Remove the markup — or the page — the day a role is filled. A posting that stays live for months after hiring signals low quality, and expired roles collecting applications damage your reputation with applicants. Set a valid-through date on every posting and review open roles on a schedule. If a role is genuinely evergreen — many shops are always hiring technicians — refresh the publication date and description periodically rather than letting the same posting age indefinitely. And never mark up roles you are not actually hiring for; bait postings can get a whole site excluded from Jobs features. ## Measuring whether it works Track three things. First, indexation: check whether your postings appear in Google for Jobs for relevant local searches within a few weeks of publishing. Second, applicant source: ask every applicant where they found the role, or use distinct apply URLs per channel, so you can see what the Jobs box contributes. Third, time-to-fill: compare how long roles stay open before and after adding markup. Faster fills at lower job-board spend is the return on this work. Job Posting schema is one of the rare SEO tasks with a clear cause and effect: add valid markup to real open roles, and your hiring pages become eligible for the most prominent hiring placement in search. For service businesses competing for scarce skilled labor, that visibility is worth an afternoon of implementation.