Fix delayed or missing Search Console data

Diagnose cadence, quota, authorization, property, cache, and reporting-delay issues.

Last checked 20 August 2026

Search Console features use different schedules and failure handling. Start by identifying which data is missing instead of reconnecting or repeatedly restarting TechDash.

Identify the expected timing

Top-page import runs only when you select Import from GSC and then Import pages. It requests the previous 28 date labels ending yesterday. An import does not schedule future imports.

Search Analytics is checked by an hourly scheduler and becomes eligible once per UTC day. A due website requests one rolling 7-day window covering days 9 through 3 before the current UTC date. The first successful run stores a baseline, so loss incidents require a later daily comparison. The interface queue remains labelled Search Console weekly, but the runtime cadence is not weekly.

Daily URL Inspection is checked hourly for enabled monitored URLs that have not been inspected on the current UTC date. Work stops when the local safety allowance or Google's quota is reached. Daily eligibility does not guarantee every URL receives a successful result.

Check TechDash prerequisites

Scheduled Search Console work requires:

  • A usable TechDash license
  • TechDash running on the computer
  • Working internet connectivity
  • A website that is not paused
  • A saved Search Console property and refresh token

URL Inspection additionally requires an enabled monitored URL. Search Analytics does not require every property URL to be in Monitored Pages.

Open Queue Status. Review Search Console weekly and Search Console URL inspection under Queues. Waiting jobs indicate a backlog. An active job is still processing. No queued job can also mean the work is not due, prerequisites failed before enqueueing, the daily allowance is exhausted, or the work already finished.

Check the connection and property

The green Search Console badge shows that a property and refresh token are stored locally. It is not a live access test.

If an interactive import reports Google account needs reconnecting., Google rejected the saved authorization. If it reports This Google account cannot access that Search Console property., check whether the user's property permission was removed.

Also confirm that the matched property represents the intended site. The property selected during connection determines both the performance rows and which URLs Google permits TechDash to inspect. The current connected UI does not display or change the property after the original success dialog.

Understand Google's reporting behavior

Google says Search Analytics data is typically available after two to three days. TechDash's rolling window leaves a 3-day buffer, but Google can still delay or revise data. TechDash changes the window key at the UTC day boundary, while Search Console interprets date labels in Pacific Time. Near those boundaries, the latest eligible TechDash window can appear offset from dates viewed in Search Console.

Search Analytics returns top rows, not a guaranteed complete export. TechDash requests at most 1,000 rows for each rolling dimension and at most 250 page rows for an import. A low-volume page or query can be absent even when property totals exist.

An import message has a specific meaning:

  • Search Console did not return any pages for that range. means Google returned no page rows.
  • No new pages to import. Those URLs are already monitored or are on another host. means rows were returned but all were skipped.

Understand quota and retry handling

TechDash rate-limits and coalesces identical Google requests. Identical top-page imports can be cached for one minute. Repeating an action may reuse a result rather than force fresh data.

For retryable Google rate limits and temporary errors, the scheduler uses delayed retries. Repeated 429 responses trigger longer pauses. URL Inspection reserves local allowance for every attempt, including retries.

Daily-quota and rate-limit conditions do not create SEO incidents. They stop or defer API work. Restarting TechDash does not reset persisted URL Inspection usage.

Non-quota Search Analytics API errors have a notable current behavior: TechDash records the Search Analytics checks as good with a message that Search Analytics was skipped after a Google API error. Treat that message as missing comparison data, not proof of healthy search performance.

Use this troubleshooting order

  1. Confirm which feature and date window you expected.
  2. Confirm TechDash was running, licensed, online, and the website was not paused.
  3. Check the two Search Console queues in Queue Status.
  4. Read the exact import or authorization error.
  5. Confirm the Google account still has property access.
  6. Check whether URL Inspection allowance has been reached.
  7. Allow for Google's two-to-three-day Search Analytics delay.
  8. Wait for the next hourly sweep or next UTC day's rolling window as appropriate.
  9. Contact support with the website, expected feature, approximate time, matched property if known, and exact error.

Do not delete the website to repair a connection. Website deletion removes its local monitoring history, Search Console data, incidents, and assets.

Sources

Related articles