agentleFS
peakanswerpeakanswer/peak-answer-skills/skills/geo-audit/SKILL.md

geo-audit

Skill0 starsChanged 49 days agoMITView on GitHub

Audit a site for whether AI search engines can reach, read and quote it. Use when someone asks why ChatGPT or Perplexity does not cite their site, wants a GEO or AEO audit, asks about AI crawler access, or is about to start optimising for AI search and needs a baseline.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use geo, seo-local and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ORBWEVASkill

    geo

    Generative Engine Optimization — optimize content for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Gemini). Use when user wants to rank in AI search, improve AI citability, audit content for LLM visibility, or explicitly invokes /geo commands. Triggers on "GEO", "generative engine", "AI search", "AI overviews", "citability", "Perplexity", "ChatGPT search", or /geo commands.

    Also in 7 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 3 projects that use this

  • megastepSkill

    seo-schema

    Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the rules properly. Disallow: / under User-agent: * blocks every agent that has no more specific block of its own.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GEO audit

Work out whether the AI engines can reach a site, read it, and find something quotable on it. In that order, because the later checks do not matter if the earlier ones fail.

Run the checks in dependency order

A site that blocks GPTBot does not have a schema problem. Fix the top of this list before reporting anything below it.

1. Crawler access

Fetch https://<domain>/robots.txt and check each of these user agents by name. They are separate crawlers with separate jobs, and blocking one does not imply the others:

AgentOperatorWhat blocking it costs
GPTBotOpenAITraining and, in practice, retrieval coverage
OAI-SearchBotOpenAIChatGPT search results specifically
ChatGPT-UserOpenAILive fetches when a user asks about your page
ClaudeBotAnthropicClaude's index
Claude-UserAnthropicLive fetches during a Claude conversation
PerplexityBotPerplexityPerplexity's index
Perplexity-UserPerplexityLive fetches
Google-ExtendedGoogleGemini and AI Overviews grounding
BingbotMicrosoftBing and Copilot
Applebot-ExtendedAppleApple Intelligence

Read the rules properly. Disallow: / under User-agent: * blocks every agent that has no more specific block of its own. A more specific group wins outright — an agent named in its own group ignores the wildcard group entirely, it does not merge with it.

Also check for the mistakes that look fine:

  • A Disallow: with no path means allow everything. A Disallow: / blocks everything. One character.
  • Crawl-delay is ignored by most of these agents. It is not a block, so do not report it as one.
  • A 404 on /robots.txt allows everything. A 500 is treated as a full block by several crawlers, which is much worse than not having the file.
  • Cloudflare bot rules, a WAF, or a "verify you are human" interstitial can block a crawler while robots.txt reads permissive. Fetch a real page with each user agent string if you can, rather than trusting the file.

2. The page actually resolves for a crawler

Fetch the homepage and two deep pages with a plain client, no JavaScript. Check:

  • Status is 200, not a redirect chain ending somewhere unexpected.
  • The main content is in the HTML. If the body is an empty <div id="root">, the content is client-rendered and several of these agents will see nothing. This is the single most common silent failure.
  • No noindex in a meta tag or X-Robots-Tag header.
  • The canonical, if present, points where you expect. A canonical pointing at a different page hands the citation to that page.

3. What the engines look for once they can read it

  • llms.txt at the root. Absent is not fatal and its adoption is genuinely contested, so report it as a small opportunity rather than a fault. See the llms-txt skill for what belongs in one.
  • Structured data. Organization and WebSite on the homepage, Article on posts, FAQPage where there are real questions and answers, Product with offers on product pages. Validate it parses; invalid JSON-LD is worth less than none because it looks done.
  • Answer structure. Whether a page states its answer near the top, has real headings, and contains anything liftable like a comparison table or an FAQ. See the answer-readiness skill.
  • Sitemap at /sitemap.xml, referenced from robots.txt, returning 200 and listing live URLs.

What to report

Ordered by what blocks what, with the fix beside each finding. Not a score with no instructions attached.

For each finding give: what is wrong, the evidence (the exact line of robots.txt, the URL that 404s), what it costs, and the specific change. "Add User-agent: GPTBot / Allow: / to robots.txt" is a finding. "Improve crawlability" is not.

Say what passed too. A list of only problems reads as a sales pitch and hides whether the important things are already fine.

Two honest caveats to include

  • Blocking a crawler is sometimes deliberate. Publishers block GPTBot on purpose. Ask before calling it a fault.
  • None of this makes an engine cite you. It makes citation possible. What gets cited is usually somebody else's article about the category, so a clean audit is the floor, not the win. Say so, or the report over-promises.

With the Peak Answer MCP connected

If the audit_site tool is available it runs this whole pass in one call and returns answer readiness, crawler access, robots.txt, sitemap, structured data, headings, meta description, readability and entities together. Use it for the baseline, then read the findings yourself rather than pasting them, because the ordering above is what makes a report actionable.

geo_audit is a different thing: it asks a real model ten real buying questions and takes minutes. It starts a background run and returns immediately, so call it once and collect the result later. Never block an audit on it.

Free, no signup: https://peakanswer.com/tools/ai-visibility-audit

Download now (ZIP)

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.