saascode
marketing & growth·run 102 · May 2026

SeoRadar

A tenant-isolated agency data endpoint that normalizes authorized first-party search telemetry with optional paid observations, detects bounded changes and emits signed snapshots without claiming rank truth or causal diagnosis.

Genesis score6.77/10
Make SeoRadar real.0/500
500 more votes and SeoRadar is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Search agencies manage client properties across first-party search telemetry, rank providers and question datasets. Every source has different dimensions, freshness, location and cost. Teams rebuild weekly reports and can miss a page or query shift until traffic has already changed. SeoRadar creates a normalized, source-aware event feed for each client.

A rank is a bounded observation conditioned by query, location, device, language, time and provider. A first-party click or impression is not a universal market ranking. An anomaly is a statistical change, not proof of an algorithm update, technical defect or competitor action. A signed snapshot supports bounded origin and integrity; it does not make the underlying observation true or permanent.

The supplied research confirms a free-within-quotas first-party interface, metered rank data and an official data endpoint, while finding no reviewed direct competitor with the full multi-client event combination. The first release uses the first-party source as an anchor and adds paid observations only where the agency authorizes cost and purpose.

Who pays — and why

An SEO or growth agency serving multiple software clients and repeatedly consolidating first-party search data, rank observations and weekly change reports.

What it unlocks
Tenant-isolated normalized search observations with original source and dimensional context
Page, query and result-feature change candidates with uncertainty and comparable baselines
Signed client snapshots and weekly event feeds that remain separate from diagnosis and business outcome
How Genesis scored it
6.77across seven criteria
tension 7temporal 7blindspot 5buyer 7leverage 8convergence 5why-not 7
8
Asymmetric leverage

Normalization, events and endpoint delivery are strongly code-scalable.

7
Productive tension

The product combines low-cost first-party data with paid observations while preserving every source’s limits.

5
Convergence

The source records one cross-reference and no inbound connections.

Why it scored well

The source confirms the first-party and paid data interfaces, an official protocol endpoint and an adjacent agency skill, while finding no reviewed product combining multi-client normalization, anomaly events and signed snapshots.

What's holding it back

The buyer quartet is incomplete, only one interface set is clearly verified, provider observations differ, anomalies are non-causal, the claimed share of value from the free source is unsupported and incumbents can add protocol access.

Signals detected4 sources crossed
SignalSupplied interface review

SignalSupplied provider and protocol review

SignalSupplied repository review

SignalSupplied category review

Direction briefseoradar.md
seoradar.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.