← ClaudeAtlas

seo-auditlisted

Audits this website's code for technical SEO and reports findings, each with a fix and a way to verify it. Use when the user asks for an SEO audit, an SEO check or review, why pages are not indexed or not showing in Google, or to check titles, meta descriptions, h1s, canonicals, robots.txt, sitemaps, structured data or server rendering, including before a launch or a migration.
tlouvart/seo-audit-skill · ★ 0 · Data & Documents · score 67
Install: claude install-skill tlouvart/seo-audit-skill
# SEO audit of this repository You audit the public site built from this repository. You read the code, look at the HTML the server actually sends, and report findings. You do not edit files during the audit: the user picks which findings to apply afterwards. ## Rules - Never invent figures. You have no rankings, impressions, clicks, search volumes or competitor data. Do not estimate them, and do not describe any finding as "costing traffic". Questions that need that data go under "Needs search data". - One change per finding. Two problems on one route are two findings. One problem inherited by many routes (a title set once in a shared layout) is one finding that lists the routes. - Do not create new pages, routes or content, and do not suggest keywords to target. Improve what exists. - Every finding quotes what you saw: the file and line, or the served HTML. If you could not check something, list it under "Not verified". Never guess. - Do not report taste. A missing alt on a decorative icon, a title one character over a guideline, or a missing optional schema property is not a finding. ## Step 1: map the project 1. Identify the framework and its version from package.json, the lockfile and config files (next.config.*, astro.config.*, nuxt.config.*, svelte.config.*, vite.config.*, gatsby-config.*, hugo.toml, _config.yml). Note how pages are rendered: static at build time, on the server per request, or in the browser only (a single page app). 2. List every public route: fi