Launching today

SEO Scrubbox

Launching today

Technical SEO checks for the AI search era

12 followers

Technical SEO checks for the AI search era

12 followers

Visit website

Technical SEO & live visual crawling: AI checks, canonicals, rendering diffs, redirects, sitemaps, hreflang, JSON-LD, CrUX.

Free

Launch tags:Chrome Extensions•SEO•Artificial Intelligence

Launch Team

FramerLaunch websites with enterprise needs at startup speeds.

Promoted

Maker

📌

Hey Product Hunt 👋 I built SEO Scrubbox because I kept running into the same problem in technical SEO: you often need several different tools just to understand how a page is actually seen by search engines, AI crawlers, and rendered-page systems. SEO Scrubbox brings those checks into one lightweight Chrome extension. It helps you compare source vs rendered content, check canonicals, robots directives, redirects, JSON-LD, hreflang, internal links, sitemaps, Core Web Vitals, security headers, caching, and AI crawler access from robots.txt. I also added ScrubberCrawl, a live visual crawler that maps URLs as it discovers them, with filters, crawl depth views, metric-based node sizing, and CSV export. The goal is simple: make it faster to diagnose what crawlers and AI systems may actually be working with, without jumping between lots of tools. It’s free while I keep improving it, and I’d genuinely love feedback from SEOs, developers, and anyone working on AI search visibility.

Report

17h ago

@charles_vayssie Love the focus on technical SEO and visual crawling in one place. How do you handle JavaScript-heavy sites where rendering issues, indexing problems, and structured data errors often only appear after the page is fully rendered?

Report

4h ago

Maker

Thanks @nicole_hynek ! That’s exactly one of the problems I wanted to make easier to debug.

SEO Scrubbox checks both the raw source HTML and the rendered DOM, then compares the key SEO signals between the two. So if JavaScript changes the canonical, meta robots, title, meta description, H1 structure, internal links, JSON-LD, or data-nosnippet elements after rendering, it can flag those differences.

For JS-heavy sites, I also added rendered vs non-rendered comparison views, including link count and word count differences, so you can quickly spot cases where content or links only appear after client-side rendering.

The idea is not to fully replace a large crawler, but to make those “what does the crawler actually see?” checks much faster directly from the page.

Report

3h ago

Thanks @nicole_hynek ! That’s exactly one of the problems I wanted to make easier to debug.

The idea is not to fully replace a large crawler, but to make those “what does the crawler actually see?” checks much faster directly from the page.