Complete Guide

What Is JobPosting Schema and Why Does It Matter for Recruitment Websites?

JobPosting schema structured data describing a job vacancy on a recruitment website

JobPosting schema is a type of structured data that describes a job vacancy in a format search engines can read. It sits alongside the visible job description on the page and spells out the key facts, such as the job title, employer, location, employment type, date posted and expiry date, in a standard, machine-readable form.

That is useful, but it has limits. Valid structured data does not guarantee that Google will index a page, rank it or show it in Google for Jobs. This guide explains what JobPosting schema is, how it works, which properties matter, how to check it and where it can go wrong, so you can judge what it can and cannot do for a recruitment website.

What Is Structured Data?

A visitor to a job page sees a job title, a company, a location, an employment type and a description. A search engine sees the HTML behind the page and has to work out which text is the title and which is the location. Structured data removes some of that guesswork by labelling each fact.

Google’s introduction to structured data describes it as a standardized format for providing information about a page and classifying its content. It can be written in JSON-LD, microdata or RDFa, and Google generally recommends JSON-LD where your setup allows it, because it is the easiest to implement and maintain. JSON-LD usually sits in a script block in the page, separate from the visible text.

Structured data does not replace visible content. It describes content that is already on the page, and the two must agree.

What Is JobPosting Schema?

JobPosting is the schema.org type for a job vacancy, and it is the type Google documents for job listings. It describes one specific opening: what the job is, who is hiring, where it is based, when it was posted and, if relevant, when it closes. Google can use this information to understand the vacancy and, when other requirements are met, to consider the page for job search experiences.

The markup should describe a genuine, available vacancy. It belongs on an individual job detail page, not on a careers landing page that lists several jobs. Google’s documentation says JobPosting structured data must only be on a page dedicated to a single job, and it treats markup on a list page as a policy problem.

How JobPosting Structured Data Works

  1. A company publishes a job page with the vacancy details visible to visitors.
  2. The page also carries JobPosting structured data that describes the same vacancy.
  3. Search engines can read that data when they process the page.
  4. Google may then check the page against its technical and content requirements for job search features.

None of this forces Google to show the job. The page still has to be found, crawled and indexed first, which our guide on how Google finds job listings on your website explains. Structured data is information you offer, not an instruction Google must follow.

Important JobPosting Properties

Google’s JobPosting structured data documentation lists the properties it supports. The table below summarizes the main ones and how Google treats them. Requirements can change, so check the current documentation before you implement anything.

PropertyWhat it describesGoogle’s treatment
@context and @typeDeclares the schema.org vocabulary and the JobPosting typeNeeded for the markup to be valid JobPosting data
titleThe title of the job, not the postingRequired
descriptionThe full job description in HTMLRequired
datePostedWhen the employer posted the job (ISO 8601)Required
hiringOrganizationThe company offering the jobRequired
jobLocationThe physical place where the employee will workRequired for jobs at a physical location
validThroughWhen the posting expires (ISO 8601)Required if the posting has an expiration date
employmentTypeFull time, part time, contractor and similar valuesRecommended
jobLocationTypeTELECOMMUTE for jobs that are 100% remoteRequired for 100% remote jobs
applicantLocationRequirementsWhere applicants may be located for a remote jobRecommended, and needed for some remote jobs
baseSalaryThe base pay as stated by the employerRecommended

This is a summary, not a copy of the specification. Several properties have extra rules, such as the country that jobLocation must include and the exact salary format, so use Google’s page for the details.

Google separates the properties into groups, and the difference matters:

  • Required properties must be present for the page to be eligible for the job experience.
  • Recommended properties add information that can improve the experience, but a page can still be eligible without them.
  • Conditional properties become required in particular situations. For example, validThrough is required when a posting has an expiration date, and jobLocationType is required when a job is 100% remote.
  • Optional business information, such as an employer logo or an internal job code, is yours to add if it helps.

Missing a required property can stop a page being eligible. Missing a recommended property usually just makes the data less complete. Do not copy a fixed list from an old article: Google’s current documentation is the reference, and it can change.

Why Structured Data Must Match Visible Job Content

The data you provide has to describe what a visitor can actually see. That means the job title, employer, description, location, employment type, salary, closing date and the ability to apply should all agree between the page and the markup. Google’s guidance says information in the markup must be visible on the job page. Salary that appears in the markup but not on the page is one of its examples of a problem.

Typical risks include:

  • Markup that describes information visitors cannot see.
  • Incorrect or outdated details.
  • Reusing the same markup for unrelated jobs.
  • Marking a closed vacancy as open.
  • Adding JobPosting data to a page that is not a genuine job listing.

If the markup and the page disagree, Google may treat the page as having a structured data problem and may not use the data.

JobPosting Schema and Google for Jobs

JobPosting schema can make a job page eligible for Google’s job search experiences when the page also meets the technical and content requirements. It is an enabler, not a switch. Several things are separate, and none guarantees the next:

  • Valid markup: the data is correctly formed.
  • Eligibility: the page meets the requirements for the job feature.
  • Crawling: Google has requested the page.
  • Indexing: Google has stored the page.
  • Appearance: the job is actually shown to someone searching.

You can do everything correctly and still not see your job in a particular result. Google decides what to index and display.

How to Validate JobPosting Structured Data

A practical check takes a few minutes with Google’s Rich Results Test:

  1. Pick a live, individual job detail page.
  2. Enter its URL in the Rich Results Test, or paste the code you want to check.
  3. Confirm that job posting data was detected.
  4. Read every error and warning the tool reports.
  5. Compare the detected values with what the page shows.
  6. Fix the issues and test again.

A clean result shows that Google can read the markup. It does not show that the page is indexed, that it will rank or that it will appear in job search. For that, check the page with the URL Inspection tool in Search Console.

Common JobPosting Schema Errors

ProblemHow to correct it
Missing required propertiesAdd every required property from Google’s current documentation
Invalid date formatUse ISO 8601 dates, such as 2026-11-14
Unrecognized employment typeUse one of Google’s supported values, such as FULL_TIME
Wrong or incomplete job locationDescribe the real work location and include the country
Missing employer detailsProvide the company name as hiringOrganization
Markup that differs from the pageMake the visible content and the markup agree
Expired vacanciesRemove or update the page, and set validThrough correctly
Remote work marked up incorrectlyUse remote properties only for jobs that are 100% remote
Markup on a listing pagePlace JobPosting data only on single job pages

Error messages and labels in the testing tool can change, so read what the tool reports for your own page rather than relying on a list in an article.

JobPosting Schema for WordPress Websites

On WordPress there are four broad routes: writing JSON-LD by hand, using an SEO or structured data plugin that supports JobPosting, using a recruitment plugin that generates it, or custom development. Whatever you choose, inspect the generated output. Installing a plugin does not prove the markup is complete or correct, because it depends on the information you enter and on how the theme and other plugins behave.

Watch for duplicates too. If two plugins each output a JobPosting for the same page, the page can end up with conflicting entities, so test after any change to your theme or plugins. Our overview of making WordPress job listings SEO-friendly and the comparison of a WordPress job board and a recruitment plugin help you choose.

Where CMAA Recruit Fits

CMAA Recruit is a WordPress recruitment plugin for publishing jobs on your own website (read the overview). Based on the current Free plugin code, on each single job page it outputs JobPosting structured data as JSON-LD, built from the job’s own details, plus separate BreadcrumbList data.

The markup can include the job title, the visible description, the date posted, the page URL, a direct apply flag, the hiring organization (the company name, website and logo from the plugin’s General Settings, or the site name if none is set), the employment type, a job code as an identifier, and an image. A validThrough date is included only when you set an expiry date, and baseSalary is included only when salary values are entered and the salary is not set to hidden.

Several properties depend on how you fill in the job. The location comes from a free-text Location field, so write it as a city followed by a country, because Google requires a country. A job whose work mode is remote is marked as fully remote. An employment type that the plugin does not recognise is sent as OTHER. Salary is expressed per year. Check the output on a real job page, and do not assume it guarantees indexing, rich results or Google for Jobs placement.

Publish structured job listings through your WordPress website

Explore how CMAA Recruit supports job publishing and recruitment management in WordPress.

Frequently Asked Questions

What does JobPosting schema do?

It describes a job vacancy in a standard format so search engines can understand its key facts. It can make a page eligible for job search features, but it does not force indexing or display.

Is JobPosting schema required for Google for Jobs?

Google’s documentation says you must include the required properties for your content to be eligible for the job experience. In practice that means adding valid JobPosting data, along with meeting the other requirements.

Does JobPosting schema improve Google rankings?

Google does not present it as a ranking boost. Its purpose is to help Google understand the job and make the page eligible for job search features. Treat any claim of a ranking improvement with caution.

Should every job listing have its own JobPosting markup?

Yes, each individual job detail page should describe its own vacancy. Do not put JobPosting markup on a careers page that lists several jobs, and do not reuse one block of markup for different jobs.

Can WordPress generate JobPosting structured data?

WordPress core does not do this for job listings by itself. An SEO plugin, a recruitment plugin or custom code can generate it, and you should check the output either way.

How do I test whether my job schema is valid?

Use Google’s Rich Results Test on a live job page, review the errors and warnings, and compare the result with the visible page. Then use Search Console to check indexing.

Final Takeaway

JobPosting schema helps search engines understand an individual vacancy, but it only works when it is accurate, matches the visible job page and follows Google’s current requirements. Validate it, keep it up to date, and remember that valid markup is a starting point, not a promise of indexing or placement.

Compare WordPress recruitment capabilities for publishing jobs

Compare the Free and Pro capabilities against your website's job publishing and application management needs.

CMAA Softwares

About CMAA Softwares

CMAA Softwares builds practical software for SMEs and professional firms, grown out of problems solved first inside CMAA Advisors' own payroll, compliance, and recruitment desks. CMAA Recruit is our recruitment ATS plugin for WordPress. Learn more about us.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top