Can JobPosting markup be added to a job search results page?

Definition: No. Google's JobPosting documentation requires the structured data on the most specific page for one job, alongside the job description that people can read. A job search results page is a list page, so it is outside that documented placement.

Key facts

• Google's JobPosting technical guidelines say to use the most detailed leaf page and exclude pages intended to present a list of jobs, including search result pages.
• The structured data must appear on the same page as the job description that job seekers can read in their browser.
• Google limits JobPosting markup to pages containing a single job posting.
• Google says the page should include required properties, follow its technical and content policies, and be tested with the Rich Results Test.
• Schema.org defines JobPosting as a listing that describes a job opening in a certain organization. Its type page lists properties such as baseSalary and totalJobOpenings.

Why the page type matters

Google's technical guidance for job postings places the markup on the most specific page describing one job and its relevant details. The same guidance says that JobPosting markup must only be used on pages containing a single job posting. A results page can link to individual jobs, but its page purpose remains a list of jobs.

Google also separates page markup from sitemap management. Its sitemap guidance says to exclude search results pages, list pages, and other dynamic pages from the sitemap, while the sitemap URLs for jobs should identify the canonical page for each posting.

What belongs on the individual job page?

Schema.org describes JobPosting as “A listing that describes a job opening in a certain organization.” Its definition includes baseSalary for the base salary of the job or an employee role, and totalJobOpenings for the number of positions open for the posting. These properties describe the job represented by the detail page.

Google's example uses JSON-LD with the JobPosting type and a job title:

{
  "@context": "https://schema.org/",
  "@type": "JobPosting",
  "title": "Software Engineer"
}

The example is only the shape of the markup. Google's required properties documentation also covers the posting date, full HTML description, hiring organization, job location, and job title. The description must represent the job, including responsibilities, qualifications, skills, working hours, education requirements, and experience requirements.

How can you check the implementation?

Google's implementation checklist says to make the page crawlable, add the required and recommended properties, follow the technical and content policies, and validate the code with the Rich Results Test. Its URL Inspection guidance also says the page must be accessible to Google and free of a robots.txt block, a noindex tag, and login requirements.

When a position closes, Google documents three page-level options: populate validThrough with a past value, remove the page so it returns a 404 or 410 status code, or remove the JobPosting structured data. The documentation recommends the Indexing API for informing Google about job URL changes and still recommends a sitemap for site-wide coverage.

Related terms

• Structured data
• JSON-LD
• Canonical URL
• XML sitemap

FAQ

Can you place JobPosting markup on a page that lists several jobs?

No. Google says the markup belongs on a page containing a single job posting. Put the structured data on each job's detail page where its description is readable.

What if the same job has several URLs?

Use canonical URLs on copies of the posting. Google's sitemap guidance also says that each job URL in a sitemap should identify the canonical page for that posting.

What should you do when a job is no longer open?

Set validThrough to a past value, remove the page with a 404 or 410 response, or remove the JobPosting markup. Google lists each option in its removal guidance.

Sources

1. Google Search Central, "Job posting (JobPosting) structured data for Job Search", 8 September 2026
2. Schema.org, "JobPosting", 16 September 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer