Google Indexing API drops approval form and clarifies quota limits

On Oct. 16, Google stripped the approval form from its Indexing API documentation, effectively eliminating the explicit request‑for‑approval step that developers previously had to complete. The same update also revised the quota page to show the current limits without mentioning a separate approval process. This matters because the API is still the recommended way to push JobPosting and BroadcastEvent URLs, and the daily and per‑minute caps now apply directly to every project.

The quota details that remain visible are 200 publish requests per day (updates + removals), 180 metadata requests per minute, and 380 total requests per minute across all endpoints, resetting each day at midnight Pacific Time. Google’s spam policies still govern submissions, and the documentation warns against circumventing limits with multiple accounts.

Understanding these limits is essential for any site that relies on the Indexing API for time‑sensitive content. Because the approval pathway is gone, there is no longer a formal channel to ask for a higher quota via the old form; any increase must now be pursued through the Google API Console or future documentation updates.

What stays the same

• The API continues to support only pages with JobPosting or BroadcastEvent embedded in a VideoObject.
• Google’s default quota is still framed as “for testing” but now applies without a formal approval request.
• The spam‑policy enforcement and the prohibition on using multiple accounts to bypass limits are unchanged.

What has changed

• The explicit “Request quota and approval” link and form have disappeared, so you can’t submit a formal request for higher limits through that channel.

Why the change matters for your workflow

Knowing the exact numbers helps you decide whether to batch submissions, stagger them across the day, or fall back to sitemap submissions for less urgent URLs.

Practical steps to keep your pages indexed efficiently

• Check your current usage in the Google API Console regularly to avoid hitting the 200‑request daily ceiling.
• Prioritise which URLs you push through the API – focus on JobPosting and BroadcastEvent pages that benefit most from immediate indexing, and rely on sitemaps for the rest of your site, as recommended in Google’s job‑posting guide.
• Monitor Google’s changelog and the API quota page for any future changes to the approval or quota‑increase process.
• Implement simple logging that records each publish or removal request, so you have an audit trail if Google’s spam policies flag your activity.

What to do now

Start by logging into the Google API Console for each project that uses the Indexing API. Note the current daily and per‑minute usage numbers and compare them against the 200‑request daily limit. If you’re close to that ceiling, trim non‑essential submissions or batch them during low‑traffic periods. For any need to raise the limit, use the console’s built‑in quota‑increase request feature, citing your legitimate business case (e.g., high volume of new job listings). Finally, keep a watch on the API documentation and changelog for any re‑introduction of an approval flow or further quota adjustments.

Sources

• Search Engine Journal — Google’s Indexing API Docs No Longer Explain How To Get Approval