Indexing API Guidelines to follow:

Updating/Removing a job posting via indexing API is a 2-step process:

Since job sites have a high rate of updates/removals, we recommend using the indexing API for informing Google to do a fresh page crawl, which can lead to higher quality user traffic.

For job posting URLs, we recommend using the Indexing API to send updates/removals instead of sitemaps because the Indexing API prompts Googlebot to crawl your page sooner than removing the URL from the sitemap and pinging Google. However, we still recommend having keeping your sitemap updated with only live job postings so that crawlers can use it as a reference in case if your requests return any API errors

Check the troubleshooting guidelines for common issues and the list of manual actions before verifying these points and submitting your reconsideration request:

Use the URL Inspection tool to find any structured data error or indexing issues: 

Note: We suggest removing building or floor numbers from the jobLocation address as they’re not always recognized by Google.

We've recently updated our documentation with Jobs specific filters, tracking parameters and tools to help track your job posting's performance!

If you’re seeing apply button titles for your job postings appear incorrectly, follow the tips provided for creating good titles and snippets in Search Results

1. Follow the logo troubleshooting steps mentioned for updating your logo markup
2. Verify image is following logo guidelines. 
3. Image must be between 1:1 - 2:1 ratio
4. Verify image URL is accessible by Google by running it through URL inspection tool and clicking "Live Test"
5. Submit image sitemap to schedule a fresh crawl for quicker processing
6. Verify image is indexed using URL inspection tool

Google’s job search experience will soon launch the ability for providers to label remote jobs in Google Search. This allows job seekers to find a job directly in Google Search that they can perform from home.  If you’re a job data provider, you’ll need to add markup to your remote job postings so that they can be included in our results when users are looking for remote jobs.

Implementing the indexing API and keeping a dedicated updates sitemap of live job postings, is our recommended approach for sites that have a high rate of updates/removals. The Indexing API is an easier, faster, and more reliable way to inform Googlebots of your updates/removes and also prevents the need for submitting an entire sitemap list of job posting URLs after each update.

We recommend using the indexing API to send requests while also keeping your sitemap updated with current (non-expired job) postings. Doing so will help act as a backup for our crawlers to reference in case if your request responds with an indexing API error.

indexing API:

• Quicker updates by submitting individual HTTP requests to individual URLs
• Ultra low latency in order to display changes <15 min of request, compared to sitemap(hourly)
• Easier to debug issues with async notifications
• Explicit Deletion semantic

Sitemaps:

• Beneficial for large scale updates
• Can contain up to 50K of URLs
• Supports many submission endpoints(e.g. robots.txt, sent by ping, Search Console, etc.)
• Easy to generate

429 HTTP status error is due to your requests exceeding the quota currently granted. Request more quota by submitting a request form. Once submitted, your request will be reviewed within 1-3 business days. Increasing your quota and use of the indexing API is also free of charge!

***Here are a couple of things to note for 429 HTTP status errors:

1. URLs that receive a 429 HTTP response will not be successfully sent by the indexing API. 
2. Verify on your API console whether your 429 errors are from exceeding your per minute or daily quota

Yes, each URL listed in your batch request, counts as an HTTP request towards your daily quota amount. This includes both URL_UPDATED and URL_DELETED request types.

If you’re receiving 401/403 errors, make sure that your account has completed the prerequisites for authorization in order to send request using the indexing API. Once completed, you can test locally by submitting an update request to see if you’re receiving a successful 200 HTTP status.

As long as your job postings have passing markup and are accessible by Google, you should see an update within 1-2 hours of sending your HTTP request.

Not following the job posting content policies may lead to a manual action, which can prevent your site from appearing in the jobs experience on Google Search. It can also impact the job post experience, interactions, and ranking.

Depending on the nature of the policy violation, a manual action might apply on the whole site which might remove all the site’s jobs from the jobs experience on Google Search, or might apply only on the individual job posting. Learn how to fix manual actions.

While you don't have to implement optional markup properties such as directApply, if you choose to implement them, the markup must follow our policies. Incorrect implementation may lead to manual action, such as removal of the job post or entire site.

We encourage the use of the Indexing API as it allows Google to schedule pages for a fresh crawl, which can lead to higher quality user traffic. 

If you use the Indexing API to notify Google of new jobs, we expect that you also use it to notify Google of expired (deleted) jobs. This will help Google quickly remove expired jobs from the jobs experience on Google Search, and therefore improve the user experience as users will not be shown expired jobs. For more information, please visit the Indexing API quickstart page.