A critical analysis of server log data reveals that the Google Indexing API is no longer functioning as a reliable method for triggering crawls for general web content.
While the API was once an effective, near-instantaneous way to request indexing, its behavior has fundamentally changed in stages, culminating in a complete disconnect from Google's crawling system for most websites.
Carolyn Holzman's forensic analysis comparing server log activity before and after key dates illustrates this shift.
Prior to early December 2022, a request submitted through the Indexing API would act as a priority alert to Google's crawlers.
This would predictably trigger a sequence of bot visits, including a non-Chrome `Fetcher` bot to check the `robots.txt` file, followed by a full set of mobile and desktop Googlebots to process the page, resulting in rapid indexing.
However, beginning around December 5, 2022, the system's effectiveness was dramatically reduced.
An API call would only yield a single mobile Googlebot visit, a significant downgrade from the previous comprehensive crawl.
The final change occurred in late 2023. Now, the connection between the API and the crawling system appears to be severed entirely.
This can be confirmed through a definitive test.
When a URL is submitted, an "event" is successfully logged in the corresponding Google Cloud Service account dashboard.
This gives the appearance that the request has been received and is being processed.
However, a review of the server logs for the target domain shows a complete absence of any corresponding crawl visit from Googlebot.
The front-end system registers the ping, but the back-end crawling infrastructure is no longer dispatched.
This creates a deceptive situation where the system looks like it's working from the user's dashboard, but no actual crawling or indexing action is initiated.
The only way to verify this disconnect is by owning the site and cross-referencing the Google Cloud dashboard with server logs.
Therefore, while the Indexing API may still function for its stated purposes of job postings and live events, for all other general web content, it no longer sends a bot and should be considered effectively non-operational for triggering new crawls.