Google Search Console API Data Stuck On June 3rd

06/10/25

TL;DR Summary of Google Search Console API Data Delay Since June 3rd

The Google Search Console API has not updated data since June 3rd, causing issues for tools like Looker Studio that rely on it. The problem appears linked to the API’s data processing state, where setting dataState to ‘all’ retrieves fresh data but ‘final’ data remains stuck. Users and SEO professionals have reported delays and data gaps, though the exact scope and cause remain unclear.

Optimixed’s Overview: Understanding the Recent Google Search Console API Data Processing Delays

Summary of the Issue

Since early June, the Google Search Console (GSC) API has experienced a significant delay in reporting fresh data. This has impacted SEO tools and reporting platforms that depend on timely information from the API.

What’s Happening?

  • The API’s data has been stuck since June 3rd, with no new updates available under the usual ‘final’ data state.
  • Users have discovered that switching the dataState parameter to ‘all’ can access more recent, though unprocessed, data.
  • This suggests a processing delay within Google’s backend systems that prevents the ‘final’ data from updating properly.

Community and Expert Observations

SEO professionals such as Martin McGarry and Simon Cox have publicly noted the issue on social media platforms like Bluesky. Some users have reported similar delays in Google Discover reporting, but these appear to be separate incidents. Comments from experts like Mike Sullivan clarify the technical nature of the problem.

Implications for SEO and Reporting

If you rely on the GSC API for analytics or reporting, be aware that data since June 3rd may be incomplete or delayed. Adjusting API queries to include fresh data states could provide partial relief until Google resolves the processing delays.

Source: Search Engine Roundtable by barry@rustybrick.com (Barry Schwartz). Read original article.