When publishing a job posting, add JobPosting structured data to the detail page for a single vacancy and ensure the markup matches the page content. After testing the markup and checking that Google can access the page, use the Indexing API to notify Google of additions or changes, and submit a sitemap as well. When recruitment ends, update or remove the expired job posting’s markup, or remove the page, and notify Google. These steps help Google keep track of vacancies, but do not guarantee that related features will appear in search results.
Choose the right page before adding job posting markup
JobPosting belongs on a detail page that describes a single vacancy and provides the full job description. It must not appear on job listing or search results pages. If the same vacancy has multiple URLs, specify a canonical URL for each page.
- Add the required properties; recommended properties can provide additional information and improve the experience for job seekers.
- All information in the markup must be visible on the page and accurately reflect the vacancy. For example, if the markup includes compensation, the page must provide that information too; the title value must match the job title on the page.
- Provide a complete job description and a way to apply. Do not require users to log in to view the job description or charge job seekers a fee.
Test before publishing and check rendering after deployment
First, validate the code using the Rich Results Test. Then deploy a small number of pages and use the URL Inspection tool to see how Google renders them. Confirm that the job information is visible and that the pages are not blocked from crawling by robots.txt, excluded from indexing by noindex, or restricted by a login requirement.
Testing is no substitute for reviewing the content. Fake vacancies, misleading descriptions, or improper use of markup do not necessarily involve syntax errors, so tools may not detect these problems. After publishing, you also need to allow time for Google to recrawl and index the pages; Google may take several days to find and crawl them.
Notify Google when you update the content
When details such as the job title or compensation change, update both the page and the markup to keep them consistent. For new or changed job posting URLs, Google recommends using the Indexing API rather than relying solely on a sitemap, because the API can prompt Googlebot to start crawling sooner. Submitting a sitemap is still recommended to help Google crawl the entire site.
- The job posting sitemap should list canonical job posting URLs that Googlebot can access, excluding search results pages, listing pages, and other dynamic pages.
- Provide an accurate lastmod whenever possible, reflecting when the page content last changed. Do not mark unchanged pages as newly updated.
Handle expired job postings when recruitment ends
When a vacancy is no longer open for applications, you must take one of the following actions rather than simply waiting for Google to discover that it has expired:
- Set validThrough to a date in the past.
- Remove the entire page and return a 404 or 410 status code.
- Remove the JobPosting structured data from the page.
Afterward, use the Indexing API to notify Google and continue to submit a sitemap. Failure to handle expired job postings promptly may result in a manual action.
Job posting structured data: perspectives from across the web
How should locations be marked up for work-from-home jobs?
If a job allows employees to work from home without visiting a physical workplace, but restricts where they can be based, you can use jobLocationType to mark it as a work-from-home role. Use applicantLocationRequirements to specify the permitted locations, including at least one country or region. If there is no physical work location, jobLocation is not required; if you use that property, you must specify addressCountry.
How should you troubleshoot a job posting that does not appear in the job search experience?
First, review structured data errors and the Unparsable structured data report, then check whether the content complies with the guidelines. If you receive a manual action, use the report in Search Console to address the issues. Errors are not necessarily syntax issues, so testing tools may not detect them all. If a page receives a structured data manual action, its markup will be ignored, but the page will still appear in Google Search results.
What can you do if a job posting displays the wrong company logo?
You can specify the correct logo using hiringOrganization.logo in the structured data or suggest an edit to the knowledge panel. Google's documentation states that updating structured data is generally more efficient. Updating the knowledge panel may take longer, but it gives the organization greater control over how it appears in search results. When a third-party job site supplies a logo, Google may still choose the logo from the knowledge panel.
What markup requirements apply when work experience is accepted in place of education?
You can set experienceInPlaceOfEducation to True to indicate that the vacancy accepts work experience in place of educational qualifications. When using this setting, you must also include both experienceRequirements and educationRequirements so that the markup contains the corresponding experience and education requirements.
References
- 產品子類結構化資料 (ProductGroup、Product) | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How should you troubleshoot a job posting that does not appear in the job search experience?
- 瞭解徵人啟事結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How should locations be marked up for work-from-home jobs?; What can you do if a job posting displays the wrong company logo?



