seo-audit-technical
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Analyse technique SEO d'un site à partir du crawl déjà collecté dans la réserve. Produit des findings normalisés avec un critère de succès par recommandation (où tu en es / où tu dois arriver / comment on mesure). Couvre codes HTTP, canonicals, redirects, h1, meta, linking interne, images, hreflang, duplicates, contenu mince, Core Web Vitals. Use when running the technical part of a SEO audit, after seo-collect has filled the reserve. Triggers : "audit technique de <client>", "/seo audit-technical <client>".
- Reads credentials
In this repository17 other files it gives its agents.
- seo-osSkill
- article-createSkill
- content-brief-creatorSkill
- content-quality-evaluatorSkill
- content-refreshSkill
- seo-audit-backlinksSkill
- seo-audit-eeatSkill
- seo-audit-geoSkill
- seo-audit-manualSkill
- seo-collectSkill
- seo-content-pruningSkill
- seo-funnel-orchestratorSkill
- seo-monitoringSkill
- seo-publishSkill
- seo-reportSkill
- seo-strategySkill
- seo-weekly-recapSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.