--- title: "Google Search Console Data Delay: Preliminary vs. Finalized Data" description: "Finalized Search Console performance data is normally available within two to three days, while the 24-hour view and API can expose preliminary data sooner." canonical_url: "https://gscdump.com/learn-google-search-console/limits/data-delay" last_updated: "2026-07-20" --- Search Console's finalized performance data is normally available within two to three days. Newer preliminary data can appear sooner in the 24-hour report and through the Search Analytics API, but Google warns that it is still being collected and can change. Other Search Console reports update on their own schedules. Google does not publish a fixed processing time for every report, so a single "GSC delay" does not describe the whole product. ## Search Performance Data ### Finalized Data: Normally Two to Three Days Google's [Search Console data documentation](https://support.google.com/webmasters/answer/96568) says collected performance data should normally be available within two to three days. Use finalized data when you need stable daily reporting. Search Console groups normal daily data in Pacific Time. If you compare it with a system that uses another reporting time zone, the daily totals can appear shifted even after both systems finish processing. ### Preliminary Data: Available Sooner The Performance report's [24-hour view includes preliminary hourly data](https://support.google.com/webmasters/answer/7576553). Google marks incomplete data with a dotted line and notes that it can change in the next few hours. The Search Analytics API exposes the same distinction through [`dataState`](https://developers.google.com/webmaster-tools/v1/searchanalytics/query): - Omit `dataState` or use `final` for finalized data. - Use `all` to include fresh daily data. - Use `hourly_all` with the hour dimension for fresh hourly data. Responses that include fresh data can return `first_incomplete_date` or `first_incomplete_hour` metadata. Use those fields instead of assuming that every recent row is final. ## Other Report Timelines ### URL Inspection: Indexed Snapshot and Live Test The default [URL Inspection result](https://support.google.com/webmasters/answer/9012289) is not live. It describes Google's most recently indexed version of the URL, which can differ from the page currently served by your site. The optional live test fetches the current page in real time and checks whether it appears indexable. A successful live test does not mean the page is indexed or guaranteed to appear in Search. ### Page Indexing: Crawl-Dependent Updates The [Page indexing report](https://support.google.com/webmasters/answer/7440203) reflects Google's knowledge of URLs after crawling and processing. Google does not promise a three-to-five-day refresh interval. A newly added site can [take up to a week to generate Search Console data](https://support.google.com/webmasters/answer/96568), and individual page changes depend on when Google recrawls the affected URLs. Use URL Inspection for a specific page. Use the Page indexing report for site-wide patterns and issue groups. ### Core Web Vitals: Rolling 28-Day Field Data The Core Web Vitals report uses Chrome User Experience Report (CrUX) field data. Each assessment represents the 75th percentile over a [rolling 28-day collection window](https://support.google.com/webmasters/answer/9205520). A fix can begin influencing the assessment as new visits enter the window and older visits leave it. A full window takes 28 days to turn over, and URLs without enough eligible Chrome traffic might not appear at all. ### Sitemaps: No Fixed Processing Promise The [Sitemaps report](https://support.google.com/webmasters/answer/7451001) shows when a submitted sitemap was last read and the status of the latest fetch and processing attempt. Google does not document a guaranteed one-to-three-day processing window. Submitting a sitemap helps Google discover URLs, but does not guarantee that every listed URL will be crawled or indexed. ## When to Investigate ### Performance Data Is More Than Three Days Behind If finalized data is more than three days behind, check it. The delay alone does not prove that your property or integration is broken. 1. Check the report's last-updated date and whether you selected preliminary data. 2. Check Google's [Search Console data anomalies](https://support.google.com/webmasters/answer/6211453) for a known reporting issue. 3. Compare the UI with a simple API query grouped only by date. 4. For a new property, allow up to a week for initial data to appear. ### An API Sync Stopped Updating Start with the integration: - The access token might have expired, and the refresh attempt might have failed. - The refresh token might have expired or been revoked. - The user might no longer have permission for the property. - The client might be hitting Search Analytics load or request-rate quotas. - A query might be returning zero available detail rows rather than an explicit error. Losing verification or permission removes access to the property. It does not necessarily mean Google stopped collecting performance data for the site. ### Some Dates or Rows Are Missing An absent date can be a processing issue, an extraction failure, or a genuine zero-data day. Querying without filters and grouping only by date is Google's recommended way to check which dates contain data. Missing detail rows can also come from anonymized queries or Search Console's internal data truncation. The [50,000-row-per-data-day ceiling](https://developers.google.com/webmaster-tools/v1/how-tos/all-your-data#data-limits) is a data-availability limit, not a request quota; it limits the rows available for that date before your client receives the response. ### Historical Numbers Changed Google can correct previously reported data. For example, the official [anomalies log](https://support.google.com/webmasters/answer/6211453) documents a 2026 correction that changed historical impressions and related CTR and position metrics. Search Console's BigQuery export can also [revise an earlier data day atomically](https://support.google.com/webmasters/answer/12917991) and records the new version in `ExportLog`. When a historical number changes, check Google's anomaly log before attributing the difference to rankings or site changes. ## How gscdump Handles Recent Data gscdump's synchronization code treats the newest dates as non-stable. Its hosted initial and daily sync jobs require Pro access. For eligible stored-data sites, it: - Runs a daily sync for eligible stored-data sites - Re-fetches the recent non-stable window instead of assuming the first value is final - Uses an Iceberg ingestion ledger to detect missing stable dates and support backfills - Archives the returned analytics tables in Cloudflare R2 - Reports sync failures rather than silently advancing a completed watermark The archive still reflects only the data Google exposed through the API. It cannot reconstruct anonymized query text or detail rows Google truncated. Free accounts query supported reports live against Google and do not receive this background archive. ## FAQ ### Why is yesterday's data missing? Finalized data for yesterday might not be ready. Check the 24-hour view for preliminary data, or request fresh data through the API with `dataState: "all"`. Do not treat it as final until Search Console no longer marks it incomplete. ### How do I check whether Google has a reporting problem? Check the [Search Console data anomalies page](https://support.google.com/webmasters/answer/6211453). For broader crawling, indexing, or serving incidents, also check the [Google Search Status Dashboard](https://status.search.google.com/). ### Does the delay affect the API? The delay affects API availability too, but the API lets you choose finalized or fresh data with `dataState`. Fresh responses can include metadata identifying the incomplete period. ### Can I get real-time search performance data? No event-level real-time feed is available. The closest Search Console view is preliminary hourly data in the 24-hour report or with `dataState: "hourly_all"`. URL Inspection's live test is a current page fetch, not real-time click or impression data. ## Related Articles - [16-Month Data Limit](/learn-google-search-console/limits/16-month-data-retention): Preserve performance data before it ages out - [GSC Export Row Limits](/learn-google-search-console/limits/export-row-limits): Understand UI and API row limits - [GSC API Rate Limits](/learn-google-search-console/api/rate-limits): Request and load quotas - [GSC vs. GA4 Data Discrepancies](/learn-google-search-console/limits/gsc-vs-ga4): Why clicks and sessions differ