seo-audit-skill — Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

108 audit rules across 12 categories
Core Web Vitals via Lighthouse integration
Structured data (JSON-LD) validation
Security header check (CSP, HSTS, X-Frame-Options)
Accessibility basics (alt text, ARIA, heading order)
Output as markdown or JSON for downstream tooling

Démo en direct

Aperçu en pratique

seo-audit-skill.replay ▶ prêt

0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : seo-audit-skill

How to run your first full SEO audit and prioritize fixes

👤 Site owners and SEO practitioners who inherit a site with unknown SEO health ⏱ ~30 min beginner

Quand l'utiliser : New project, new site, or pre-launch checklist.

Déroulement

Run full audit

Run seo-audit-skill on https://example.com — all 108 rules, output markdown.✓ Copié

→ Report with per-rule pass/fail and a category summary
Prioritize by impact

Group the failures into 'ship this week' (high impact, low effort) vs 'backlog'. Explain the cutoff.✓ Copié

→ Ranked fix list with rationale
Generate fix PRs

For the top 5 'ship this week' items, draft the code changes in a PR-ready diff.✓ Copié

→ Diffs for meta tags, headers, and structured data

Résultat : A sprint-sized SEO fix list with drafted diffs.

Pièges

Lighthouse scores vary run-to-run — Run 3 times, take median; skill supports --runs=3
Rules flag false positives on JS-heavy SPAs — Use --render=js to enable JS rendering; costs more time

Combiner avec : trae-skill

Run just the Core Web Vitals checks in CI

👤 Performance engineers wiring SEO to CI ⏱ ~20 min intermediate

Quand l'utiliser : You want a CI gate that blocks regressions in LCP/CLS/INP.

Déroulement

Scope to CWV category

Run seo-audit-skill --category=cwv on our staging URL.✓ Copié

→ Just the CWV rules with values
Wrap in CI

Generate a GitHub Actions step that runs this and fails if LCP > 2.5s.✓ Copié

→ YAML snippet with threshold logic

Résultat : A CI gate that catches perf regressions before prod.

Pièges

CI runner is slower than users — Use field data via CrUX where possible; treat lab data as a regression detector, not absolute target

Validate and fix structured data (JSON-LD)

👤 Developers wanting rich results in SERPs ⏱ ~25 min intermediate

Quand l'utiliser : Your pages aren't getting rich snippets despite having JSON-LD.

Déroulement

Scope to structured-data rules

Run seo-audit-skill --category=structured-data on these 5 URLs.✓ Copié

→ Per-URL list of schema errors and missing required fields
Generate corrected JSON-LD

For each error, produce the corrected JSON-LD snippet keyed to the page type.✓ Copié

→ Per-page snippets ready to paste

Résultat : Schema.org-valid JSON-LD deployed; ready to re-check via Google Rich Results Test.

Pièges

Schema valid but Google still doesn't show rich results — Validity is necessary, not sufficient. Check eligibility guidelines for the specific rich result type.

Audit and set security headers

👤 Developers wanting baseline security + SEO signal ⏱ ~45 min intermediate

Quand l'utiliser : securityheaders.com gave you an F and you want to understand why.

Déroulement

Run security category

Run seo-audit-skill --category=security on https://example.com.✓ Copié

→ CSP, HSTS, X-Frame-Options, Referrer-Policy status
Generate headers config

Produce the nginx and Cloudflare Worker configs to set the missing headers safely (report-only CSP first).✓ Copié

→ Copy-paste configs with report-only CSP

Résultat : A secure header config rolled out behind report-only mode.

Pièges

Enforcing CSP breaks the site — Always start with Content-Security-Policy-Report-Only; watch reports for 1-2 weeks before enforcing

Combiner avec : claude-code-owasp-skill

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

seo-audit-skill + trae-skill

TRAE scaffolds SEO basics, seo-audit verifies them

Scaffold SEO with TRAE, run seo-audit to verify, fix gaps.✓ Copié

seo-audit-skill + claude-code-owasp-skill

Security-header subset of SEO overlaps with OWASP checks

Run seo-audit security category, then OWASP skill for deeper security review.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
full_audit	url: str, runs?: int, render?: 'js'\|'static'	First audit on a site	0
category_audit	url, category: 'cwv'\|'security'\|'structured-data'\|...	Focused checks or CI	0
diff_fix_generator	report, top_n?	After audit, to turn findings into PRs	Claude tokens

Coût et limites

Coût d'exécution

Quota d'API: None. Runs locally via headless Chromium.
Tokens par appel: Report interpretation uses 5-15k Claude tokens depending on site size
Monétaire: Free
Astuce: Use --category= to avoid running all 108 rules when you only need a subset.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials

Sortie de données : Fetches the target URL and its assets. Does not send report to any third party.

Running against authenticated/intranet URLs requires you to pass cookies — don't hardcode session tokens.

Dépannage

Erreurs courantes et correctifs

Puppeteer fails to launch

Install Chrome dependencies: apt-get install libgbm1 libnss3 (Linux) or run npx puppeteer browsers install chrome

Vérifier : node -e 'require("puppeteer").launch().then(b=>b.close())'

Rules flag modern JS framework features as problems

Use --render=js so the audit runs post-hydration

All CWV rules report N/A

Lighthouse lab mode; on slow connections it times out. Increase --timeout.

Alternatives

seo-audit-skill vs autres

Alternative	Quand l'utiliser	Compromis
Google Lighthouse CLI	You only need the canonical CWV/perf subset	No structured-data or SEO-specific rules
Screaming Frog	You need enterprise-grade crawling of large sites	Paid, desktop app, not LLM-integrated

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills