Google removed the Indexing API endorsement form from its records on Oct. 16, alongside alongside the instructions telling developers to ask for approval.
In September, I reported that job commission operators had waited months for responses to their endorsement requests. Google’s changelog says it updated the quota leaf “to indicate the current quota limits and process” and to “remove an outdated form.” It doesn’t say whether the endorsement necessity itself has changed.
What Google Removed
Before the Oct. 16 update, the quota page stated the API “provides first default quota for testing, and it requires additional endorsement for use and asset provisioning.” A division titled “Request quota and approval” connected to the form and stated “the quota may addition or decrease according to the document quality.” Both are gone.
The quickstart is no longer listing “Request endorsement and quota” as an first set-up action. The usage page dropped three identical notes stating the API has a default quota “for testing,” in supplement to instructions on how to petition endorsement and quota. While the two are dated Oct. 16 (the same), the changelog lone mentions the quota page.
Google had clarified the evaluation language in September 2024, whenever its changelog stated the aim was “to improved explain that the default quota is for first setup and testing.”
What’s Still In The Docs
The quota leaf motionless lists the default limits. Each project gets 200 publish requests per day, counting the two updates and removals. Per minute, a project gets 180 metadata requests and 380 requests throughout all endpoints. The regular bounds resets at midnight Pacific Time.
The API is motionless constricted to pages alongside JobPosting or BroadcastEvent embedded in a VideoObject. The use leaf motionless says Google’s spam policies use to submissions and tells developers not to get about submission limits, “such as by using multiple accounts.”
Google’s job posting guide, which was final updated Sept. 8, motionless recommends the Indexing API complete sitemaps for job posting URLs and a sitemap for full-site coverage. The quickstart itself did distant alongside the paragraph comparing the two.
Why This Matters
Job commission owners in my September study stated they had waited months without receiving an update concerning the position of their endorsement requests, and Google’s documents gave no timelines for reviewing specified requests.
In addition, I noticed that the newly-updated Indexing API records no longer provides data on how to present your use to be allowed to utilize the API; nor does it provision data as to what volition happen to applications that have been earlier submitted to be reviewed, or if a project that never received endorsement can now utilize its default quota for live job postings or livestreams.
Looking Ahead
You can inspect your project’s current quota in the Google API Console, anywhere the quota leaf motionless directs you. Keep an eye on that leaf and the changelog for any new way to petition a higher quota.
Featured Image: Tetiana Yurchenko/Shutterstock. Source: Google.
