seo

seo is a command for Claude Code from fatihkan/badi. It costs 0 tokens per session (852 once invoked), scanned A, original, MIT.

A website search-engine optimisation audit. Search-engine optimisation, or SEO, is the practice of making pages easier for search engines to understand and rank.

In plain words
What is it for?
Use it to check titles, descriptions, social-sharing tags, headings, image text, canonical URLs, robots.txt, sitemaps, HTTPS, structured data, and page speed.
Why use it?
It identifies missing page information, crawlability problems, accessibility-related gaps, and basic speed issues that can reduce discoverability.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

Good fit Use it to check titles, descriptions, social-sharing tags, headings, image text, canonical URLs, robots.txt, sitemaps, HTTPS, structured data, and page speed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fatihkan/badi/seo
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.

Clone the repo
git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

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.

agentmods badge for seo

README.md
[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/seo.svg)](https://agentmods.dev/commands/fatihkan/badi/seo)
Your own site
<a href="https://agentmods.dev/commands/fatihkan/badi/seo"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/seo.svg" alt="Measured on agentmods" 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 852 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00852
Opus 5 $0.00000 $0.00426
Sonnet 5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

Measured today against content hash 9c7ae9c6c42c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

seo 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 today.

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.md · 84 lines

How it starts

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

SEO audit command. Website SEO analysis, meta tag checks, sitemap validation, and speed assessment.

Required Tools

  • Bash (badi seo commands)

Procedure

Step 1: Define the Scope

Ask the user: "Which analysis shall we run?"

  • Full audit — 20+ checks (recommended starting point)
  • Meta tags — OG, Twitter Card detail
  • Sitemap + robots.txt — Crawlability
  • Speed + resources — Performance starter

Step 2: SEO Audit (Default)

badi seo audit [url]

What is checked:

  • Title, Description, OG tags, Twitter Card
  • H1 structure (must be single)
  • Image alt tags
  • Canonical URL, Viewport, lang, charset
  • HTTPS, Schema.org, robots meta
  • Word count, link analysis

An SEO score of 0-100 is given.

Step 3: Detailed Analyses

badi seo meta [url]        # Meta tag analysis (missing detection)
badi seo sitemap [url]     # robots.txt + sitemap.xml
badi seo speed [url]       # TTFB + HTML size + compression

Step 4: Improvement Suggestions

If the score < 80, based on the findings:

  • Title missing/long: 30-60 character suggestion
  • No description: 120-160 character example
  • H1 problem: page structure suggestion
  • Missing image alts: combined WCAG + SEO benefit
  • No canonical: duplicate-content risk
  • No Schema.org: structured-data opportunity

Step 5: Lighthouse Deep Analysis

For deeper metrics:

badi lighthouse [url]

Core Web Vitals + Performance + Accessibility + Best Practices + SEO score.

Step 6: AI Search Optimization (GEO/AEO)

Per Google's 2026 guidance, optimizing for AI features (AI Overviews, AI Mode) IS SEO — they pull from the same Search index via retrieval + query fan-out, so there is no separate "AI index" to target and indexability is AI visibility. Verify live (this space moves fast), but the durable levers:

  • No special files or schema for Google AI — Google explicitly ignores llms.txt and requires no AI-specific schema or content "chunking." Don't waste effort there; foundational SEO + original, non-commodity content is the lever. (Other engines may read llms.txt, but none have committed to acting on it — don't rely on it.)
  • Lead with the answer + evidence — front-load the substantive answer and original data/statistics/citable claims; studies show AI engines preferentially quote early, evidence-rich passages.
  • Earn off-site brand mentions — authentic third-party mentions/press correlate with AI citation more than backlinks; build distribution, not just links.
  • Structured-data hygiene — schema still aids eligibility, but FAQ rich results were deprecated (2026); audit and remove inert FAQ markup.
  • Measure AI visibility, not just clicks — clicks fall when AI answers appear while brand exposure rises; track the Search Console Gen AI (AI feature) impression report + branded-search volume. Don't block Google-Extended expecting to control AI Overviews — it governs Gemini Apps, not Search AI features.
  • Preferred Sources — if you run a publisher/brand, add Google's Preferred Sources button (the official user-level mechanism to surface in Top Stories / AI features).

Read the full file on GitHub · 84 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. today First seen · 84 lines · 0 tokens per session scan A 9c7ae9c6c42c

Subscribe to this mod's changes

seo is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 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-09-06.