Claude SEO Skill Reference

Key takeaways#

Resource type: claude-seo is a Claude Code SEO skills and subagent collection.

Scope: The repository description lists 25 sub-skills and 18 sub-agents.

Coverage: It covers technical SEO, schema, E-E-A-T, GEO/AEO, backlinks, local SEO, ecommerce SEO, international SEO, Google APIs, and reporting.

Cost note: Optional integrations may create external costs, so teams should set API limits before use.

What this resource is#

Claude SEO is a public skill collection for Claude Code focused on search work across technical SEO, E-E-A-T, structured data, GEO/AEO, backlinks, local SEO, semantic clustering, ecommerce SEO, international SEO, maps intelligence, Google APIs, and reporting. The repository description says it includes 25 sub-skills and 18 sub-agents, with optional DataForSEO, Firecrawl, and Banana extensions. It should be modeled as an OpenTools resource because the durable entity is a collection of reusable agent instructions, skills, recipes, or writing guidance rather than a hosted SaaS product, standalone MCP server, or model family.

The source for this page is the public repository at https://github.com/AgriciDaniel/claude-seo. Public repositories are especially useful for builders because they show the actual files, update history, install notes, license context, and project scope. Before adopting any agent skill collection, a team should inspect the instructions directly and decide which parts are safe to expose to its AI coding assistant.

Setup path#

Install and usage should follow the repository README. Treat optional DataForSEO, Firecrawl, and Banana extensions as separate integrations that need their own credentials, privacy review, and cost limits.

A careful setup starts with a disposable project or a non-production workspace. Add only the skills needed for the current job, read the skill text, and run a small task before connecting credentials, analytics data, customer content, or production repositories. Skill packs can improve agent behavior, but they also add instructions that may influence how an agent reads, edits, reports, and prioritizes work.

What is included#

The collection covers many SEO workflows: audits, content analysis, structured-data review, local search work, semantic clustering, reporting, and search-oriented agent tasks. Builders can use it as an inspectable prompt and skill library for repeatable SEO work in Claude Code.

The practical value is repeatability. Instead of rewriting a long prompt every time, a builder can keep structured guidance in files that an agent can load and reuse. That is useful for teams that want shared standards for SEO review, Cloudflare development, content editing, reporting, or similar agent-assisted workflows.

When to use it#

Use this resource when the repository matches an active workflow and the team wants more specific agent behavior than a generic chat prompt can provide. It is a strong fit for people already using Claude Code or compatible skill systems and for operators who want source-visible instructions they can audit before use.

Do not treat the repository as a magic quality gate. SEO outputs can be persuasive even when wrong, so verify claims against Google Search Console, crawls, page source, logs, and primary documentation before making site changes. For sensitive work, keep human review in place, limit third-party API keys, and verify any generated report or code change against primary sources.

Verification notes#

This OpenTools resource was created from the official public GitHub repository and repository metadata collected on 2026-08-10. Repository stars, README content, install commands, and linked integrations can change quickly, so users should confirm the latest README before relying on the guidance in production agent workflows.