For everyone who ships more than one thing

Search, speed and AI answers
on one dashboard.

Search Console, Bing, GA4 and PageSpeed for every site you ship — then it opens the fix as a pull request on your repo, and comes back to tell you whether it worked.

One email when it opens up. No drip sequence, no sharing your address.

The Growth Radar dashboard: one row per product, with clicks, impressions, position, speed and enrolment for each.

01 of 04 — the loop

It notices

Rank 8, thousands of impressions, 1% of them clicking. That's a title problem, not a content problem — and it's the one worth your evening.

02 of 04 — the loop

It ships

The fix arrives as a pull request on that product's own repo. It can't touch auth, payments, CI or dependencies, and it never merges itself.

03 of 04 — the loop

It measures

Baseline captured the day it ships, read again weeks later. You end up knowing which kind of change works on your kind of site.

04 of 04 — the loop

It compounds

Every product you own on one list, ordered by how close each one is to a paying user. The guesses stop starting from scratch.

The problem

Six products, six tabs, and no memory.

Ship more than one thing and your search data lives in six places that never talk. You notice a page dropped three weeks after it dropped. You apply some advice, never find out whether it helped, and read the same advice again next quarter. The missing piece is not another chart — it is a record of what you changed, what it was meant to move, and what happened next.

Every source

One row per product. Every number that matters.

Google Search Console

Clicks, impressions, CTR and rank, per query and per page.

Bing Webmaster

The index ChatGPT and Copilot read. Not a rounding error.

GA4

Sessions by channel — including the AI Assistants group.

PageSpeed + CrUX

Real-user Core Web Vitals, not just lab numbers.

PostHog

Who actually showed up, and which page they landed on.

Revenue state

Can this product take money yet, and what's blocking it.

First principle

Missing is a value. It is never a zero.

A product with no analytics is not a product with no visitors, and a source that fell over is not a source reporting calm. Four different silences, four different marks — carried by shape as well as colour, so the distinction survives a grey screenshot and a colour-blind reading.

Never measured
The source has never been connected for this property. That is not a zero.
0
Measured, genuinely zero
Connected, it ran, and the number really is nought. A different sentence entirely.
The source failed
It ran and fell over. Red in this product means changed or failed, and nothing else.
Has not run yet
Scheduled, not yet reported. Silence with a reason attached, and a time it is due.

Enrolment

Every property in Google and Bing, verified, sitemap in.

A property nobody measures is a property nobody can grow. Growth Radar does by API everything an API can do — Search Console, Bing, both sitemaps, GA4, IndexNow. For the rest it names the exact missing thing: the literal DNS TXT record to paste, or the one screen to click. Not a red dot.

Agent-first

Built for the web that reads, not just the one that clicks.

Assume your next visitor is an agent. Growth Radar checks that each of your properties serves an llms.txt, has an IndexNow key, and is present in the index that AI assistants actually read — and will open the pull request to fix each of those. It holds itself to the same standard: /llms.txt.

Questions

The things you'd reasonably want to ask first.

Is this another rank tracker?+

No. A rank tracker tells you a number moved. Growth Radar records the change you deliberately shipped, the metric it was supposed to move, and the value at ship time — so it can tell you whether the work paid off, per kind of change, across every product you own.

You want push access to my repositories?+

Only if you want the shipping half; the measuring half works without it. When you do enable it, changes go through an allowlist of paths per kind of change, with an absolute veto on anything touching authentication, payments, CI config, dependencies or secrets. It opens pull requests and has no ability to merge them.

How many products can I track?+

It was built for a portfolio, not a single site. The whole point is the cross-product view — twelve products on one screen, sorted by whichever measure you care about today.

What about AI search?+

Bing's index is what several assistants read, so it is tracked as a first-class source rather than an afterthought. GA4's AI Assistants channel is surfaced too, with the caveat that it undercounts badly — most assistant traffic arrives referrer-less. Growth Radar also checks that each property serves an llms.txt and an IndexNow key, and will open the PR to add them.

Who is behind it?+

One person, building it because he needed it for his own portfolio. It runs against those products every day before it runs against yours.

Early access

It's not open to everyone yet.

It runs on one person's portfolio every day. Leave your email and you'll hear when it can run on yours — your own Search Console, your own repos.

One email when it opens up. No drip sequence, no sharing your address.