Aeo Audit logo

Aeo Audit

Community
indranilbanerjee
aeo-audit

Run a one-time AEO audit of six AI answer engines, scored per surface. "check our AI search visibility"

Overview

Publisherindranilbanerjee
Repositorydigital-marketing-pro
Skill nameaeo-audit
Stars
866
Forks
138
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by indranilbanerjee on GitHub. Read the source before you install it.

Installation

Install the Aeo Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/aeo-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git /tmp/digital-marketing-pro
mkdir -p .claude/skills
cp -r /tmp/digital-marketing-pro/skills/aeo-audit .claude/skills/aeo-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Aeo Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Aeo Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Aeo Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/digital-marketing-pro:aeo-audit

Purpose

Evaluate the brand's visibility and accuracy across AI answer engines. Analyze how the brand is cited, described, and recommended by ChatGPT, Perplexity, Google AI Mode (the conversational search surface that became Google's default at I/O 2026 — ~1B MAUs as of May 2026), Google AI Overviews, Gemini, and Microsoft Copilot. Produce optimization recommendations to improve AI visibility.

AI Mode vs AI Overviews — why both matter: AI Overviews are the summary block at the top of a classic Google SERP and trigger on a subset of queries. AI Mode is a conversational tab (and now the default search experience for opted-in users) backed by Gemini 3.5 Flash with deeper reasoning, follow-ups, and a different citation pattern. The two surfaces select different sources for the same query in a large share of cases (internal observation, 05/2026 — "40–60%" is a rough estimate; re-verify against your own probe set). Audit both.

Cross-reference with GSC AI Performance Report (rolled out 3 June 2026): The Google Search Console AI Performance Report (UK rollout first, global to follow) gives you actual impressions in AI Overviews + AI Mode for verified properties. Synthetic probe results from this skill should be reconciled against GSC actuals — see /digital-marketing-pro:gsc-ai-performance for the workflow. Important caveat: the GSC report intentionally excludes click data; click-through attribution must come from GA4 (the new AI Assistant channel group, added 13 May 2026, captures Medium=ai-assistant referrals from ChatGPT/Gemini/Claude; see /digital-marketing-pro:analytics-insights).

Google's official position on AI optimization (Google AI Optimization Guide, updated 15 May 2026): no llms.txt, no AI-specific schema, no separate AI eligibility gate. Pages eligible for snippets in classic Search are eligible for AI Features. Don't manufacture work around fictional ranking factors — /digital-marketing-pro:aeo-geo documents what does work (entity consistency, citation-worthy snippets, knowledge graph alignment).

Information Agents (Google AI Pro / Ultra, summer 2026 launch): Google announced at I/O 2026 a new class of persistent agents that continuously monitor web / news / real-time data for subscribers and deliver synthesized updates with actionable capabilities. Once these go live, they become a 7th probe target for this skill (alongside ChatGPT / Perplexity / AI Mode / AI Overviews / Gemini / Copilot). Until then, treat AI Mode as the proxy — agents are powered by the same Gemini 3.5 Flash backbone. Source: blog.google/search-io-2026.

Input Required

The user must provide (or will be prompted for):

  • Brand name: The brand to audit
  • Website URL: Primary domain
  • Key queries: 5-10 queries a potential customer might ask that should surface the brand
  • Competitors: 2-3 competitors for comparison
  • Product/service categories: What the brand should be known for

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Define a test query set: branded queries, category queries, comparison queries, "best of" queries, problem-solution queries
  3. Analyze how the brand appears in AI responses for each query type
  4. Check citation accuracy: Are facts correct? Are URLs valid? Is the description current?
  5. Compare brand mention frequency and sentiment against competitors
  6. Assess source authority: Which sources are AI engines pulling brand info from?
  7. Evaluate structured data and knowledge panel presence
  8. Identify content gaps where the brand should appear but does not
  9. Generate optimization recommendations for improved AI visibility

Output

A structured AEO audit report containing:

  • AI visibility scorecard across platforms (ChatGPT, Perplexity, Google AI Mode, Google AI Overviews, Gemini, Microsoft Copilot)
  • Query-by-query results showing where the brand appears, how it is described, and citation sources
  • Competitor comparison matrix for AI visibility
  • Citation accuracy assessment with corrections needed
  • Source authority analysis — which pages/sites drive AI mentions
  • Content gap list — queries where the brand is absent but should appear
  • Optimization playbook: structured data, content strategy, authority building, and entity optimization

Numbered output convention

All AEO audit outputs go to ${CLAUDE_PLUGIN_DATA}/{brand}/seo/aeo-audit/{YYYY-MM-DD}/:

00-input.md                 brand identity, target query set, competitor list, AI platforms probed
01-query-set.md             the 10-25 queries probed, with intent classification
02-probe-results.json       raw probe responses per platform per query (the data layer)
03-platform-scorecard.md    visibility scorecard per AI platform (1-10) with diff vs prior run
04-citation-accuracy.md     fact-by-fact accuracy check of AI descriptions; what to correct
05-source-authority.md      which pages/sites are driving AI mentions; topical entity map
06-content-gaps.md          queries where brand is absent but should appear
07-competitor-matrix.md     side-by-side AI presence vs competitors
08-quality-scorecard.md     the gates below
09-optimization-playbook.md  structured data, content, authority, entity work — sequenced
PLAN.md                     single-page deliverable

Reconcile 03-platform-scorecard.md against /digital-marketing-pro:gsc-ai-performance actuals — probe results show what AI could surface; GSC shows what it actually surfaced.

Quality scorecard

GateWhat it checks
query_set_size≥ 10 queries probed (below this, results are anecdotal)
platform_coverage≥ 4 of the 6 supported platforms probed (ChatGPT, Perplexity, AI Mode, AI Overviews, Gemini, Copilot)
competitor_coverage≥ 2 competitors probed alongside the brand on same query set
citation_accuracy_doneEvery "brand appears" result has been fact-checked (no silent ship of "AI said X — sounds right")

status: ready requires all four gates pass.

AI-visibility scoring standard (canonical — reused across the plugin)

This skill defines the plugin's single AI-visibility scoring standard. Every AI-visibility surface reuses it — do not invent a parallel model.

  • Canonical surfaces (6): Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, Microsoft Copilot. This exact set is the PLATFORMS constant in scripts/geo-tracker.py — reference that constant, don't re-list a different set.
  • Canonical rubric: the per-platform 1-10 visibility score plus the four gates above. Score each platform separately; never average across platforms (a brand can be 9/10 on Perplexity and 2/10 on ChatGPT — the average misleads).
  • Recurring mode: /digital-marketing-pro:geo-monitor applies this same rubric on a schedule (weekly / monthly) and tracks it over time. The 0-100 GEO health score + A-F letter grade that geo-tracker.py emits is the trend view of the same underlying data — a longitudinal roll-up, not a second scoring model.
  • Consumers: geo-monitor (recurring), share-of-voice (its AI dimension), rank-monitor (AI Overview citation presence in --features mode). All reconcile synthetic probe scores against GSC actuals via /digital-marketing-pro:gsc-ai-performance.

Chain handoffs

  • Upstream: /digital-marketing-pro:aeo-geo for the strategy framing this audit measures against
  • Downstream:
    • /digital-marketing-pro:gsc-ai-performance — reconcile synthetic probe results against GSC actuals
    • /digital-marketing-pro:keyword-cluster — 06-content-gaps.md becomes seed input for clustering
    • /digital-marketing-pro:entity-audit — drives 05-source-authority.md corrections in Knowledge Graph
    • /digital-marketing-pro:seo-drift — next quarter, compare two AEO snapshots

Tips & caveats

  • AI Mode and AI Overviews frequently disagree on the same queries (internal observation, 05/2026 — the "40-60%" figure is a rough estimate, re-verify against your own probe set) — always probe both separately, never roll them into "Google AI".
  • Don't probe more than 25 queries per session. Beyond that, model rate limits + token cost dominate. Pick the 10-25 highest-value queries.
  • Citation accuracy is the audit's most-skipped step. AI engines confidently hallucinate brand facts; if you don't fact-check, you're certifying wrong info. Always check at least the top-cited fact per platform.
  • Synthetic probes overstate presence. Real users phrase queries differently than the test set. The cross-reference with the GSC AI Performance Report (3 Jun 2026, UK first) is what tells you actual impressions.
  • Score the probe results, don't average platforms. A brand can score 9/10 on Perplexity (cites everyone) and 2/10 on ChatGPT (selective citing) — the average misleads. Report per-platform scores side by side.

Agents Used

  • seo-specialist — AI search analysis, entity optimization, structured data, citation strategy

Frequently asked questions

What does the Aeo Audit AI skill do?

Run a one-time AEO audit of six AI answer engines, scored per surface. "check our AI search visibility"

Why use Aeo Audit on TypingMind?

Because you install it once and use it with any model. Aeo Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Aeo Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/aeo-audit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Aeo Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Aeo Audit?

As many as you like. As long as a model supports skills, you can use Aeo Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Aeo Audit AI skill free?

Yes. It is published on GitHub by indranilbanerjee under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇