Why Search Console data is two days behind
Search Console's reporting lag, why the most recent days keep changing, and what the freshest data you can request actually is.
Performance data in Search Console runs roughly two days behind, occasionally three. This is normal and not a fault in whatever you are viewing it with.
What causes it
Search logs are processed in batches at enormous scale, then filtered — bot traffic removed, rare queries anonymised, duplicates reconciled across dimensions. The result is published once it settles.
Why recent days keep changing
The most recent day or two are partial. Look at yesterday this morning and again tonight and the number will have grown. This is not a correction; the day is still being assembled. Any comparison involving the last two days is comparing a complete period against an incomplete one.
The two data states
The API exposes a dataState parameter with two values:
final— only fully processed days. Stable, and about two days stale.all— includes partial recent days, marked as fresh. More current, still moving.
Neither is more correct. final is right for reporting; all is right for "is anything on fire today".
Practical rules
- Never diagnose a drop from the last two days alone.
- For week-over-week, end both periods at least three days back.
- If you export weekly, export the same weekday each time — the partial-day effect is consistent.
- A dip at the right edge of any Search Console chart is the default state, not a signal.
Searchlight requests dataState: all, so the freshest partial days are visible rather than hidden.
See how Searchlight shows it