Inferensys

Glossary

JobPosting

A Schema.org type used to markup a job listing, providing structured details about the hiring organization, job location, employment type, and base salary, which is required for Google's job search experience.
Stylish WeWork-like workspace with hot desks and document wall, professional searching through enterprise knowledge base on a mounted ultrawide display, warm industrial pendants overhead.
SCHEMA.ORG TYPE

What is JobPosting?

A structured data vocabulary for defining employment listings with machine-readable precision.

JobPosting is a Schema.org structured data type used to markup an employment listing, providing search engines with explicit, machine-readable details about a hiring organization, job location, employment type, and base salary. It is the required schema for inclusion in Google's dedicated job search experience, enabling rich result displays that surface critical information directly to candidates.

Proper implementation requires nesting several dependent types, including MonetaryAmount for salary specification and Place for geographic location. Google mandates specific properties—datePosted, hiringOrganization, title, and validThrough—and enforces strict guidelines against indexing expired or misleading listings, making accurate markup essential for algorithmic trust and visibility in the job-seeking ecosystem.

STRUCTURED DATA FOR RECRUITMENT

Key Features of JobPosting Schema

The JobPosting schema type enables search engines to parse and display job listings with rich attributes, making them eligible for Google's dedicated job search experience.

01

Base Salary Requirement

Google requires the baseSalary property for job listings to appear in its job search experience. This structured field must specify:

  • A value (numeric or range)
  • A currency code (ISO 4217, e.g., USD)
  • A unitText indicating the pay period (HOUR, MONTH, YEAR)

Without valid salary data, the listing is ineligible for enhanced display in Google for Jobs.

02

HiringOrganization Entity

The hiringOrganization property links the job to an Organization entity, which should be a fully defined object rather than a plain string. Best practices include:

  • Providing the organization's name and sameAs URL to a canonical profile (e.g., LinkedIn, Crunchbase)
  • Including the company logo for brand recognition in search results
  • Nesting the organization's address if the job is at a specific office

This entity linkage strengthens the employer's presence in the Knowledge Graph.

03

EmploymentType Classification

The employmentType property categorizes the role using a controlled vocabulary. Common values include:

  • FULL_TIME
  • PART_TIME
  • CONTRACTOR
  • TEMPORARY
  • INTERN
  • VOLUNTEER
  • PER_DIEM

Accurate classification ensures the listing surfaces in filtered searches and improves match quality for candidates using Google's job search filters.

04

JobLocation and Remote Roles

The jobLocation property defines where the work is performed using a Place type. For physical locations, include a PostalAddress with addressLocality, addressRegion, and addressCountry. For remote positions, use the TELECOMMUTE value for jobLocationType:

  • jobLocationType: "TELECOMMUTE" signals a fully remote role
  • Hybrid roles can specify multiple location entries
  • Geo-coordinates via latitude and longitude improve local search relevance
05

ValidThrough Expiration

The validThrough property specifies an ISO 8601 date after which the job listing is no longer active. This is critical for:

  • Preventing expired listings from appearing in search results
  • Maintaining data quality and user trust
  • Automating listing lifecycle management

Google recommends setting this date accurately and removing or updating the markup once the position is filled to avoid candidate frustration.

06

Direct Apply and Indexing API

For listings to appear in Google's job search, the page must either:

  • Be directly crawlable without login walls
  • Use the Indexing API to push updates immediately

Additionally, the directApply option can be signaled to indicate candidates can apply without redirection. Google's job search guidelines require the structured data to match the visible content on the page exactly—any discrepancy triggers a manual action.

JOBPOSTING SCHEMA

Frequently Asked Questions

Essential answers to common questions about implementing the Schema.org JobPosting type for Google's job search experience and enhanced visibility in search results.

JobPosting is a Schema.org structured data type used to markup a job listing on a webpage, providing machine-readable details about the hiring organization, job location, employment type, and base salary. When implemented correctly using JSON-LD, this markup enables your job listings to appear in Google's dedicated job search experience, which aggregates listings from across the web into a unified, interactive interface. The schema works by defining a set of required and recommended properties—such as hiringOrganization, jobLocation, and baseSalary—that search engines parse to understand the specifics of the role. Google explicitly requires baseSalary for job listings in certain regions, making JobPosting one of the few Schema.org types with mandatory property enforcement for rich result eligibility. The structured data also powers features like the ability to filter by salary range, location proximity, and employment type directly within search results, significantly improving discoverability for qualified candidates.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.