Google has recently updated its documentation for the Indexing API, providing clearer information about quotas, usage, and the approval process. This update aims to address common misunderstandings and set proper expectations for API users.
Key Changes and Clarifications:
Default Quota Purpose: Google has emphasized that the default quota is primarily for initial API setup and testing submissions, not for ongoing use.
Approval Requirement: Users need additional approval for extended usage and resource provisioning beyond the initial testing phase.
Quota Correction: A documentation error has been fixed, clarifying that the DefaultRequestsPerMinutePerProject quota has always been set at 380, not a lower figure as previously documented.
Default Quota Breakdown:
- DefaultPublishRequestsPerDayPerProject: 200 publish requests per day (includes URL_UPDATED and URL_DELETED requests)
- DefaultMetadataRequestsPerMinutePerProject: 180 read-only requests per minute to the getMetadata endpoint
- DefaultRequestsPerMinutePerProject: 380 requests per minute across all endpoints
Usage Restrictions and Approval Process:
Google has reiterated that the Indexing API is currently limited to pages with either JobPosting or BroadcastEvent embedded in a VideoObject. To request additional quota and gain approval for using the API with these specific types of content, users must complete a dedicated form.
Quota Management:
- Users can view their current quota in the Google API Console.
- Quota adjustments may occur based on document quality, potentially increasing or decreasing allocated resources.
Pricing:
Google has confirmed that all use of the Indexing API remains free of charge.
This update serves as a reminder for developers and SEO professionals to carefully review their Indexing API usage and ensure compliance with Google's guidelines. It also highlights the importance of obtaining proper approval for extended use, especially for those managing job postings or broadcast events at scale.
