Short answer
Google has removed the approval form and the instructions for requesting approval from its Indexing API documentation. The company has not said whether the approval requirement itself has changed. The API still applies only to job posting and live video pages, so sites that manage them should not rely on a single indexing route and should keep a sitemap fallback.
Highlights
- Google removed the approval form and application instructions from the Indexing API docs.
- It is unclear whether the approval requirement changed; the daily limit and usage restrictions remain in the docs.
- The API covers job postings and live video only; other pages rely on sitemaps and Search Console.

2 min readAuthor: UNIT Journal EditorEditor-in-chief: Uğur Deniz İlhan
Google has changed its Indexing API documentation. According to Search Engine Journal the approval form and the request-approval section were removed from the quota page. Google's changelog says the quota page was updated "to reflect the current quota limits and process" and that an "outdated form" was removed.
What exactly changed in the docs?
The section linking to the approval form is gone. The quickstart no longer lists a "request approval and quota" step, and the notes on the usage page saying the default quota is for testing were removed as well.
The changelog does not say whether the approval requirement itself has changed, nor what happens to sites that applied earlier. This is not an "open to everyone" announcement; it is only a path disappearing from the documentation.
Which limits remain?
The quota page still shows the default limits: 200 publish requests per project per day, 180 metadata requests per minute and 380 requests per minute across all endpoints. The API remains limited to pages with JobPosting or BroadcastEvent embedded in a VideoObject. Spam policies still apply, and using multiple accounts to get around limits is prohibited.
What should companies in Turkey do?
If you do not run a job board, careers site or live video content, this change does not affect you directly. If you do, add the following to your technical SEO checklist:
- Check your project's current quota in the Google API Console and watch for unexpected increases or drops.
- Do not tie indexing to the API alone; keep an up-to-date sitemap for listings as a fallback. Google's job posting guide recommends a sitemap for full-site coverage.
- Notify Google of expired listings with removal requests and validate JobPosting markup on the pages.
- Follow documentation changes weekly so you hear first if Google announces a new application route.
Frequently asked
- Can I now use the Indexing API for any page?
- No. According to the API documentation it applies only to pages with JobPosting or BroadcastEvent embedded in a VideoObject. For other pages, use sitemaps and Search Console.
Sources
- Search Engine Journal ·
Follow UNIT Journal
What's new in search, AI and technology, in your feed every day.


