geo-audit

Validate llms.txt, AGENTS.md, JSON-LD, and robots.txt for GEO and AEO discoverability gaps.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill geo-audit-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: geo-audit
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/geo-audit
Command: npx skills add https://github.com/AAbdulghany/fms --skill geo-audit-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and surface GEO and AEO discoverability gaps in public docs and codebases by auditing artefacts such as llms.txt, AGENTS.md, AI-crawler directives, and JSON-LD citations to ensure accurate AI surface-up and citation grounding.

Core Features & Use Cases

  • Discovery validation: checks for essential artefacts like llms.txt, AGENTS.md, robots.txt directives, and JSON-LD metadata.
  • Capability signaling: ensures upstream manifest references and GEO/AEO scope are clearly defined.
  • Content-format hygiene: enforces structured metadata, snippet-friendly formatting, and safe prompt boundaries.
  • Token economics awareness: surfaces per-page token estimates and guidance for efficient prompts.
  • UX and adoption: provides guidance for AI-friendly copy and interaction points to improve discoverability.
  • Use Case: a documentation site can run the audit at milestone boundaries to verify readiness for LLM-based indexing and agent-based tooling.

Quick Start

Run the geo-audit against your web project to surface GEO/AEO readiness gaps and guide remediation.

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 site for LLM discoverability and AEO readiness?

Validate AEO readiness by checking llms.txt, AGENTS.md, JSON-LD, and robots.txt to surface discoverability gaps across six buckets (Discovery, Capability-signaling, Content-format, Token-economics, Analytics, UX) for accurate AI citation grounding.

What is GEO and AEO discoverability for web projects?

GEO and AEO discoverability ensures public docs and developer portals are correctly indexed by AI-crawlers through validated llms.txt files, AGENTS.md manifests, and structured JSON-LD metadata citations.

How do I validate llms.txt and AGENTS.md files for AI-crawler access?

Validate llms.txt and AGENTS.md files by running an audit that checks for essential artefacts, upstream manifest references, and robots.txt directives to verify agent-based tooling coverage and cross-links.

Can I run a GEO audit on a developer portal at milestone boundaries?

Yes, you can run a GEO audit on a developer portal at milestone boundaries or during landing-site work to verify LLM-based indexing readiness, skill manifests, and agent-crawler coverage.

What is the best way to check JSON-LD metadata and token economics for documentation sites?

Check JSON-LD metadata and token economics by auditing structured metadata, snippet-friendly formatting, and per-page token estimates to enforce safe prompt boundaries and efficient LLM indexing.