awesome-seo-auditlisted

Read-only SEO and AI-discoverability audit of a site or codebase — technical SEO, programmatic and scaled-content safety, and agent/LLM readability (crawler access, snippet directives, render-blindness) — with evidence per finding, a SHIP / FIX / BLOCK verdict, and a baseline/diff mode that catches what a deploy quietly broke. Use when asked to audit SEO, check for thin or cannibalizing pages, judge whether LLMs and agents can read the site, confirm a release changed nothing that ranks, or 'проверь SEO'. Reports only; writes no content. Do not use for WCAG accessibility (awesome-accessibility-audit) or landing conversion mechanics (awesome-landing-audit).
khasky/awesome-agent-skills · ★ 8 · Code & Development · score 78

Install: claude install-skill khasky/awesome-agent-skills

# SEO Audit Audit a site or web codebase for how it performs in both classic search and AI/agent discovery, and whether a set of generated pages is safe to ship. It treats SEO surfaces as auditable artifacts — files, headers, markup, rendered output — not as vibes. Read-only: it reports findings and a verdict; it never writes content or edits files. For *fixing* the issues, hand the report to the relevant content/dev workflow. Three audit tracks plus a re-audit mode, run the ones in scope: - A. Technical SEO — the on-page and crawl fundamentals. - B. Programmatic and scaled-content quality gate — is a generated page set safe from thin-content, doorway, and borrowed-reputation penalties? - C. AI / agent readability — can LLMs, AI crawlers, and the agents acting for their users fetch, parse, cite, and operate this? - Re-audit — diff the current surfaces against a stored baseline; this is the after-a-deploy mode. ## Scope and method 1. Establish scope — one page, a page *type* (all `/location/*`), or the whole site. For a generated set, sample per cohort (page type), don't eyeball one page and generalize. 2. Build the URL set, and keep the count it started at — take `sitemap.xml` and every sitemap `robots.txt` names, add what an internal-link crawl from the entry point reaches, then subtract what is not a page: resource extensions (`.pdf`, `.jpg`, `.png`, `.svg`, `.css`, `.js`, `.xml`), feed and API paths (`/feed/`, `/wp-json/`, JSON endpoints), and URLs that differ from one