Skip to content

Product · Runs in Claude Code

The whole SEO department, as a repository.

Answer

The Agentic SEO System is a Claude Code monorepo containing 19 specialist SEO agents and 79 composable skills. It connects to Google Search Console, GA4, DataForSEO, Firecrawl and PageSpeed, runs audits and content production end to end, and keeps a per-site changelog so agents never re-work a page they touched in the last 14 days.

What ships in the box
19 Specialist agents
79 Composable skills
12 Live API integrations

§ 01
Install

Three commands, then you are running.

$ git clone <your-access-url> && ./setup.sh
wiring GSC · GA4 · DataForSEO · Firecrawl · PageSpeed
$ /add-site --domain yoursite.com
$ /how-do-i my traffic dropped last month and I do not know why
→ gsc-compare → gsc-audit-indexing → site-audit --focus technical

The third command is the one that matters. You describe the situation in a sentence and the system hands back the recipe — checked against the data you have actually connected.

§ 02
Connections

What it plugs into.

Your own keys, your own accounts. Nothing is resold and nothing is proxied — the system reads the same APIs you already have access to.

Integrations — the data it actually reads

Search

Google Search Console

Queries, impressions, positions and index coverage, per property.

Analytics

Google Analytics 4

Sessions, conversions and referral traffic through the Data and Admin APIs.

Performance

PageSpeed Insights

Core Web Vitals, field data and lab runs, per URL.

SERP data

DataForSEO

Keyword volumes, competitor rankings and SERP features.

SERP data

Serper

Live SERP lookups when a check has to be current rather than cached.

Crawl

Firecrawl

Full-site crawls and page extraction, including rendered content.

Publish

WordPress

Drafts, posts, media and taxonomies through the REST API.

Publish

GitHub

Commits content straight to the repository for static sites.

Publish

Astro

Writes into content collections, schema-valid on the first build.

Storage

Google Drive

Delivers reports into a client's Drive folder, mirroring the local tree. Scoped to drive.file, so it only ever sees what it created.

Reporting

SMTP

Emails the finished report from your own mail server, not a third party's.

Runtime

Claude Code & Codex

Both runtimes, from one canonical skills tree. The same skills and agents run in either.

§ 03
Mechanism

One loop, running continuously.

Fig. 1 — The operating loop. Five stages, one instance, no handoffs.

Schematic — Agentic SEO System

  1. 01

    MEASURE

    gsc-report · ga4-report

  2. 02

    DIAGNOSE

    gsc-opportunities · site-audit

  3. 03

    PLAN

    topical-map · topic-plan

  4. 04

    PRODUCE

    content-pipeline · generate-visual

  5. 05

    PUBLISH

    wp-integration · internal-linking

Feedback — 14-day cooldown per page

FEEDBACK — 14-DAY COOLDOWN PER PAGE 01 MEASURE gsc-reportga4-report 02 DIAGNOSE gsc-opportunitiessite-audit 03 PLAN topical-maptopic-plan 04 PRODUCE content-pipelinegenerate-visual 05 PUBLISH wp-integrationinternal-linking SCHEMATIC — AGENTIC SEO SYSTEM

§ 04
Contents

Four systems, one orchestrator.

Group A

17 skills · GSC + GA4

Analytics

  • gsc-report
  • gsc-compare
  • gsc-cannibalization
  • gsc-opportunities
  • ga4-report
  • ga4-traffic-sources
  • ai-traffic
  • combined-insights
  • keyword-analysis
  • topic-plan
  • topical-map

Group B

8 specialist agents

Site audit

  • technical-auditor
  • on-page-auditor
  • content-quality-auditor
  • performance-auditor
  • backlink-analyst
  • competitive-intel
  • local-seo-auditor
  • site-audit

Group C

Brief → draft → publish

Content pipeline

  • content-strategist
  • researcher
  • content-writer
  • content-pipeline
  • internal-linking
  • generate-visual
  • wp-integration

Group D

The surface most stacks miss

AI visibility

  • ai-search
  • ai-seo
  • ai-visibility
  • ai-competitors
  • geo-audit
  • prompt-fanout
  • prompt-mining

§ 05
Comparison

What it replaces.

Fig. — Agentic SEO System vs. the usual stack
Agentic SEO System vs. the usual stack
Capability Agentic SEO SystemAhrefs / SemrushFreelance SEOChatGPT + prompts
Reads your GSC + GA4 Yes Yes Yes No
Writes and publishes Yes No Yes Drafts only
Tracks AI citations Yes Partial No No
Runs unattended Yes Reports only No No
Remembers what it changed Yes No Sometimes No
Yours if you cancel Yes No No

Scroll sideways to compare — the first column stays put.

§ 06
Questions

§ FAQ

Before you install it

What exactly do I get?

A monorepo you clone. It contains the agents, skills and a Python execution layer wired to real APIs — Search Console, GA4 Data and Admin, DataForSEO, Firecrawl, Serper, PageSpeed Insights, WordPress REST, Google Drive and SMTP. The annual tier also includes a self-hostable web app frontend over the same engine.

Which CLI does it run in?

Both Claude Code and OpenAI Codex. The Claude skills tree is canonical and a generator emits Codex-flavoured copies, so the same skills and agents work in either runtime without maintaining two codebases.

Can I run it for multiple clients?

Yes. The platform is multi-site by design. Each client lives under its own directory with separate config, secrets, GSC and GA4 property IDs, brand voice and changelog. Agents read the changelog before recommending work, which is what stops them proposing the same fix every month.

What happens when a skill needs data I have not connected?

It refuses and tells you which connection is missing, rather than producing a confident report built on nothing. The /how-do-i skill runs the same check before handing you a recipe, so a chain that needs search history you do not have yet gets rejected before it wastes your afternoon.