How to Run a Full SEO Audit with Claude Code

To audit a website with Claude Code, install the open-source Claude SEO plugin, run /seo setup, then /seo audit followed by your URL. It checks technical SEO, content quality, schema, AI-search readiness and Core Web Vitals in parallel and returns a prioritized plan. Verify each finding before you change anything.

  • By Praveen Jha · Updated 2026-10-22 · 10 min read · SEO, AEO & search
Best for
Developers, SEO consultants and technical site owners
Time
15 minutes setup, a few minutes per audit
Cost
Plugin is free (MIT); Claude Code needs a paid Claude plan
Needs
Claude Code 1.0.33+; the setup step installs Python tools and Chromium
Level
Intermediate

What the Claude SEO plugin is

Claude SEO is an open-source plugin for Claude Code, maintained by Daniel Agrici under the MIT licence. It is a community project, not an Anthropic product. Its README describes 26 sub-skills and 19 specialist agents covering technical SEO, E-E-A-T content quality, Schema.org markup, AI search (GEO), local, e-commerce and international SEO. An audit runs these checks in parallel and turns them into a prioritized action plan.

Before you install

  • Plugins run with your user permissions. Read the repository's install script and hooks before installing, and keep Claude Code's approval prompts on.
  • Pin a release. Note the version you install so audits stay comparable over time.
  • Audits fetch your live URLs. Run your first audit against a site you own, and do not paste production credentials into the session.

Step 1: Install the plugin

Open Claude Code in any folder and run:

Claude Code

/plugin marketplace add AgriciDaniel/claude-seo
/plugin install claude-seo@agricidaniel-claude-seo
/seo setup

The setup step creates an isolated Python environment inside the plugin's data folder and installs Playwright Chromium for page rendering. Run /seo doctor any time to check that everything is ready.

Prefer a manual install? Clone the repository, read install.sh, then run it: git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git && bash claude-seo/install.sh

Step 2: Run the audit

Claude Code

/seo audit https://yourwebsite.com

The full audit returns a score and a prioritized list. For narrower checks, these commands are the ones I use most:

  • /seo page <url>: deep analysis of one page's on-page elements, content and schema.
  • /seo technical <url>: crawlability, indexability, redirects, canonicals and speed.
  • /seo schema <url>: detect, validate and generate JSON-LD structured data.
  • /seo geo <url>: how quotable and citable your passages are for AI Overviews and answer engines.
  • /seo content <url>: E-E-A-T and content quality review.
  • /seo google: optional Google APIs such as Search Console, PageSpeed and CrUX, using your own credentials.

Step 3: Triage before you fix

An audit report is a list of hypotheses, not a to-do list. Sort findings in this order, because each level blocks the next:

  1. Can Google reach and index the page? Broken pages, blocked resources, wrong canonicals, missing or stale sitemaps.
  2. Can a visitor use the page? Broken forms, slow mobile loading, layout shifts.
  3. Does the page answer the query? Thin content, missing direct answers, no author or date.
  4. Is the page marked up and linked well? Schema, internal links, titles and descriptions.

Verify every finding: For each important item, ask Claude for the URL it checked and the evidence it saw: the HTML, the response status or the Search Console record. Fix only what you can reproduce.

A real example: what an audit surfaced on praveenjha.com

When I audited my own site with Claude in October 2026, the findings that mattered were not exotic. The contact page rendered blank because a build setting was missing, so every Enroll button led nowhere. Every page carried duplicate meta description and canonical tags. The sitemap had no last-modified dates, and a full-screen splash animation pushed mobile Largest Contentful Paint to 6.6 seconds. Each fix was small; the value was in finding and ranking them in an afternoon.

Step 4: Fix, then re-run

Because Claude Code works in your codebase, you can ask it to make a fix right after it explains the problem: "Fix the duplicate canonical tags you found, show me the diff, and don't touch anything else." After deploying, run the same audit command again and compare scores and findings, so you know each change worked.

Copy-paste prompts

Turn the audit into a plan

From the audit you just ran, give me the 10 fixes with the biggest impact, ordered by: indexing, usability, content, markup. For each, show the evidence (URL and what you observed), the effort (S/M/L) and the file or setting to change.

Prove a finding

For finding #[n], fetch the URL again, show me the exact HTML or response header that proves it, and tell me how I would know the fix worked.

Fix safely

Fix finding #[n] in this codebase. Change only the files needed, explain each change in one line, and show me the diff before saving.

AI-search readiness

Run /seo geo on [url]. Then rewrite the opening paragraph of the page as a 50-word direct answer to its main question, keeping my tone and facts.

Troubleshooting

  • /seo commands are not recognised Check that Claude Code is version 1.0.33 or newer, re-run the two plugin commands, then restart Claude Code.
  • Setup fails while installing Chromium Run /seo doctor to see what is missing, check your network or proxy, and run /seo setup again.
  • The report recommends FAQ or HowTo rich results Google retired HowTo rich results in 2023 and no longer shows FAQ rich results for most sites. Keep FAQ content for readers and AI answers, not for rich snippets.
  • Findings contradict Search Console Trust Search Console for what Google actually indexed. Use the audit to explain why, and check with URL Inspection.

FAQ

Is the Claude SEO plugin made by Anthropic?

No. It is an open-source community plugin by Daniel Agrici, released under the MIT licence. Review its code and pin a version before you use it on client sites.

Can Claude Code replace paid SEO tools?

For technical, on-page, schema and content audits, largely yes. For large backlink databases and long-term rank tracking you still need a data provider such as Ahrefs, Semrush or DataForSEO.

How long does an audit take?

A single page takes a minute or two. A full-site audit runs agents in parallel and usually finishes in minutes, depending on site size and your connection.

Does it check Core Web Vitals?

Yes. It reports LCP, INP and CLS, using field data from the Chrome UX Report when available and Lighthouse lab data otherwise.

Do I need coding skills?

You need to be comfortable running commands in Claude Code. Fixing findings is easier if Claude Code is opened inside your site's codebase.

Related pages