agentmods.dev

seo-audit

seo-audit is a command for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 26 tokens per session (1,979 once invoked), scanned A, original, MIT.

A review of a website's search-engine readiness, covering technical setup, page content, credibility signals, links, local listings, competitors, and visibility in AI answers.

In plain words
What is it for?
Use it to audit a full site or focus on technical SEO, content, local search, keywords, competitors, or AI answer visibility.
Why use it?
It brings ranking problems and missed content opportunities into one prioritized action plan instead of requiring separate checks.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the digital-marketing-pro plugin — 154 skills, 18 commands, 24 agents shipped together

not rated 806repo +14 4d ago A scan 26 tokens original MIT

Good fit Use it to audit a full site or focus on technical SEO, content, local search, keywords, competitors, or AI answer visibility.

Compare 6 commands from other repositories ↓
View source ↗ indranilbanerjee/digital-marketing-pro indranil.in
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add indranilbanerjee/digital-marketing-pro
Claude Code
/plugin install digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 154 skills, 18 commands, 24 agents.

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-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/seo-audit/github.svg)](https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/seo-audit)
Your own site
<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/seo-audit"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/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.

agentmods 80×15 button for seo-audit

Your own site · 80×15
<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/seo-audit"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/seo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,979 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.00026 $0.01979
Opus 5 $0.00013 $0.00989
Sonnet 5 $0.00005 $0.00396
Haiku 4.5 $0.00003 $0.00198

Measured 11d ago against content hash 532e9ae8edc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

commands/seo-audit.md · 171 lines

How it starts

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

SEO Audit

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Audit a website's SEO health across all major ranking dimensions: technical infrastructure, on-page optimization, content quality, E-E-A-T signals, local SEO, link profile, and AI answer engine visibility. Produces a prioritized action plan with impact-to-effort scoring.

Trigger

User runs /digital-marketing-pro:seo-audit or asks for an SEO audit, keyword research, content gap analysis, technical SEO check, or competitor SEO comparison.

Inputs

Gather the following from the user. If not provided, ask before proceeding:

  1. URL or domain — the site to audit, or a topic/keyword if running in keyword research mode

  2. Audit scope — one of:

    • Full site audit — end-to-end SEO review covering all dimensions below (default)
    • Technical only — crawlability, Core Web Vitals, structured data, infrastructure
    • Content only — thin content, gaps, freshness, E-E-A-T, keyword opportunities
    • Local SEO — Google Business Profile, NAP consistency, local schema, reviews
    • Competitor comparison — head-to-head benchmarking against specific competitors

  3. Target keywords (optional) — specific keywords the site is targeting or wants to rank for

  4. Competitors (optional) — 2-3 domains to benchmark against. If not provided and comparison is needed, identify likely competitors from the keyword space.

Process

1. Keyword Research

If SEO tools are connected (Ahrefs, Similarweb):

  • Pull keyword data, search volume, difficulty scores, and current ranking positions automatically
  • Identify keywords gaining or losing ground

If tools are not connected:

  • Use web search to research the keyword landscape
  • Note: "For precise volume and difficulty data, connect an SEO tool via /digital-marketing-pro:connect ahrefs or /digital-marketing-pro:connect similarweb."

For each keyword opportunity, assess:

  • Search volume signals — relative demand (high, medium, low)
  • Keyword difficulty — how competitive (easy, moderate, hard)
  • Intent classification — informational, navigational, commercial, or transactional
  • Long-tail opportunities — specific, lower-competition phrases with clear intent
  • Question-based keywords — "how to", "what is" queries for People Also Ask

Read the full file on GitHub · 171 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. 11d ago First seen · 171 lines · 26 tokens per session scan A 532e9ae8edc2

Subscribe to this mod's changes

seo-audit is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (806 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 1,979 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.

Claude CodeMarketing and SEOaeoclaude-plugincontent-marketingmarketing-automationseo
Related

Other commands, from other repositories

brand-setup

Configure brand voice, terminology, compliance guardrails, and style guide for content production.

indranilbanerjee/contentforge · 16 tokens

output-folder

Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.

indranilbanerjee/contentforge · 20 tokens

create-content

Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.

indranilbanerjee/contentforge · 22 tokens

audit-content

Audit your content library for freshness decay, coverage gaps, and optimization opportunities.

indranilbanerjee/contentforge · 14 tokens

content-brief

Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.

indranilbanerjee/contentforge · 19 tokens

publish

Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.

indranilbanerjee/contentforge · 18 tokens