SEO-GEO Skill System for Claude Code & Claude.ai — 5 connected skills: Collector → Auditor (/90) → Implementer → Monitor. Technical SEO, Core Web Vitals, E-E-A-T, Entity SEO, AI visibility (ChatGPT, Perplexity, Claude), competitive analysis. English by default.
Skill Claude CodeCodex
Automated SEO data collector. Crawls a website and produces a structured site-data.json file containing: title/meta/H1 tags, robots.txt, sitemap, HTTP headers, Core Web Vitals (via PageSpeed Insights), schema markup detection, AI bot access analysis in robots.txt, and sample page snapshots. Optionally integrates…
Skill Claude CodeCodex
Performs an expert SEO audit (Local or General) + full GEO analysis: Technical SEO, Core Web Vitals, E-E-A-T, Entity SEO, GEO (AI visibility), UX-Conversion, and competitive analysis with scores /90 and a prioritized action plan. Use this skill for: SEO audit, local/national SEO, Google Business Profile, keyword gap…
Skill Claude CodeCodex needs its repo
SEO fix file generator. Reads the audit-actions.json produced by seo-geo-audit and generates ready-to-deploy fix files: rewritten meta tags, JSON-LD schema blocks, robots.txt corrections, .htaccess redirects, optimized content snippets, and an implementation checklist. Use this skill for: "generate the fixes", "create…
Skill Claude CodeCodex
SEO monitoring and delta tracking. Re-runs the collector on a previously audited site, compares current data against the baseline from the first audit, and produces a delta report showing improvements, regressions, and alerts. Use this skill for: "monitor my SEO", "check if the fixes worked", "compare my site to the…
Skill Claude CodeCodex
Contexte partagé du système SEO-GEO. Contient le profil client, les standards SEO de référence et les conventions de rapport. Ce skill est chargé automatiquement par les autres skills du pipeline SEO (seo-collector, seo-geo-audit, seo-implementer, seo-monitor). Ne pas utiliser directement — il sert de couche de…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: