v0.7.0: JavaScript Rendering March 15, 2026 ## What’s New in v0.6.7 ### Client-Side Redirect Detection Crawler now detects redirects that happen inside the HTML body rather than through HTTP headers. Two patterns are supported: - **Meta refresh tags** \- `` is detected and recorded as a 302 redirect hop - **Next.js NEXT_REDIRECT** \- The `NEXT_REDIRECT;replace;/target;307;` pattern used by Next.js server actions is detected and recorded with its original status code ### Why This Matters Server-side redirects (301, 302, 307, 308) are already tracked through HTTP response headers. But many sites use client-side mechanisms to redirect users - either through meta refresh tags or framework-specific patterns like Next.js NEXT_REDIRECT. These redirects were previously invisible to the crawler, making redirect audits incomplete. Now, when a page returns a 200 status but contains a client-side redirect pattern, the crawler creates a synthetic redirect hop and adds it to the page’s redirect chain. This means SEO analysis, redirect audits, and orphan page detection all benefit from the fuller picture. ### Who Benefits - **SEO professionals** get complete redirect chain data that includes client-side redirects previously missed - **Next.js site owners** can audit NEXT_REDIRECT patterns alongside traditional HTTP redirects - **Content teams** can identify pages that appear to load but immediately redirect users elsewhere ## Wrap-up A CMS shouldn't slow you down. Crawler aims to expand into your workflow — whether you're coding content models, collaborating on product copy, or launching updates at 2am. If that sounds like the kind of tooling you want to use — [try Crawler](/content/download/index.html). Crawler runs locally on your machine. Use the CLI or the desktop app — your workflow, your terms.