Sitebulb?

KINDAYou can build the valuable core, but the established product has meaningful operational complexity. Pick one narrow promise for v1.

BUILD FIRST

One specific customer type and one primary use case
A vertical slice that completes the main job without manual workarounds
Visible limits, review steps, and a fallback when an external dependency fails

LEAVE FOR LATER

Broad third-party integrations
High-scale collaboration, syncing, and permissions
Automation that can cause harm without human review

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Sitebulb is a technical SEO website crawler and audit tool (Sitebulb Ltd.) sold as a desktop app for Windows/macOS plus a browser-based 'Sitebulb Cloud' edition. Per the official feature/product pages, it crawls sites like a search engine and flags issues for professional SEOs. Core verified capabilities: JavaScript crawling via an Evergreen Chromium renderer (like Googlebot) with a 'Response vs Render' diff report; 'all you can eat' crawling with no per-URL credits, unlimited projects/domains, and up to 10M URLs per audit in Cloud; crawl maps visualizing site structure and spider traversal; performance audits collecting Core Web Vitals and running Lighthouse across the whole site; structured-data validation against Google/Schema.org; indexability checks (robots directives, canonicals, robots.txt); internal-link and broken-link/redirect reports; on-page analysis (thin/duplicate content,

SOURCES

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a focused replacement for the Sitebulb-style technical SEO crawler: a tool an SEO runs against their own site (or a client's) to surface technical issues before they hurt rankings. Do not reproduce Sitebulb's brand, logo, proprietary assets, or UI; use original naming and design. Core workflow: (1) user enters a seed URL and crawl config (depth limit, concurrency, include/exclude regex, respect-robots toggle, JS-render on/off); (2) a polite crawler queues, dedupes and fetches URLs with configurable rate limiting; (3) results land in an issue dashboard grouping findings by category (indexability, links/redirects, on-page, structured data, performance, duplicate content, missing metadata) with severity counts and affected-URL lists; (4) a URL explorer lets the user filter/sort/search the full URL table and choose visible columns; (5) drill into single-page detail (status code, title, meta description, canonicals, H1s, headings, img alt, internal/external links, response time, render vs source diff if JS enabled); (6) export reports to HTML/CSV; (7) optional scheduled re-crawls and a crawl-vs-crawl diff view. Technical: choose Node.js/TypeScript or Python; use Playwright/Puppeteer (headless Chromium) only for the optional JS-render pass; store data in SQLite/Postgres; produce static HTML reports; schedule via cron. The built-in 'hints' engine should be rule-based (regex/heuristics), not AI. Suggested Lighthouse integration for per-page performance scores is optional. Explicit out-of-scope: SaaS billing/credits, multi-user collaboration, cloud-scale crawling of millions of URLs, GA/Search Console or keyword-data integrations, sentiment analysis, security scanning, and full hreflang validation. Ship a README covering local setup, how to run a crawl and generate reports, architecture, and important limitations (local-machine crawl speed, robots/ToS compliance caveats, JS rendering resource costs, approximate hint accuracy).

Do not copy the original brand, proprietary assets, or UI; create an original visual system.

Visit the official product page