All documentation

Reference

Troubleshooting

Empty screens, zero citations, failed runs, and stale data.

Search or Site traffic is empty

If Traffic → Search or Traffic → Site traffic shows no data, the usual cause is not a broken integration. It is a data window that does not reach back far enough to include your most recent import.

Both screens default to a 28 day window. The date range filter at the top of the page offers 7, 28 or 90 days and carries the choice in the URL as ?days=; any other value reads as 28, so 90 days is the widest window these screens show (readDays in platform/frontend/src/lib/filters.js). If your most recent import lands outside the default 28 days but inside 90, choosing Last 90 days is the actual fix.

In steady state, imports run on a schedule rather than the moment you load the page: Search data refreshes daily at 05:00 UTC through discoveredby-cli@enqueue-gsc-import.timer, and Site traffic data (Google Analytics) refreshes daily at 06:00 UTC through a separate discoveredby-cli@enqueue-ga4-import.timer.

Mapping a property to a project is the exception to that schedule. Mapping queues that project's first import there and then rather than deferring it to the next scheduled run (_enqueue_import in platform/backend/api/routers/integrations.py), so a freshly mapped property does not sit waiting on the timer for its first pull. If that immediate enqueue is lost, the next scheduled run picks the property up anyway: the daily fan-outs reach a project through its mapped properties, and the import widens to a 180 day backfill for any property whose history has never been pulled (_enqueue_ga4_for_eligible_projects and _enqueue_gsc_for_eligible_projects in platform/backend/api/tasks.py). For a mapped property, then, a missed enqueue costs a delay of a day, not a lost import.

Connecting is not the same as mapping, and that difference is the other common cause of an empty Search or Site traffic screen. Connecting maps nothing (oauth_complete in platform/backend/api/routers/integrations.py). The integrations settings list your properties and suggest a project for a property whose site exactly equals one of your project domains, where that match is unambiguous (suggest_gsc_projects and suggest_ga4_projects in platform/backend/api/services/integrations/google/property_suggestions.py), but nothing is attached until you take the suggestion or pick a project yourself. A subdomain-only match such as a shop.example.com stream against an example.com project, no match at all, or an ambiguous one, gets no suggestion; pick the project from the dropdown instead. An unmapped property is in no fan-out's scope, so nothing imports for it and no later run heals it: if those screens have been empty since the day you connected, open the integrations settings and map the property to the project. That mapping is what starts the first import.

A mapping belongs to the project, not to the person who made it. If a teammate has already mapped a property, these screens show its data to everyone on the project, so you do not need to connect Google yourself. The integrations settings never suggest a second Search Console property for a project a teammate's property already feeds, nor a second copy of an Analytics property the project already gets through them.

Widening the window is still the fix when the most recent successful import, whichever kind, lands outside the default 28 days but inside 90. An import older than 90 days cannot be brought into view from these screens; the next successful import is what fills them again.

Search or traffic shows no changes

Search, Site traffic and AI traffic compare the selected window with the one before it, and they show those changes only when each window holds imported Google data on at least 80% as many days as the other (is_comparable in platform/backend/api/services/integrations/google/gsc_search_metrics.py). When one falls short, every change is hidden rather than shown as a rise or a fall, and a note names the short window (comparisonGapReason in platform/frontend/src/lib/comparison.js).

On the 7-day Search window this is common. Search Console reports two to three days late, so the current week is often too short to compare until the import catches up: choose 28 days, or look again in a few days. A short previous window usually means the property was mapped recently, and a short current one on Site traffic or AI traffic usually means the import has stopped, which Integrations helps you check.

No citations yet

Being named in AI answers without yet being cited as a source is a normal, common starting state, not a sign anything is broken.

A mention and a citation are different things: a mention is your brand named in an answer, a citation is your domain linked as a source for that answer, and you can be mentioned without being cited (see Key terms). An engine can describe your brand from what it already knows without pulling one of your pages into the answer at all, so winning a mention is often the earlier, easier outcome, and a citation can take longer to follow.

If citation rate reads zero while your collected answer count is not zero, that is a real zero, not a broken measurement: see Metrics defined for how a genuine zero differs from no data. Domain coverage, a separate number on that same page, catches the weaker signal of an engine reading one of your pages without linking to it. Zero citations alongside domain coverage above zero means retrieval without citation, not a bug.

A run failed

Where to look: each prompt's Runs tab lists the executions in the filter bar's window that match its engine, country, persona and language chips, failed ones included, with their status, up to the 50 most recent. While fewer than 50 are listed, widening the date range or clearing a chip shows more; once 50 are listed it cannot, since the list already holds the newest 50 and clearing a chip only swaps in newer runs of other engines or targets. 90 days is the widest window, so an older run is not listed there. A failed execution shows a plain-language reason drawn from a closed, safe set (timeout, rate limited, provider error, or internal error) rather than a raw error string.

A failed run is retried automatically later the same day, at 03:00, 05:00, 09:00 and 17:00 UTC, so a short engine outage rarely costs you the day. A retry that succeeds replaces the failed run with the answer. Until then, and if the 17:00 retry also fails, the run stays failed for that day. A retry only happens while the prompt, the engine and your plan would still run it.

A Google AI Overviews or Google AI Mode run that reads No AI Overview shown or No AI Mode answer did not fail: the request succeeded and Google showed no AI answer for that search. It counts toward the shown rate instead of any answer metric (see When Google shows no AI answer).

What a failed run does to your numbers: nothing, quietly. Every answer metric on Metrics defined is built from executions whose status is completed, whether it counts those executions directly or counts the mentions attached to them; the three run metrics there also count runs with no AI answer, never failed ones. A failed execution is never completed, so it never contributes an answer, a citation, a retrieval, or a mention to any of those counts. A run that failed to get an answer at all does not drag your visibility, citation rate, share of voice, or any other metric down: it is absent from the count, not counted as a miss.

My numbers moved but nothing changed on my site

Two things that have nothing to do with your website can move your numbers, and both are expected.

Adding a tracked competitor changes share of voice, even though nothing in the answers themselves changed: the denominator is a sum, added up across every active tracked brand family, of how many answers named each one, so widening your competitor roster adds that competitor's own count to the sum (see Metrics defined). The competitor's mentions were already happening; your project just started counting them.

The other cause is the engines themselves. Each tracked prompt runs again on its own schedule, and an engine's answer to the same question can differ from one run to the next even when nothing about your site, your competitors, or the prompt has changed. Engines do not answer the same way every time, so a daily figure moves on its own from one day to the next. A single day's swing is not, by itself, evidence that anything is different on your site; read the trend over the whole window instead of one day.

Competitor shares do not add up to 100 percent

Share of voice divides among you and your active tracked competitors only, so the SoV column of Overview's Brand ranking, which lists you and every active tracked competitor, should come to 100 percent between its rows. Pausing or removing a competitor updates the brand roster in the same save, so the very next load leaves it out, on both sides of the division, with no separate step and no lag (see Pausing or removing a competitor for the mechanism). Each share is rounded to one decimal place, so the total can still land a few tenths above or below 100 percent even when nothing is wrong. If the column is short of 100 percent by more than a rounding difference, that is worth a closer look.

A number says no data instead of zero

A metric reading no data is not the same as a metric reading zero, and the product never blurs the two. See How to read any number here on Metrics defined for what no data means and why, and that page's own per-metric sections for which population each number divides by. An empty population is what produces no data; a measured population that happens to contain none of what you are looking for is what produces a real zero.

Last verified 2026-11-02

Start monitoring your AI visibility.

See how AI search engines talk about your brand.

Free to start. No credit card required.