What problem does it solve? Launching a website without checking crawlability, security headers, performance, and AI search visibility leads to deindexation, leaked secrets, and lost traffic that are expensive to fix after go-live. This Skill runs a coordinated pre-launch audit and delivers a prioritized fix list tailored to the detected tech stack. ## Core Features & Use Cases - Five orchestrated sub-audits: technical SEO, AI accessibility, security, performance, and on-page SEO, each with its own playbook of checks, tool calls, and severity classifications. - Stack detection and tailored checks: fingerprints frameworks like Next.js, WordPress, Shopify, and Webflow via headers, HTML signatures, and DNS, then injects stack-specific checks such as ISR cache validation or Supabase RLS probing. - Cross-connected prioritized report: deduplicates findings across sub-audits, ranks them P0-P3 by business impact, and includes stack-specific fixes with verification commands. - Use Case: Before pushing a Next.js staging site to production, ask for a pre-launch audit to catch a staging canonical leak, Cloudflare Bot Fight Mode blocking AI crawlers, and missing security headers in one report. ## Quick Start Ask Claude Code to run a pre-launch audit on your staging site URL, for example by saying: run a pre-launch audit on https://staging.example.com.
