PruneDesk

Identifies and removes thin, unindexed, or cannibalized auto-published pages using Search Console data; agencies and SaaS marketers pay $149–$399/mo per site to recover traffic through CMS-native merges, redirects, and noindex actions. · SEO content lifecycle management

DEAD SLOW · CAUTIOUS

6.0 ShipScore / 10

Productized SaaS helps time; dedicated pruning demand is unproven and entry only middling.

Condition: Agencies or auto-publishing SaaS users must pay $149+/mo for cleanup that Ahrefs and Sitebulb reports don't already cover.

Part I — The Verdict what the instruments read

01 — The ShipScore breakdown

Control

Relies on Google's free Search Console API; CMS integrations are swappable.

Entry barriers

No tracked dedicated pruning leader, though Ahrefs and Sitebulb already ship similar reports.

Need

Auto-publish rivals prove spend ($100k, $25k, $18k MRR); zero pruning-specific signals.

Time-freedom

Automated merges and redirects are productized, but agency clients may expect hand-holding.

Scale

Global digital market, but post-auto-publish cleanup is a narrow SEO slice.

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 $199/mo (assumed category price), you need 419 subscribers for a $1M/yr pace.

Nearest tracked rivals on that curve:

MarkupX Brands / EarlySEO

$100k 100%

X · quiet

Launch Club

$41k 50%

→ moat stableX · silent

SEO STACK

$25k 30%

Keytomic

$18k 22%

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 6 similar

MarkupX Brands / EarlySEO	verified MRR $100k · CENTS 6.8 · X-chatter: low (x)	X · quiet
Launch Club	verified MRR $41k · CENTS 5.4 · revenue trend: stable · X-chatter: none (trustmrr)	→ moat stable X · silent
SEO STACK	verified MRR $25k (trustmrr)
Keytomic	verified MRR $18k (x)
Sight AI	verified MRR $11k (trustmrr)
Socialcrawl	verified MRR $10k (x)

MarkupX Brands / EarlySEO — $100k verified MRR in auto-publishing; could add a native pruning feature to its existing base.
SEO STACK — $25k MRR SEO suite that could bundle cannibalization cleanup cheaply.
Keytomic — $18k MRR content tool; adding lifecycle cleanup would lock in its existing users.

04 — Demand evidence

Adjacent auto-publish SEO tools show verified spend: EarlySEO $100k, SEO STACK $25k, Keytomic $18k, Sight AI $11k MRR.
None of the 6 tracked similar products with verified revenue stall under $2k MRR, so the category is healthy.
No Reddit signals, and almost no X chatter about dedicated pruning or cannibalization tools, so direct demand is unproven.

05 — Risks

Ahrefs and Sitebulb already offer cannibalization and pruning reports, which may cap willingness to pay.
Auto-publish incumbents could add cleanup as a free retention feature.
Bad merges or noindex calls could cut traffic, creating liability and churn.
Pruning can be episodic, so customers may cancel after a single cleanup.

06 — Kill switches — what kills this with one decision

Google Search Console API — Quota cuts or data restrictions would remove the core signal the product runs on.
Incumbent bundling — EarlySEO or Ahrefs shipping one-click pruning would commoditize the product overnight.

Part III — The Plan if you insist on proceeding

07 — What this scan can't tell you

Can't see whether pruning actually recovers traffic on auto-published sites at scale.
No data on the churn pattern of one-off cleanup versus ongoing monitoring.
Rival MRR is for content generation, not cleanup, so direct spend is unmeasured.

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

08 — The wedge & the next step

Continuous cleanup for AI auto-published sites: GSC-triggered merges, redirects, and noindex actions executed natively in the CMS, so it works as an ongoing guardrail rather than a one-time report.

Cheapest next step: Offer 10 agencies running auto-published sites a free GSC audit that quantifies their thin and cannibalized pages, then ask for $149 preorders for automated fixes.

Not quite it? Spin the model

Business-model variations of this idea, engineered to beat 6.0 — 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.