How it works
One script, four sources, and a schedule. What gets read, how often, and where the numbers come from.
How it works
Two kilobytes, deferred, first-party. It records the page, the referrer, the browser, the OS and a country derived server-side. Your IP is used at the moment of the visit and never stored.
One Google connection covers Search Console and GA4 — same consent, granted once, read-only. Google publishes its data on a two-to-three day delay, which is their pipeline and not a lag here.
Your tracked terms are checked in real search results, and the domains that appear above you become the competitor list — the rivals a searcher actually sees, not a list you guessed at.
ChatGPT, Claude, Gemini, Perplexity and Grok get the questions your buyers ask, generated from your own top pages and search terms. Answers are stored with who was cited.
Uptime and response time every five minutes. A crawl of your own pages weekly, checking titles, headings, alt text, broken links and redirect chains — weekly because these change when you deploy, not overnight.
A ranking move past your threshold opens a Slack message or a Linear issue. A digest summarises traffic, movement, mentions and anything health flagged. Repeat sends are prevented by a ledger, not by the schedule, so a retry never means a second email.