← ClaudeAtlas

seo-technical-auditlisted

Technical SEO audit of a static or mostly static website, either from its build folder before deploying or from the live site through its sitemap. Checks titles, descriptions, canonicals, hreflang pairs, headings, broken internal links and missing files, links through redirects, images without alt or size, Open Graph tags, JSON-LD that doesn't parse, sitemap.xml and robots.txt, with scripts/seo-audit.mjs (Node.js, no packages), and explains every finding with its fix. Use it before a launch or migration, after big content or template changes, as a build step that fails on errors, or when someone asks to audit, check or crawl a site for SEO problems, broken links, duplicate titles or hreflang errors.
sharabarinillia/SEO-GEO-Vercel-Playbook-Skill · ★ 1 · Data & Documents · score 78
Install: claude install-skill sharabarinillia/SEO-GEO-Vercel-Playbook-Skill
# Technical SEO audit Finds the mechanical problems that keep pages out of search or split their signals. It does not judge content quality or keywords (see `seo-metadata`), structured-data details (see `structured-data`) or speed (see `web-performance`). ## Steps 1. **Build the site** (`npm run build` or the project's command). The audit reads the output folder: `dist/`, `out/`, `build/` or `public/`. 2. **Run the audit** from the project root: ```bash node <skill>/scripts/seo-audit.mjs --dir dist --site https://www.example.com ``` - `--site` is the production origin. Without it, the home page's canonical is used. - On a live site: `--sitemap https://www.example.com/sitemap.xml` fetches every listed page; add `--check-links` to also request internal links that aren't in the sitemap. - `--json report.json` writes every finding; `--strict` also fails on warnings. 3. **Read the report.** Findings are grouped by check id. Errors keep pages out of search or break something; warnings cost ranking, clicks or requests. Look up each id in [references/checks.md](references/checks.md) for why it matters and how to fix it. 4. **Fix at the source,** never in the build output: the page template, the content file, the generator script or the CMS. Then rebuild and run the audit again until no errors remain. 5. **Keep it in the build** so mistakes can't ship. In `package.json`: ```json "scripts": { "postbuild": "node scripts/seo-audit.mjs --dir