A command that checks written documentation for signals used by search engines and AI answer tools. SEO means helping ordinary search engines find and rank a page; AEO and GEO focus on direct answers and AI-generated results.

Use it to audit a Markdown file or all Markdown files in a directory. It checks items such as the title, its length, and other search-related content signals.

It catches missing or weak document details before a pull request, including problems that can make content harder to find or quote accurately.

How SumoLogic/sumologic-documentation configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SumoLogic/sumologic-documentation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-documentation/main/.claude/commands/seo-audit.md

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/seo-audit/github.svg)](https://agentmods.dev/commands/sumologic/sumologic-documentation/seo-audit)

Your own site

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/seo-audit"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/seo-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sumologic/sumologic-documentation/seo-audit"><img src="https://agentmods.dev/badge/commands/sumologic/sumologic-documentation/seo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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,242 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02242
Opus 5.5	$0.00000	$0.00897
Sonnet 5.5	$0.00000	$0.00448
Haiku 4.5	$0.00000	$0.00224

Measured 2mo ago against content hash d7e8a6cc8827, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seo-audit 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 2mo 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/seo-audit.md · 206 lines

How it starts

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

SEO/AEO/GEO Audit — Search and AI Discoverability Check

Use this command to audit a doc for SEO, AEO, and GEO signals — run it before any PR on new or updated content, even if you're not focused on search optimization.

Signal definitions

SEO (Search Engine Optimization): signals that help traditional search engines rank and surface pages.

AEO (Answer Engine Optimization): signals that help search engines display the page as a direct answer (featured snippets, knowledge panels, "People also ask" boxes).

GEO (Generative Engine Optimization): signals that help LLM-powered tools (ChatGPT, Perplexity, Gemini, Claude) cite and quote the page accurately in generated responses.

Workflow

Step 1: Identify the file or directory

If the user provides a file path, read that file. If they provide a directory, find all .md files in it and audit each one, then produce a summary.

If no argument is given, ask the user for the file path.

Step 2: Read the file(s)

Use the Read tool to read the complete file content including frontmatter.

Step 3: Run SEO checks

Frontmatter

title present
title is under 60 characters — Critical if missing or over 60
title includes the primary keyword or product/feature name
description present — Critical if missing
description is 140–160 characters — Warning if under 100 or over 160; Suggestion if 100–139 (functional but below target)
description leads with an action verb or product name (not "This page" or "This doc")
keywords field present with 3–5 relevant terms — Suggestion if missing
No slug on a regular content page (breaks sidebar linking) — Critical if present

Headings

No H1 in body — title frontmatter generates H1; a second H1 breaks SEO — Critical if present
At least 2 H2 headings for pages over 500 words — Suggestion if none
No duplicate headings at the same level — Warning if duplicated
Headings are under 60 characters — Suggestion if over

Read the full file on GitHub · 206 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.

2mo ago First seen · 206 lines · 0 tokens per session scan A d7e8a6cc8827

Subscribe to this mod's changes

seo-audit is a command published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,242 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.

Marketing and SEO React Research Writing and docs documentation open-source

seo-audit next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
seo-auditSumoLogic/sumologic-documentation	Command	42	yesterday	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

sumologic-documentation: Command for Claude Code