The sources behind every answer
Eight of them, and they are not the same kind of thing. Four you already own, the assistant reads them with your permission and read-only scope. Four are Quattr's own daily observation of surfaces nobody's own systems record. Each one unlocks more of the 58 analyses, and each one carries a lag that travels with every number it produces.
Yours, read with your permission
Connected once, read-only, scoped by your Quattr account.
-
Google Search Console →
1 to 2 days behindClicks, impressions, CTR and average position by query, page, country and device, the ground truth for organic search.
Unlocks Search performance, striking-distance and CTR modelling, ranking movement, and every breakdown that starts "which pages…".
Where the customer is entitled to it, the BigQuery bulk export can be used instead of the API, far more unique queries and pages, with privacy-suppressed impressions grouped under a placeholder query. It is a deliberate choice, not a silent upgrade: the assistant uses it when asked.
Google's own reporting lag. Any answer touching the last 48 hours says so on the card.
-
GA4 or Adobe Analytics →
loads nightlySessions, users, engagement and, the part that matters, conversions against the goals you configured yourself.
Unlocks Search-to-revenue, funnel drop-off, conversion-rate significance, and landing-page behaviour after the click.
Conversions bind to your named goals. The assistant asks which goal rather than summing them, because configured goals routinely overlap and a total would double-count.
A same-day question gets yesterday's number, labelled as yesterday's.
-
Google Ads →
~1 day behindSpend, CPC, cost per conversion and impression share, by search term, bidded keyword, ad group and campaign.
Unlocks Paid efficiency, auction coverage, and the paid-organic join, the same keyword seen from both sides.
The search term that triggered an ad and the keyword you bid on are different fields, and the difference matters: the assistant names which one it grouped by.
Ads reporting settles overnight; same-day spend is provisional.
-
Server logs →
hours to nightlyEvery fetch your origin actually served, including the AI crawlers, GPTBot, ClaudeBot, PerplexityBot, Google-Extended, with status codes and IP verification.
Unlocks AI crawler readiness, crawl-budget waste, and Googlebot spoofing checks that no third-party index can answer.
This is the only source that can say whether an AI crawler reached a page. Everything else infers it.
Depends on how logs are shipped; the card carries the ingestion time.
Quattr's own daily observation
Collected by Quattr because no first-party system records it.
-
Site crawl →
per crawl scheduleQuattr's own cloud crawl of your site: the link graph, indexability signals, canonicals, and depth from the homepage.
Unlocks Orphan pages, internal-link distribution, indexation diagnosis, and crawl-depth waste.
Crossed with server logs, this answers the question neither can alone: is the page reachable, and did anything actually fetch it?
Cadence is set per site; the card names the crawl it read.
-
Rank tracking →
~1 day behindQuattr's daily SERP observation across your tracked demand, modelled into a comparable share for you and each tracked competitor.
Unlocks Standing versus rivals, leader gap, share by intent and page, and the separation of market movement from your own.
Always CTR-modeled search market share of tracked demand, directional, scoped to the keywords in a tracked segment, and never revenue share. It is stated that way on every card because the qualifier is the number's meaning, not a footnote to it.
Daily observation, available the following day.
-
AI visibility →
~1 day behindQuattr's own daily prompting of the answer engines, ChatGPT, Perplexity, Gemini, Google AI Mode, recording who is cited, who is mentioned, and in what tone.
Unlocks Citation rate by engine, share of voice against rivals, prompt coverage gaps, and which of your URLs answers get built from.
Answer-engine citations and Google's on-SERP AI Overviews are separate surfaces measured separately. Neither is folded into the other, and every figure names which one it is.
Daily prompt runs, available the following day.
-
Lighthouse and Core Web Vitals (CWV) →
varies by sitePerformance, accessibility, best-practices and SEO scores plus LCP, INP and CLS, collected per page.
Unlocks Page-experience health, regressions by device and template, and the join of speed to the pages that actually earn clicks.
A vital measured three weeks ago is reported as measured three weeks ago. Presenting stale page-experience data as current is the easiest way to send an engineering team after a problem that has already been fixed.
Priority URLs can run nightly; most pages far less often. The collection date rides on the card rather than being assumed.
Start here
What data sources are connected for my site, and how fresh is each one?
It answers from your own configuration rather than from this page, which is the point. A source list you can verify in ten seconds beats one you have to take on faith.