A model-agnostic, evidence-governed SEO operating system for technical SEO, content strategy, GEO/AIO, local SEO, accessibility, CRO, compliance, security, digital PR, competitive intelligence, and continuous SEO research.
Its primary operator is a technical SEO practitioner or SEO engineer accountable for an authorized audit and implementation handoff. SEO strategists and analysts, agency and in-house SEO teams, growth and product engineers, and coding-agent users are supported secondary users.
The product is documentation-first: knowledge, skills, evidence, and orchestration contracts are the primary layer. A bounded CLI runtime and optional integration adapters provide the executable layer. The exact product boundary is defined in governance/product-contract.json and explained in docs/PRODUCT-CAPABILITY-CONTRACT.md.
Requires Python 3.11, 3.12, or 3.13.
python -m pip install -e .
seoctl --registry-check
seoctl system doctor
seoctl audit technical --url https://example.com/ --fixture examples/product-proof/site-fixture.json --output outputs/first-run --max-urls 20seoctl system doctor performs deterministic, read-only local checks for the supported Python version, required assets, command registry, architecture contract, per-pack knowledge provenance, and dependency lock. It performs no network request or provider authentication and does not claim live-site or deployment readiness.
seoctl audit technical is the sole flagship command. It performs bounded read-only diagnosis and produces a decision-ready technical SEO evidence package with exactly ten artifacts in the gitignored outputs/first-run/ directory: crawl.json, findings.json, decisions.json, agent-contributions.json, trust-summary.json, technical-audit.md, executive-summary.md, remediation-plan.csv, verification-plan.json, and run-manifest.json.
This deterministic fixture audit makes no live request. The manifest labels the evidence mode FIXTURE; these results prove deterministic contract behavior only, not the condition of example.com or any other live site. A bounded live run reports observations from an authorized target at a stated time. Neither mode proves complete site coverage, search-engine indexing, ranking, traffic, conversion, production readiness, or comparative superiority, and the flagship makes no external change.
Inspect every registered command family and its family-specific options:
seoctl --help
seoctl audit --helpContinue with the five-minute quick start, then use SYSTEM_MAP.md and workflows/request-routing.md for orchestration. Live crawling and provider-backed execution are separate, optional steps that require authorization and may require credentials.
Only assess websites, data, APIs, and accounts you are authorized to access. Never commit credentials, client exports, personal data, or generated private artifacts. Live integrations are optional and read credentials from local environment variables; see .env.example.
This is not a prompt dump. It is a structured SEO operating system made of:
- 25 specialist SEO agents
- Reusable SEO skills
- Shared evidence standards
- Cross-agent workflows
- Lightweight executable runtime and router
- Tool adapter contracts and offline-safe parsers
- Knowledge-source rules
- Quality gates and anti-patterns
- JSON output schemas
- Semantic validation and tests
- Practical report and implementation templates
- LLM-specific operating guides for Codex, ChatGPT, Claude, Claude Code, Replit, and Manus
The core system is LLM agnostic. Any capable coding or reasoning model can use the files. The top-level model control files provide environment-specific operating guidance without changing the system itself.
Primary operator:
- Technical SEO practitioner or SEO engineer accountable for an authorized audit and implementation handoff
Supported secondary users:
- SEO strategists and analysts
- Agency and in-house SEO teams
- Growth and product engineers
- Coding-agent users
Every SEO recommendation must be evidence-backed, user-first, policy-safe, technically verifiable, and mapped to an owner, risk level, acceptance criteria, and measurement plan.
World-Class-SEO-Agent-System/
|-- README.md
|-- Codex.md
|-- ChatGPT.md
|-- Claude.md
|-- Claudecode.md
|-- Replit.md
|-- Manus.md
|-- SYSTEM_SPEC.md
|-- agents/
|-- adapters/
|-- skills/
|-- workflows/
|-- knowledge/
|-- schemas/
|-- orchestration/
|-- runtime/
|-- tests/
|-- examples/
|-- scripts/
`-- templates/
- Read
SYSTEM_MAP.mdfor the fastest navigation path through the repository. - Read
SYSTEM_SPEC.mdfor the system mission, evidence hierarchy, operating modes, and approval gates. - Use
workflows/request-routing.mdto choose the right agent or workflow. - Open
agents/AGENT_INDEX.mdto find the specialist agents. - Use
skills/SKILL_INDEX.mdto select reusable SEO capabilities. - Apply
knowledge/seo-quality-gates.mdbefore accepting any recommendation. - Return structured outputs using
schemas/agent-output.schema.jsonor the closest file intemplates/. - For multi-agent work, use
orchestration/README.mdandorchestration/session-state.schema.json. - For executable routing or integration work, use
main.py,runtime/, andadapters/.
| Agent | Primary Role |
|---|---|
| SEO Technical Agent | Crawlability, indexation, rendering, schema, canonicals, robots, sitemaps, Core Web Vitals |
| SEO Copywriter/Content Agent | Content briefs, metadata, E-E-A-T, information gain, refreshes, intent matching |
| SEO Information Architecture Agent | Taxonomy, URL structures, internal links, topic clusters, crawl depth |
| SEO Accessibility Agent | WCAG-oriented checks, headings, alt text, labels, keyboard access, screen reader usability |
| SEO CRO Agent | Organic landing page conversion, CTA-intent fit, funnel friction, testing ideas |
| Local SEO Agent | GBP, NAP, citations, reviews, local landing pages, local pack visibility |
| Senior SEO Strategist Agent | Roadmaps, prioritization, business alignment, KPI planning |
| Senior SEO Engineer Agent | Code-level SEO implementation, tests, templates, deployment readiness |
| SEO Scrummaster Agent | Agent coordination, challenge loops, sprint planning, risk gates |
| SEO Full Audit/Analyst Agent | Full audits, health scoring, analytics synthesis, reporting |
| SEO Output Report Agent | Plain-language reports of findings, completed work, recommendations, and next steps for non-technical stakeholders |
| SEO Diagnostic Infrastructure Agent | Budget-aware diagnostic stack setup, audit tooling, dashboards, grading models, and monitoring infrastructure |
| GEO / AIO Optimization Agent | AI Overviews, generative search visibility, entity clarity, passage citability |
| Visual & Video Search Agent | Image SEO, video SEO, transcripts, media schema, visual search readiness |
| Voice Search & Conversational Agent | Spoken queries, Q&A structures, conversational answer formats |
| SEO Compliance & Legal Agent | Spam policies, disclosures, privacy, claims, regulated content escalation |
| Negative SEO & Security Agent | Toxic links, hacked pages, malware, scraping, spam attacks |
| International & Multilingual SEO Agent | Hreflang, localization, regional targeting, multilingual site architecture |
| Digital PR & Programmatic Link Outreach Agent | Linkable assets, unlinked mentions, backlink gaps, outreach strategy |
| Predictive SEO Trend Agent | Trend forecasting, seasonality, emerging search demand |
| Competitive Intelligence Agent | Competitor gaps, new pages, SERP movement, backlink patterns, AI citations |
| SEO Research and Development Agent | Controlled SEO experiments, hypotheses, test design, results interpretation |
| SEO Knowledge Graph Sync Agent | Entities, sameAs, schema consistency, brand SERP, knowledge graph readiness |
| AI Principal SEO Scientist | Search change monitoring, rule updates, knowledge sync, system learning |
| SEO E-commerce Agent | Product/category SEO, Product/Offer/ProductGroup schema, faceted navigation, Google Shopping/Merchant eligibility, marketplace intelligence |
- Evidence-dependent multi-agent audit synthesis through
system.runandfull-site-audit - Technical SEO implementation in codebases
- Content briefs and refresh plans
- GEO/AIO and AI citation readiness
- Local SEO and multi-location scaling
- International and hreflang audits
- SEO security and negative SEO monitoring
- Programmatic SEO governance
- E-commerce, product schema, and marketplace SEO
- Competitive intelligence
- SEO experiment design
- SEO sprint planning and issue prioritization
- Digital PR and authority-building workflows
- SEO knowledge-base maintenance
Use Codex.md when working inside a coding-agent environment.
Codex is best for:
- Inspecting codebases
- Implementing metadata, schema, sitemaps, robots, redirects, and internal-link logic
- Creating SEO regression checks
- Fixing accessibility and performance issues
- Running validation and tests
Recommended flow:
- Read
Codex.md. - Route the task.
- Load the relevant agent and skill files.
- Make the smallest safe code change.
- Verify the rendered result, tests, schema, crawl signals, or performance signal as appropriate.
Use ChatGPT.md for conversation-first analysis, planning, drafting, and review.
ChatGPT is best for:
- SEO strategy synthesis
- Content briefs
- Public-facing copy cleanup with
anti-ai-public-writing - Agent debate simulation
- Competitive analysis summaries
- Local and international SEO planning
- Compliance review checklists
- Experiment design
- Executive reporting
Recommended flow:
- Read
ChatGPT.md. - Route the request.
- Ask for missing first-party evidence when needed.
- Produce a structured recommendation with assumptions and risks clearly labeled.
Claude.md: conversation-first Claude strategy, review, and orchestration.Claudecode.md: Claude Code technical SEO implementation in codebases.Replit.md: SEO-ready app building, previewing, and rapid implementation.Manus.md: autonomous multi-step SEO project coordination and execution.
request-routing.md: choose the right lead and support agents.full-audit-workflow.md: run a complete SEO audit.content-production-workflow.md: produce search-ready, user-first content.technical-deployment-workflow.md: safely ship SEO code changes.continuous-learning-workflow.md: keep the system current.monitoring-workflow.md: monitor drift, anomalies, security issues, and competitor movement.system-improvement-loop.md: improve the agent system itself.
knowledge/seo-quality-gates.md: required acceptance gates.knowledge/knowledge-sources.md: source hierarchy and trusted references.knowledge/anti-patterns.md: tactics the system must reject.knowledge/scoring-model.md: default scoring model for audits.
Any text a website or app visitor can read should pass skills/public-facing-writing-skills.md. Use anti-ai-public-writing for page copy, headings, metadata, buttons, form text, alt text, captions, transcripts, local pages, product/service copy, blog content, error messages and onboarding text.
schemas/agent-output.schema.json: standard agent response.schemas/handoff-payload.schema.json: agent-to-agent handoff contract.schemas/decision-record.schema.json: Scrummaster decision record.schemas/rule-update.schema.json: knowledge-base rule update.
See examples/ for worked sample outputs:
- Full audit example
- Content brief example
- Technical deployment example
- Plain-language SEO report example
- Diagnostic infrastructure example
- Anonymized production-style example with crawl, GSC, and GA4-style inputs
Run repository validation locally with:
./scripts/validate-repository.ps1Run semantic schema validation and tests with:
python -m pip install -r requirements-dev.txt
python scripts/validate_schema_examples.py
pytest -qThe GitHub Actions workflow in .github/workflows/validate.yml validates JSON, internal markdown links, agent skill references, template references, schema conformance for example outputs, runtime routing, adapter behavior, and semantic repository contracts.
The executable layer is intentionally lightweight and model-agnostic. runtime/ provides session state, request routing, async execution, memory, tool dispatch and LLM clients. adapters/ provides normalized contracts for crawl exports, server logs, PageSpeed/Lighthouse payloads, schema validation, rank tracking, backlinks, GSC exports, and GA4 exports. Live API credentials are not stored in the repository; adapters are designed so teams can plug in authenticated fetchers while still testing with safe local exports.
Adapter implementation details live in adapters/README.md. Recommended tools to connect are listed in adapters/TOOLS.md. A safe OAuth2 Google Search Console pattern is provided in adapters/gsc_live_example.py. A live key-only PageSpeed Insights and CrUX adapter with SSRF-safe URL validation is provided in adapters/google_pagespeed_live.py, and a persistent cross-session drift store in adapters/evidence_store.py.
Dry-run routing:
python main.py "Run a full SEO audit" --domain https://example.comsystem.run and the full-site-audit skill are evidence-dependent multi-agent orchestration capabilities, not alternate flagship commands or completeness guarantees. Their outputs must disclose which domains ran and which evidence remained missing.
Dry-run execution with the built-in echo client:
python main.py "Run a full SEO audit" --domain https://example.com --executeOptional live execution:
$env:OPENAI_API_KEY="..."
python main.py "Run a full SEO audit" --domain https://example.com --execute --llm-provider openaiSee .env.example for optional provider settings. Do not commit real API keys.
Tool dispatch before execution:
python main.py "Run a technical crawl audit" --execute --tool crawler_csv=examples/anonymized-production-style-example/inputs/crawl.csvThe templates/ folder includes practical starting points for:
- SEO audits
- Content briefs
- Technical SEO tickets
- SEO roadmaps
- Decision records
- GEO/AIO reports
- SEO experiments
- Knowledge updates
- Outreach campaigns
- Engineering change plans
- Do not recommend manipulative link schemes.
- Do not create doorway pages, fake locations, fake reviews, or scaled low-value pages.
- Do not hide text or create content that differs materially for bots and users.
- Do not auto-apply indexation, canonical, redirect, robots, disavow, or legal/compliance changes without explicit approval.
- Do not claim certainty when evidence is incomplete.
- Do not treat industry speculation as official search guidance.
Every contribution must improve SEO capability, operating clarity, evidence quality, safety, or implementation usefulness. See CONTRIBUTING.md.
MIT. See LICENSE.