IndexGuard

Monitors programmatic and AI-generated content sites for index bloat, cannibalization, and Google Helpful Content Update risk signals, flagging pages to prune before rankings drop; sold to enterprise SEO teams and agencies. · SEO monitoring platform

DEAD SLOW · CAUTIOUS

6.2 ShipScore / 10

Strongest: proven SEO spend. Weakest: Google Search Console dependency and thin moat.

Condition: Land 5 agencies paying $300+/mo who can show a pruning decision your alerts drove — before Google changes GSC API terms or an incumbent ships the same module.

Part I — The Verdict what the instruments read

01 — The ShipScore breakdown

Control

C5 — index/impression data leans on Google Search Console API access

Entry barriers

E5 — Kibu stable not growing; no tracked leader on index-bloat wedge

Need

N7 — Kibu $234k verified plus Originality.ai $200k; distinct pruning wedge

Time-freedom

T7 — automated crawl/monitoring SaaS, but enterprise sales stays hands-on

Scale

S7 — global agencies and enterprise SEO teams, digital delivery

What the five commandments measure

C — Control	Do you own the customer, or does a gatekeeper stand between you and revenue?
E — Entry	How hard is this to copy once it works? A rival's existence isn't the question — the durability of their advantage is.
N — Need	Is demand proven with money rather than vibes?
T — Time	Can income detach from your hours, or did you buy yourself a job?
S — Scale	How far does it reach without linear cost?

Scored on the evidence below, against CENTS as we've adapted it plus a Buffett-style moat reading of every rival — the same referee for every idea, including the ones we generate ourselves. The verdict follows the arithmetic: we never relabel a score to make it read better, and the weakest commandment is always named. The exact rubric stays in-house so the scale can't be written for.

02 — The pace test — $1M/yr

At $299/mo (assumed category price), you need 279 subscribers for a $1M/yr pace.

Nearest tracked rivals on that curve:

Kibu

$234k 100%

→ moat stableX · quiet

Originality.ai

$200k 100%

X · active

A rival's moat trend is its verified-revenue trajectory, not its rating — a 4.9★ incumbent with eroding revenue is a different opponent than a widening one. How it's computed →

Part II — The Evidence the receipts, good and bad

03 — Rival scan — corpus tracks 2 similar

Kibu	verified MRR $234k · CENTS 8.0 · revenue trend: stable · X-chatter: low (trustmrr)	→ moat stable X · quiet
Originality.ai	reported MRR $200k · founder-reported · X-chatter: some (anchor)	X · active

Kibu — $234k verified MRR, stable — funded attention and distribution to bolt on index-health alerts
Originality.ai — $200k reported MRR in AI-content detection; adjacent enough to extend into de-indexing risk
Free/incumbent tooling (Siteliner, GSC notebooks) — Cited on X as good-enough for cannibalization checks at zero cost

04 — Demand evidence

Kibu verified at $234k MRR, trend stable — real recurring SEO tooling spend exists
Originality.ai reported $200k MRR (founder-reported) in adjacent AI-content risk
X shows SEO practitioners complaining about de-indexed AI slop and location-page index bloat
No Reddit signal and negligible X traction for any dedicated product in this exact niche — wedge unvalidated

05 — Risks

Google Search Console API quota or terms change guts the core data feed
Helpful Content signals are opaque; false positives destroy trust with enterprise teams
Enterprise SEO sales cycles are long and consultative, dragging time_score down
Ahrefs/Semrush-class incumbents can ship index-bloat reports as a feature

06 — Kill switches — what kills this with one decision

Google Search Console API — Quota cuts or access restriction removes the impression/index data the alerts depend on
Google algorithm disclosure shifts — If HCU-style signals fold invisibly into core ranking, the 'risk score' becomes unfalsifiable
Semrush/Ahrefs feature release — A free index-bloat module inside existing seats erases standalone purchase reason

Part III — The Plan if you insist on proceeding

07 — What this scan can't tell you

Cannot tell whether Kibu already ships index-bloat or cannibalization detection
No data on what agencies currently pay for pruning workflows
Cannot verify accuracy achievable in predicting HCU-driven ranking drops

Scores judge the market and business model — not your ability to execute. Verified MRR = independently tracked revenue; reviews/upvotes = platform-reported. Judged 2026-08-22.

08 — The wedge & the next step

Programmatic/AI-content publishers at scale: prune-list output tied to measurable recovered traffic, not another dashboard.

Cheapest next step: Run manual index-bloat audits free for five programmatic sites; ask each for $300/mo to keep monitoring.

Not quite it? Spin the model

Business-model variations of this idea, engineered to beat 6.2 — different vertical, audience, model, or wedge. Same harsh scale. Pro feature.

One evidence-backed gap a day, free

Close — but conditional. Every morning the engine files one mined gap, scored on the same harsh scale as this one. Free at 7am AEST, unedited.

Free forever · one email a day · unsubscribe in one click.

Monitor this idea

Weekly re-scan against the live corpus. If the market moves this ShipScore by a point, or flips the verdict, you hear about it. Free while we're small.