geo-optimize

A command that restructures documentation so search engines and AI answer tools can find, quote, and use it more easily. AEO means Answer Engine Optimization, and GEO means Generative Engine Optimization.

In plain words
What is it for?
Use it for new, high-traffic, or reference documentation, especially before a launch or after an SEO audit.
Why use it?
It identifies why a document may not appear in direct answers or featured search results, then proposes targeted changes while protecting accuracy.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/sumologic/sumologic-documentation/geo-optimize
Clone the repo
git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02326
Opus 5 $0.00000 $0.01163
Sonnet 5 $0.00000 $0.00465
Haiku 4.5 $0.00000 $0.00233

Measured 2d ago against content hash fa00c2b77c83, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

geo-optimize scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/geo-optimize.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GEO Optimize — Generative Engine Optimization (AEO + GEO)

Rewrites and restructures documentation to improve discoverability in AI-powered search tools (ChatGPT, Perplexity, Gemini, Claude, and similar) and to surface content as direct answers in traditional search results. Covers both AEO (Answer Engine Optimization — featured snippets, "People also ask") and GEO (Generative Engine Optimization — LLM citation and extraction).

What this command does

When you invoke /geo-optimize, Claude will:

  1. Read the doc
  2. Diagnose the current state. Identify AEO and GEO gaps before making changes
  3. Propose specific improvements. Show the user what will change and why
  4. Apply approved changes. Rewrite only the sections the user approves
  5. Validate the result. Confirm the doc is more answer- and citation-ready without breaking accuracy

When to use this command

  • New docs for features that are frequently searched in AI tools or voice search
  • High-traffic docs that rarely appear in AI-generated answers or featured snippets
  • Concept and reference docs where accuracy and citability matter most
  • After /seo-audit flags AEO or GEO suggestions
  • Before a product launch to maximize early visibility

What this command does NOT change

  • Technical accuracy — never alter facts, steps, code, or configuration values
  • Voice and tone — keep the Sumo Logic style; do not introduce formal or robotic language
  • Doc structure beyond adding or enhancing specific sections
  • Content the user has not approved

Workflow

Step 1: Get the file

Ask for the file path if not provided. Read the complete file including frontmatter.

Step 2: Diagnose AEO and GEO gaps

Before proposing changes, assess the doc against the Five GEO Principles defined in geo-guide/SKILL.md — answer-first (BLUF), one page one question, question-style headings, FAQ sections, and structured metadata — and tell the user what you found.

Read the full file on GitHub · 219 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 219 lines · 0 tokens per session scan A fa00c2b77c83

Subscribe to this mod's changes

geo-optimize is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,326 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.