---
title: "Google Search Console data delay: preliminary vs. finalized data"
description: "Check preliminary data, report dates, and API metadata before diagnosing missing Search Console traffic. Understand the usual delay and when to investigate."
canonical_url: "https://gscdump.com/learn-google-search-console/limits/data-delay"
last_updated: "2026-09-11"
---

If yesterday's Search Console performance data is missing, first check whether you're viewing finalized data. Google says collected data is [normally available in 2–3 days](https://support.google.com/webmasters/answer/96568?hl=en). That is a usual delay, not a deadline every report must meet.

For a recent-traffic check, the **24-hour view** includes preliminary data. Treat it as a developing picture rather than a finished daily total.

## Check the report before your site

1. Check the selected dates and the report's last-updated information.
2. Look for preliminary data. Google uses a [dotted line for data still being collected](https://support.google.com/webmasters/answer/7576553?hl=en).
3. If a delay looks unusual, check Google's [Search Console data anomalies](https://support.google.com/webmasters/answer/6211453) before attributing the change to your site.
4. Compare a completed earlier period using the same report settings.

A low number near the end of a chart may describe an unfinished period. When using [weekly or monthly views](/learn-google-search-console/weekly-monthly-views), also check whether the date filter includes the whole final week or month.

## Use recent data for the right question

A preliminary chart can help you notice a possible change that deserves attention. It is a weaker basis for a final monthly report.

For example, if today's clicks appear lower than yesterday's, check the elapsed time and data status before reporting a decline. This is a diagnostic example, not a finding about your site.

Dates also need consistent boundaries. Search Console uses Pacific Time outside the 24-hour view; that view uses browser-local time. Google documents this in [dates and time zones](https://support.google.com/webmasters/answer/17011259?hl=en).

## If you're reading through the API

The [Search Analytics request reference](https://developers.google.com/webmaster-tools/v1/searchanalytics/query) provides three useful choices:

| `dataState`         | Use                                                |
| ------------------- | -------------------------------------------------- |
| `final`, or omitted | Request finalized data.                            |
| `all`               | Include fresh daily data.                          |
| `hourly_all`        | Request fresh hourly data with the hour dimension. |

The official [API discovery schema](https://searchconsole.googleapis.com/$discovery/rest?version=v1), revision `20260909`, names the JSON fields `metadata.firstIncompleteDate` and `metadata.firstIncompleteHour`.

When present, each field marks the start of incomplete data, including that date or hour. Availability depends on the requested data state, grouping, and range. Do not infer finality solely from missing metadata.

For an hourly request example, continue with the [hourly Search Analytics API guide](/learn-google-search-console/api/hourly-search-analytics-api).

If an integration stops updating while the report works, inspect its last successful request and any errors. A failed request, a returned empty result, and an unfinished reporting date need different handling. [API request quotas](/learn-google-search-console/api/rate-limits) are another check when requests fail.

## Keep report timelines separate

A performance-data delay doesn't tell you when Google will recrawl a page. For a specific URL, use [URL Inspection](https://support.google.com/webmasters/answer/9012289): its indexed result describes Google's stored version, while the optional live test checks the current page.

If dates are present but detailed query rows are missing, follow the [missing-row checks](/learn-google-search-console/limits/1000-row-limit). Waiting longer does not necessarily reveal query text that privacy rules withhold.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.