Data freshness

API reads use saved answers and search data. Collection runs separately on a daily schedule.

A read request returns data already stored by SearchSeal. It does not start a scan or refresh a source. Collection may be incomplete or delayed; use saved dates to assess freshness.

Daily answer collection

Daily scans schedule active tracked questions against the engines on your plan.
Saved answers retain brand mentions and returned source URLs.
Those records feed AI reports and fixes; search fixes use saved search data.

New API questions become eligible for the next daily scan. Archiving excludes a question from future scans and preserves the answers already saved.

Read data-through dates

Authenticated REST resource responses include meta. Answer lists, reports and individual brand reads add dataThrough: each source’s latest stored day, or null when no rows exist. These brand-wide dates do not follow request filters or confirm a complete scan.

Metadata example

"meta": {
  "generatedAt": "2026-09-26T08:15:02Z",
  "timeZone": "Asia/Jakarta",
  "dataThrough": {
    "answers": "2026-09-26",
    "google": "2026-09-23",
    "bing": "2026-09-24"
  }
}

Field	Description
`generatedAt`	The UTC timestamp at which the response was generated.
`timeZone`	The account time zone used to determine today. Source dates and UTC timestamps retain their own calendars.
`dataThrough.answers`	Latest stored answer date, excluding previews but including incomplete answers.
`dataThrough.google`	Latest date in the saved Google Search Console totals.
`dataThrough.bing`	Latest date in the saved Bing daily totals.

Dates and time zones

startDate and endDate include both boundary days. The account time zone determines today; update it in Settings.

Omitting both dates selects 28 days through account-local today.
A future endDate fails with 400 invalid_request and field code future_date.
Report windows allow 90 days; answer-list windows allow 365.
A recent endDate may include a partial collection. Even when it matches dataThrough.answers, more answers may still arrive.

Search source dates

Search reports use each provider’s stored dates. Google and Bing data can lag behind AI answers, and a request does not sync either source. Check dataThrough.google and dataThrough.bing to see the latest daily data available.

Before-and-after comparisons

Completing a fix captures its preceding 14-day window. The after value remains null until a snapshot is captured at or after dueAt, 14 days later. Visibility needs three questions and ten samples per side for comparable to be true; clicks need both values. Differences do not establish that the fix caused them.

Browse the API reference or read about handling failed requests.