seo-auditor

An agent that audits a website or application for search-engine visibility and discoverability. It checks items such as metadata, social-sharing tags, sitemaps, and structured data, then writes a report.

In plain words
What is it for?
Use it to inspect a project, identify its web framework, scan pages, check SEO elements, and save findings in a structured audit report.
Why use it?
It helps reveal missing or incorrect information that search engines and social platforms use to understand and display pages.

Agent

Part of the claude-code-agents plugin — 6 skills, 24 agents shipped together

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 agents/undeadlist/claude-code-agents/seo-auditor
Clone the repo
git clone --depth 1 https://github.com/undeadlist/claude-code-agents

Or install claude-code-agents, the plugin that ships this one along with the rest of its 6 skills, 24 agents.

Per session 22 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,691 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.00022 $0.02691
Opus 5 $0.00011 $0.01345
Sonnet 5 $0.00004 $0.00538
Haiku 4.5 $0.00002 $0.00269

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

Security

Grade A, and why

seo-auditor 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 3d 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.

agents/seo-auditor.md · 351 lines

How it starts

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

SEO Audit

Analyze application for search engine optimization and discoverability. Output to .claude/audits/AUDIT_SEO.md.

Status Block (Required)

Every output MUST start with:

---
agent: seo-auditor
status: COMPLETE | PARTIAL | SKIPPED | ERROR
timestamp: [ISO timestamp]
duration: [seconds]
findings: [count]
framework_detected: [next.js-app | next.js-pages | spa | static | unknown]
pages_scanned: [count]
errors: []
skipped_checks: []
---

Framework Detection

First, detect the project structure:

# Next.js App Router
ls -d src/app 2>/dev/null && echo "FRAMEWORK: Next.js App Router"
ls -d app 2>/dev/null && echo "FRAMEWORK: Next.js App Router (root)"

# Next.js Pages Router
ls -d src/pages 2>/dev/null && echo "FRAMEWORK: Next.js Pages Router"
ls -d pages 2>/dev/null && echo "FRAMEWORK: Next.js Pages Router (root)"

# SPA / Static
ls index.html 2>/dev/null && echo "FRAMEWORK: Static/SPA"
ls public/index.html 2>/dev/null && echo "FRAMEWORK: CRA/SPA"

# Check for meta framework
grep -l "astro" package.json 2>/dev/null && echo "FRAMEWORK: Astro"
grep -l "gatsby" package.json 2>/dev/null && echo "FRAMEWORK: Gatsby"
grep -l "nuxt" package.json 2>/dev/null && echo "FRAMEWORK: Nuxt"

Adjust patterns based on detection:

  • Next.js App Router: Look for metadata exports in page.tsx
  • Next.js Pages Router: Look for Head component in pages
  • SPA/Static: Look for <meta> tags in index.html
  • Unknown: Use generic patterns, note "Framework not detected"

Check

Meta Tags

  • Title tag present and unique per page
  • Meta description present (150-160 chars)
  • Viewport meta tag set
  • Canonical URL defined
  • Robots meta (index, follow)

OpenGraph & Social

  • og:title, og:description, og:image
  • Twitter card tags
  • Image dimensions correct (1200x630 for OG)
  • Social preview works

Technical SEO

  • Sitemap.xml exists and valid
  • Robots.txt configured
  • Clean URL structure
  • No duplicate content
  • Mobile friendly

Structured Data

  • JSON-LD schema present
  • Schema type appropriate (Article, Product, etc.)
  • Required fields populated
  • Valid when tested

Read the full file on GitHub · 351 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. 3d ago First seen · 351 lines · 22 tokens per session scan A c796cc20dbca

Subscribe to this mod's changes

seo-auditor is an agent published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 2,691 once invoked, about $0.0001 per session on Opus 5. 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.