SEO and marketing decision

Screaming Frog SEO Spider

A competent technical user can build a useful subset (crawler + JS rendering + basic SEO checks and exports) in about a week; keep paying for Screaming Frog if you need their polished GUI, integrations, scale, and vendor support.

Visit website
Subscription$20.42/month ✓ verified
Initial build30 hours
Monthly upkeep4 hours + $0
Evidence2/3 runs agree

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

  • Crawl a target site, render pages (execute JS), extract key SEO fields (status, titles, metas, links), detect errors/broken links/redirects, and export reports.

What it still won’t have

  • Polish and desktop GUI of the official app (native installers and menus)
  • Built-in integrations (Google Analytics, Search Console, PageSpeed Insights)
  • Advanced features: near-duplicate detection with vector embeddings, Looker Studio crawl report, and Log File Analyser bundle
  • Brand trust, support, and yearly licence convenience

What remains hard

  • Brand trust
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

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

Not run yet
Build a self-hosted SEO site crawler using Python (Scrapy for requests + Playwright for JS rendering), store results in SQLite, and expose a simple FastAPI web UI. In scope: crawl a site respecting robots.txt, render pages, extract status code, titles, meta descriptions, H1/H2, internal/external links, detect broken links and redirect chains, export CSV and XML sitemap, provide a CLI to run/schedule crawls, and include error handling and unit/integration tests. Out of scope: vector embeddings for near-duplicate detection, Looker Studio/GA/GSC/PSI integrations, advanced visual site graphs, and paid licence management.
How we checked3 sources · 2/3 runs agreed · evidence score 84

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.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded