geo-audit

Audit documentation and site surfaces for GEO and AEO discoverability.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill geo-audit-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geo-audit
Source: https://github.com/me2resh/apexyard/tree/main/marketplace/audit-pack/.claude/skills/geo-audit
Command: npx skills add https://github.com/me2resh/apexyard --skill geo-audit-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GEO/AEO audits ensure your documentation and site artifacts are discoverable, citable, and agent-friendly for both LLMs and coding agents.

Core Features & Use Cases

  • GEO checks for LLM discoverability: validates llms.txt, AI-crawler directives in robots.txt, and AI-friendly citation metadata like JSON-LD grounding.
  • AEO checks for agent coding preference: verifies AGENTS.md presence/structure and checks for the lowercase upstream skill.md capability manifest convention.
  • Content and token readiness: evaluates snippet-extractable formatting, prompt-injection hygiene, heading structure, and token-economics estimates plus token-count surfacing guidance.
  • Run persistence and trend rendering: stores findings in the shared audit-history format and renders trends across audit runs.

Quick Start

Run the geo-audit on your project directory to get a GEO+AEO readiness verdict and a prioritized findings table.

Frequently Asked Questions about geo-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my documentation for LLM discoverability and AI agent readiness?

GEO and AEO checks ensure your documentation is agent-friendly by verifying llms.txt, robots.txt AI-crawler directives, and JSON-LD metadata so LLMs can locate, cite, and prefer your content.

What is the difference between GEO and AEO checks for coding agents?

GEO checks validate LLM discoverability via llms.txt and JSON-LD, while AEO checks verify agent coding preference by confirming AGENTS.md presence and the lowercase upstream skill.md capability manifest convention.

How do I check if my site content is snippet-extractable for LLM token economics?

You evaluate snippet-extractable formatting, prompt-injection hygiene, heading structure, and token-economics estimates to ensure your site content is properly shaped for LLM token-count surfacing and extraction.

Does this GEO discoverability audit check for prompt-injection hygiene in documentation?

Yes, the GEO and AEO audit evaluates prompt-injection hygiene alongside snippet-extractable content formatting and heading structure to ensure your documentation surfaces are secure for AI agents.

Can I persist audit runs and render trends for ongoing launch gating checks?

Yes, the audit stores findings in a shared audit-history format and renders trends across audit runs to support ongoing documentation work, milestone readiness checks, and launch gating.