agentleFS
lcrvl2lcrvl2/seo-skills/skills/seo-audit-geo/SKILL.md

seo-audit-geo

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Analyse GEO (Generative Engine Optimization) d'un site — sa visibilité dans les réponses des IA génératives (ChatGPT, Perplexity, Google AI Overviews). Couvre l'intégralité de la méthode (phase 5) : accès bots LLM (matrice par bot), llms.txt, structure AEO scorée sur le contenu réel (answer-first, listes, tableaux, FAQ, définitions), JS-rendering, entité (Organization/Person/FAQPage schema completeness, Wikidata, cohérence de marque), et visibilité LLM (mentions, sentiment, citations). Architecture hybride : socle script (schema, robots, URL) + jugement agent (structure du contenu via WebFetch). Use when running the GEO part of a SEO audit, after seo-collect. Triggers : "audit GEO de <client>", "/seo audit-geo <client>".

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.