Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AgricIDaniel/claude-seo/llms.txt

Use this file to discover all available pages before exploring further.

/seo audit is Claude SEO’s flagship command. It crawls up to 500 pages of any publicly accessible site, detects the business type (SaaS, local, e-commerce, publisher, or agency), dispatches up to 15 parallel specialist subagents, and returns a SEO Health Score from 0 to 100 alongside two output files: FULL-AUDIT-REPORT.md and ACTION-PLAN.md. The action plan is not a generic checklist — every finding carries a first-principle observation, a dependency chain, a failure-mode check, and a leading indicator to monitor.

Syntax

/seo audit <url>
Example:
/seo audit https://example.com

What Happens When You Run It

1

Render the homepage

Claude SEO fetches the homepage using --render auto, which detects SPA frameworks (Next.js, React, Vue, Nuxt, Astro) and switches to a full Playwright Chromium render when needed. Raw HTML, rendered HTML, extracted text, SPA status, and accessibility data are all captured.
2

Detect business type

Signals from the homepage — pricing pages, location schema, product listings, portfolio structure — are used to classify the site as SaaS, local service, e-commerce, publisher, or agency. The detected type determines which conditional subagents are spawned.
3

Crawl up to 500 pages

Internal links are followed up to 500 pages with a 5-request concurrency limit, a 1-second crawl delay, and a maximum of 3 redirect hops per URL. robots.txt is respected throughout.
4

Dispatch parallel subagents

Up to 15 specialist subagents are launched simultaneously. Eight run on every audit; the remaining seven are conditional on detected business type, available credentials, or stored baselines.
5

Aggregate the SEO Health Score

Findings from all subagents are weighted and combined into a single 0–100 score.
6

Write output files

FULL-AUDIT-REPORT.md, ACTION-PLAN.md, audit-data.json, per-category finding files under findings/, and a screenshots/ folder (when Playwright is available) are all written to {domain}-audit/.
7

Offer a PDF report

After the markdown report is complete, Claude SEO offers to generate an enterprise-grade A4 PDF via WeasyPrint and matplotlib — cover page, table of contents, executive summary, Lighthouse gauges, query bars, an index donut, metric cards, and a phased implementation roadmap.
SPA rendering. --render auto (the default) detects empty <div id="root"> shells and single-bundle scripts, then switches to Playwright automatically. Use --render always to force rendering on every page or --render never for raw-HTML-only audits. Pages with scroll-bound hydration or post-interaction content fetches may still produce noisy findings; cross-check those with the seo-visual subagent’s Playwright snapshot.

The 7 Specialist Subagents

Every full audit spawns at least these seven dedicated agents in parallel. Additional agents (local, maps, ecommerce, backlinks, Google APIs, drift, cluster) are spawned conditionally based on business type and available credentials.
SubagentWhat It Covers
seo-technicalrobots.txt, sitemaps, canonicals, Core Web Vitals, security headers, IndexNow
seo-contentE-E-A-T signals, readability, thin content, AI citation readiness
seo-schemaSchema.org detection, validation, gap identification, JSON-LD generation
seo-sitemapSitemap structure, URL count, lastmod accuracy, deprecated tags
seo-performanceLCP, INP, CLS measurements with CrUX field data when available
seo-visualDesktop and mobile screenshots, above-fold analysis, layout shift detection
seo-geoAI crawler access, llms.txt, passage citability, brand mention signals

Scoring Weights

The SEO Health Score is a weighted composite across seven categories:
CategoryWeight
Content Quality23%
Technical SEO22%
On-Page SEO20%
Schema / Structured Data10%
Performance (Core Web Vitals)10%
AI Search Readiness10%
Images5%

Output Files

All outputs are written under {domain}-audit/:
  • FULL-AUDIT-REPORT.md — comprehensive per-category findings from every subagent
  • ACTION-PLAN.md — prioritized recommendations (Critical → High → Medium → Low)
  • audit-data.json — structured envelope for PDF report generation
  • findings/ — per-category specialist files (technical.md, content.md, schema.md, performance.md, visual.md, geo.md, etc.)
  • screenshots/ — desktop and mobile captures (requires Playwright)

Action Plan Structure

Every item in ACTION-PLAN.md follows a strict four-field format that removes vague advice from the deliverable:
FieldWhat It Contains
First-principle observationThe raw signal that triggered the finding
Dependency chainWhich other recommendations this one unlocks or depends on
Failure-mode checkAn explicit “how would we know this failed?” criterion
Leading indicatorThe metric to monitor as an early signal of improvement

Priority Definitions

  • Critical — blocks indexing or causes active penalties; fix immediately
  • High — significant ranking impact; fix within 1 week
  • Medium — optimization opportunity; fix within 1 month
  • Low — nice-to-have; add to backlog

Real Sample Output

Below is the first 50 lines of a real /seo schema https://rankenstein.pro/about audit — verbatim from the plugin’s output. Full site audits follow the same structured format across all categories.
# Schema Markup Report: rankenstein.pro/about

**URL:** https://rankenstein.pro/about
**Date:** 2026-02-09
**Format Detected:** JSON-LD (3 blocks) | No Microdata | No RDFa

---

## Summary

| Metric | Value |
|--------|-------|
| **JSON-LD Blocks** | 3 |
| **Schema Types** | Organization, WebSite, SoftwareApplication |
| **Critical Issues** | 2 |
| **Warnings** | 5 |
| **Passed Checks** | 18 |
| **Overall Grade** | B+ (solid foundation, actionable gaps) |

---

## Existing Schema Validation

### 1. Organization (`@id: #organization`)

| Property | Value | Status | Notes |
|----------|-------|--------|-------|
| `@context` | https://schema.org | Valid | |
| `@type` | Organization | Valid | Active type |
| `@id` | https://rankenstein.pro#organization | Good | Enables cross-referencing |
| `name` | Rankenstein | Valid | |
| `description` | Present, 200+ chars | Good | Descriptive and keyword-rich |
| `url` | https://rankenstein.pro | Valid | Absolute URL |
| `logo` | ImageObject with @id, url, width, height, caption | Excellent | Well-structured |
| `foundingDate` | "2024" | Imprecise | Year-only accepted but ISO 8601 preferred |
| `areaServed` | "Worldwide" | Text | Works but GeoShape is more semantic |
| `contactPoint` | email + contactType | Valid | Consider adding telephone |
| `founder` | 1 Person (Daniel Agrici) | Incomplete | Page describes two co-founders; second missing |
| `sameAs` | 5 social profiles | Good | GitHub, X, LinkedIn, YouTube, Reddit |
| `knowsAbout` | 6 topics | Good | Relevant topical signals |

**Critical Issue:** The `founder` property only includes Daniel Agrici.
Benjamin Samar (Co-Founder & Technical Director) is displayed on the page
but absent from the schema. This creates a content-schema mismatch that
can confuse search engines.

/seo page <url>

Deep single-page analysis without a full crawl. Covers on-page SEO (title, meta, headings, URLs), content quality (word count, readability, E-E-A-T), technical elements (canonical, robots, Open Graph), schema markup, images (alt text, sizes, formats), and Core Web Vitals potential issues.
/seo page https://example.com/about

/seo sitemap <url>

Validates an existing XML sitemap against format correctness, URL count (flag if over 50k per file), URL status codes, lastmod accuracy, deprecated tags (priority, changefreq), and coverage versus crawled pages. Use /seo sitemap generate to create a new sitemap with industry-specific templates.
/seo sitemap https://example.com/sitemap.xml
/seo sitemap generate

/seo images <url>

Image optimization analysis across alt text presence and quality, file sizes (flags images over 200 KB), format recommendations (WebP/AVIF), responsive images (srcset, sizes), lazy loading, and CLS prevention via explicit dimensions.
/seo images https://example.com

Google API Enrichment

Claude SEO works fully offline, but adding Google API credentials unlocks real field data at four tiers:
TierCredentials RequiredData Unlocked
0API keyPageSpeed Insights, CrUX, CrUX History (25-week trends)
1+ OAuth or Service AccountSearch Console queries, URL Inspection, Indexing API
2+ GA4 property configOrganic traffic, top landing pages, device / country breakdown
3+ Ads developer tokenKeyword Planner search volume and competition data
Run /seo google setup to launch the credential wizard. All credentials are stored under ~/.config/claude-seo/ with 0o600 permissions — nothing is committed to the repository.

Build docs developers (and LLMs) love