Why is JobPosting Schema Critical for Hiring?
Recently, an IT company’s HR director reached out to us: job postings had been sitting on the site for weeks with zero applications. Analysis revealed a missing JobPosting Schema. After implementation, applications increased 2.5x in the first month. On average, our clients see a 40% increase in applications after setup. Savings on vacancy advertising reach up to 150,000 rubles per year — vacancies find candidates through Google for Jobs on their own. Sites with markup get 2x more traffic from search compared to those without. The only guaranteed way to appear in Google for Jobs is to implement JobPosting Schema.
What Problems Does Job Markup Solve?
- Low visibility. Without markup, Google does not highlight the vacancy in a special block. Research shows: sites with markup get 2x more search traffic. One of our clients increased applications by 80% after implementation.
- Data errors. Often the wrong employment type is used, or validThrough is missing, causing jobs not to be indexed or shown expired. In one project, we found 40% of jobs had invalid markup.
-
Duplicated markup. Listing pages (e.g.,
/career) must never have JobPosting Schema — this is a gross error leading to penalties. Each job must have its own page.
How We Do It: A Real-World Example
Consider a real task: set up markup for a Senior PHP Developer (Laravel) position. Stack: Laravel 11, MySQL, Redis, Docker. We generate JSON-LD directly in Blade templates. The average salary for a Senior PHP developer in Moscow is 250,000 rubles per month, important for the baseSalary field.
Example JSON-LD for a job posting
{ "@context": "https://schema.org", "@type": "JobPosting", "title": "Senior PHP Developer (Laravel)", "description": "<p>We are looking for an experienced PHP developer to work on a high-load SaaS project. Stack: Laravel 10, PostgreSQL, Redis, RabbitMQ.</p><ul><li>Backend feature development</li><li>Code review</li><li>Participation in architectural decisions</li></ul>", "employmentType": "FULL_TIME", "hiringOrganization": { "@type": "Organization", "name": "TechSoft", "sameAs": "https://technosoft.ru", "logo": "https://technosoft.ru/logo.png" }, "jobLocation": { "@type": "Place", "address": { "@type": "PostalAddress", "streetAddress": "16 Lva Tolstogo St.", "addressLocality": "Moscow", "addressRegion": "Moscow", "postalCode": "119021", "addressCountry": "RU" } }, "jobLocationType": "TELECOMMUTE", "baseSalary": { "@type": "MonetaryAmount", "currency": "RUB", "value": { "@type": "QuantitativeValue", "minValue": 200000, "maxValue": 300000, "unitText": "MONTH" } } } In a real project, add required fields datePosted, validThrough and a unique identifier. Our approach: data is taken from the Vacancy model and serialized into JSON-LD. Validation at the DTO level — for example, if salary_from is null, we omit the value field. This prevents errors.
How to Choose the Right employmentType?
Employment type affects filters in Google Jobs. A wrong value means your job won’t reach the right audience. Here is a comparison:
| Value | When to use | Typical mistake |
|---|---|---|
FULL_TIME |
Full-time, 40 hours | Confused with CONTRACTOR for staff |
PART_TIME |
Part-time, 20 hours | Specifying CONTRACTOR for part-time jobs |
CONTRACTOR |
Freelance, project-based | Forgetting to include duration in description |
TEMPORARY |
Seasonal temporary work | Using FULL_TIME for seasonal projects |
INTERN |
Internship | Omitting training information |
VOLUNTEER |
Unpaid volunteer work | Including a salary — this is an error |
Which Required Fields Must Be Checked?
Before publishing the markup, ensure all required fields are correct and match the page data. Here is a table with validation rules:
| Field | Type | Example | Note |
|---|---|---|---|
title |
Text | "Senior PHP Developer (Laravel)" | Must match the page heading |
description |
HTML | " We are looking... " |
Minimum 50 characters, no empty tags |
datePosted |
Date | "YYYY-MM-DD" | Publication date in ISO 8601 |
validThrough |
DateTime | "YYYY-MM-DDThh:mm:ss" | Mandatory, otherwise job never expires |
employmentType |
Enum | "FULL_TIME" | One of schema.org allowed values |
hiringOrganization.name |
Text | "TechSoft" | Company name |
jobLocation.address.addressLocality |
Text | "Moscow" | City for filtering |
baseSalary |
MonetaryAmount | see example | Specify range or exact value |
What Google Requirements Must Be Met?
-
descriptionmust contain the full job details, not a summary. Otherwise Google will reject the markup. -
validThroughis mandatory. If omitted, the job might stay in the index indefinitely. Provide the closing date. - Data in the markup must match what the user sees on the page. If you specify a salary of 200,000–300,000 but the page says "from 150,000", expect penalties.
- Do not tag aggregate pages (job lists). Only individual job pages.
Google Developers: Job Posting structured data
Our Process
- Analysis — study the current job page structure, CMS, templates.
- Design — develop a data schema and field mapping.
- Implementation — write code to generate JSON-LD (in any language: PHP, Python, JS).
- Testing — validate via Schema Markup Validator and Google Search Console.
- Deployment & monitoring — go live, check coverage in GSC.
Estimated Timeline
Setting up job microformatting takes from 1 to 3 business days depending on template complexity. If integration with an ATS is required, it may extend to a week. The cost is calculated individually.
What's Included
- Full audit of existing markup (if any)
- Creating a module to generate JobPosting Schema for your CMS
- Setup on test and production servers
- Verification in Google tools
- Documentation for your developers
- One month of support after launch
Typical Implementation Mistakes
Forgetting validThrough, using wrong employmentType, using a non-standard currency format (e.g., "RUR" instead of "RUB"), writing invalid HTML in description, or assigning the same identifier to different jobs. Any of these errors can lead to markup rejection by Google. Proper implementation avoids these issues and can save up to 200,000 rubles per year on advertising. Contact us for a free audit — no obligation.
Leave a request for a consultation to discuss your project.