SEO and marketing decision
Leafpad io
A single-tenant replacement covering core detection, LLM-driven rewrites, and CMS publishing is realistic for a competent developer in ~40 hours; enterprise features (Ahrefs competitor tracking, MCP production server, domain-readiness automation) would require more investment.
Visit website↗$39/mo
$468/yr
Read off the official pricing page.
$100one-off40 h to build
$80/mo4 h/mo upkeep
On cash alone, building overtakes the subscription at 3 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Detect pages losing clicks from Google Search Console, generate SEO-backed rewrites with an LLM, propose internal links and SEO meta, and publish approved updates to the site's CMS via its API.
What it still won’t have
- Domain Readiness Score and automatic publish cadence driven by domain signals
- Native MCP production server integration for one-click publish from Claude/ChatGPT/Cursor
- Built-in competitor tracking and Ahrefs-backed keyword suggestions
- On-brand automated visuals and managed AI generation credits
- Multi-platform, production-grade CMS integrations and rescan automation
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a single-tenant LeafPad-like service using Node.js (Express), Postgres, React, and deploy on Vercel (frontend) + Render or DigitalOcean App (backend). Core features in-scope: (1) connect to Google Search Console and ingest performance data; (2) detect pages with >=20% click decline over 90 days and surface candidate list; (3) call an LLM (OpenAI/GPT) to generate an SEO-optimized draft and alt images via an image API; (4) compute and propose internal links, meta tags, and sitemap changes; (5) publish approved updates to WordPress (REST API) and Ghost (Admin API) and support manual CSV export; (6) basic approval UI showing current vs. proposed diffs and scheduling. Out of scope: competitor tracking via Ahrefs (paid crawling), advanced Domain Readiness scoring, MCP server integration, and multi-tenant billing. Require error handling, request retries, auth token refresh, tests covering ingestion, generation, and publishing flows, and CI deploy scripts.
How we checked
How the score was reached
- Build verdict base78
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score84
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productLeafpad - official product
- official pricingLeafpad Pricing
- official docsLeafpad Docs
Integrity checks
What held up, and what did not.
