Google clarifies Indexing API Quota and Usage in recent documentation update

Google this week updated its Search Central documentation, providing crucial clarifications on the quota and usage of the Indexing API. This update, announced on September 4, 2024, aims to enhance user understanding of the API's default quota, approval process, and resource provisioning.

The Indexing API, a tool designed to help website owners inform Google about the latest changes to their web pages, has been a subject of interest for many developers and SEO professionals. The recent documentation update addresses several key points that users should be aware of when utilizing this service.

According to the updated documentation, Google has established a default quota for the Indexing API, specifically intended for initial API onboarding and testing submissions. This quota is broken down into three main categories:

1. DefaultPublishRequestsPerDayPerProject: This quota limits the number of 'publish' requests that can be sent to the 'publish' endpoint daily, per project. It encompasses both 'URL_UPDATED' and 'URL_DELETED' request types. The default value is set at 200 requests per day.
2. DefaultMetadataRequestsPerMinutePerProject: This quota restricts the number of Read Only requests that can be sent to the 'getMetadata' endpoint per minute, per project. The default value is established at 180 requests per minute.
3. DefaultRequestsPerMinutePerProject: This quota applies to all endpoints and is set at 380 requests per minute, per project.

It's important to note that these default quotas are primarily for setup and initial testing purposes. Users requiring additional resources or looking to use the API for production purposes will need to go through an approval process.

The documentation update clarifies that the Indexing API is currently limited to crawling pages with specific types of structured data. As of September 2024, the API can only be used for pages containing either 'JobPosting' or 'BroadcastEvent' schema markup embedded within a 'VideoObject'.

For users who require quota beyond the initial default limits or who seek approval to use the API for pages with the aforementioned markup, Google has provided a formal request process. Interested parties can fill out a designated form to request additional quota and gain approval for expanded use of the API.

When submitting a request for increased quota, users need to provide details about their project from the Google Cloud console. It's worth noting that the granted quota may be subject to change based on the quality of the documents submitted through the API.

In addition to the clarifications, Google has rectified a documentation error regarding the DefaultRequestsPerMinutePerProject quota. The company confirmed that this quota has always been set at 380 requests per minute, contrary to what may have been previously stated in the documentation.

Despite the quota limitations and approval process, Google has maintained its policy of providing the Indexing API without charge. All use of the Indexing API remains available without payment, making it an accessible tool for eligible website owners and developers.

For users who wish to monitor their current quota usage, Google directs them to the Google API Console. This platform allows users to view their quota allocations and usage across various Google APIs, including the Indexing API.

These updates have several implications for current and potential users of the Indexing API:

1. Initial Testing: The default quota allows for initial setup and testing, but may not be sufficient for large-scale or production use.
2. Approval Requirement: Users need to go through an approval process to use the API beyond initial testing, especially for pages with specific structured data.
3. Resource Planning: Developers and website owners should plan their API usage carefully, considering the quota limitations and approval requirements.
4. Document Quality: The quality of submitted documents may influence the granted quota, emphasizing the importance of maintaining high-quality content and markup.
5. Specific Use Cases: The current limitation to 'JobPosting' and 'BroadcastEvent' markup indicates Google's focus on specific use cases for the Indexing API.

The Indexing API operates through specific endpoints:

• The 'publish' endpoint for URL updates and deletions
• The 'getMetadata' endpoint for retrieving information about indexed URLs

Each endpoint has its own quota limitations, which users must consider when implementing the API in their systems.

This clarification from Google comes at a time when efficient indexing and quick updates to search engine databases are crucial for businesses and content creators. The Indexing API offers a direct method for informing Google about new or updated content, potentially speeding up the indexing process.

However, the limitations and approval process suggest that Google is carefully managing the use of this powerful tool, likely to maintain the quality and integrity of its search index.

Key Facts

• Announcement Date: September 4, 2024
• Default Daily Quota for 'publish' requests: 200 per project
• Default Per-Minute Quota for 'getMetadata' requests: 180 per project
• Overall Default Per-Minute Quota: 380 requests across all endpoints per project
• Current API Limitations: Only for pages with 'JobPosting' or 'BroadcastEvent' embedded in 'VideoObject'
• Approval Process: Required for quota extension and production use
• Pricing: All use of the Indexing API is free of charge
• Quota Monitoring: Available through the Google API Console