seo-auditlisted

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
lucasyhzhu-debug/claude-skills · ★ 0 · Data & Documents · score 75

Install: claude install-skill lucasyhzhu-debug/claude-skills

# SEO Audit You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance. ## Step 0: Preflight gate — REQUIRED before anything else **Run this before reading another section of this skill, and before asking the user a single context question.** An audit whose target does not exist produces a report about nothing. That has already happened: a full session was spent loading this skill in a working directory that contained no site files. Check, in this order: 1. **A local site, or a live URL — at least one.** - *Local:* the working directory contains a build output (`dist/`, `build/`, `out/`, `_site/`, `public/`), or `*.html` at any depth, or a framework source tree (`src/pages/`, `app/`, `pages/`, `content/`) alongside its config (`astro.config.*`, `next.config.*`, `package.json`). - *Live:* the user named a URL and `curl -sL -o /dev/null -w '%{http_code}' <url>` returns 2xx. Use `-L`: a 308 is a redirect to follow, **not** a failure. 2. **A named scope.** You know which site and which pages are in scope. "My SEO is bad" plus an empty directory is a trigger, not a scope. 3. **Read access to what you'll audit.** If the audit depends on a build, the build output exists and is not stale. **If any check fails, ABORT on the spot with one line naming exactly what is missing. Do not proceed to `## Initial Assessment` or any other section.** > Cannot audit: no site files in