[ad_1]
Google up to date their job posting structured information steerage with the intention to change the necessities of the way to finest hold Google notified of latest webpages and modifications to current webpages.
Google Job Posting Structured Knowledge Steering
Google’s job posting structured information steerage is designed to assist publishers grow to be eligible for enhanced visibility in Google Search outcomes by means of interactive job listings in search. It additionally offers an outline of the method of including, testing and sustaining job posting structured information.
Of specific significance is the power to inform Google of latest job posting webpages and modifications to current pages, which advantages publishers by having essentially the most related and helpful job postings accessible within the SERPs.
Modifications In The Steering For Notifying Google
The change within the steerage was to make clear how publishers can notify Google of modifications and new webpages. There doesn’t appear to be a change within the steerage of what to do however reasonably there’s a change in how using sitemaps is emphasised and inspired.
Within the earlier model of the steerage Google inspired customers to depend on the Indexing API “as a substitute of sitemaps” to instantly notify Google of pages that want instant crawling.
The earlier steerage acknowledged:
“Hold Google knowledgeable by doing one of many following actions:
For job posting URLs, we suggest utilizing the Indexing API as a substitute of sitemaps as a result of the Indexing API prompts Googlebot to crawl your web page before updating the sitemap and pinging Google. Nevertheless, we nonetheless suggest submitting a sitemap for protection of your total website.”
The advice to make use of the Indexing API “as a substitute of sitemaps” appears to discourage using sitemaps, although the following sentence recommends submitting a sitemap for all the website.
The up to date steerage fixes the looks of a battle between the 2 sentences by changing the phrase “as a substitute of” with the phrase “and”.
It now reads:
“Hold Google knowledgeable by utilizing the Indexing API and submitting a sitemap. For job posting URLs, we suggest utilizing the Indexing API as a substitute of sitemaps as a result of the Indexing API prompts Googlebot to crawl your web page sooner. Use the Indexing API to inform Google of a brand new URL to crawl or that content material at a URL has been up to date.”
The up to date steerage now recommends utilizing each the Indexing API and a sitemap, whereas clarifying that the Indexing API is quicker.
There are comparable modifications to 2 extra passages additional down the web page along with eradicating all mentions of “pinging” Google about modifications to the sitemap with a GET request.
This assertion:
“Hold Google knowledgeable by doing one of many following actions:”
Was modified to this:
“Hold Google knowledgeable of modifications:”
That change makes it clearer that publishers ought to nonetheless use a sitemap whereas additionally recommending using the Indexing API for quick crawling.
Google additionally eliminated the advice to make use of a GET request for getting the sitemap crawled from the steerage:
“Should you’re not utilizing the Indexing API, submit a brand new sitemap to Google by sending a GET request to the next URL:
https://www.google.com/ping?sitemap=https://www.instance.com/sitemap.xml”
Learn the up to date Job Posting Structured Knowledge steerage right here:
Job posting (JobPosting) structured data for Job Search
Featured Picture by Shutterstock/object_photo
[ad_2]
Source link
