SEO Aeo Geo Ultimate

One request. The right workflow.

SEO work rarely arrives neatly labelled. “Why are we absent from AI answers?” may need source research, a prompt corpus, or repeated surface observations. “Improve this site” may need content, architecture, technical, commerce, local, video, or authority work. SEO-AEO-GEO Ultimate starts from one router, finds the smallest useful lane, and keeps evidence, ownership, approval, and follow-up connected.

The result is a practical operating system for search and AI visibility: broad enough for a serious site, structured enough for a team to review, and modular enough to use one skill at a time.

Install on Codex · Install on Claude Code · Start with the router · Submit to the Claude directory

Start with the router

You do not need to memorize the internal map. Start with the seo router and name the outcome you want.

Audit our Turkish pricing page and tell us what to fix first.
Make our documentation ready for AI search.
Create and validate a maintained llms.txt from our public documentation.
Find out why our brand is absent from a specific AI-search surface.
Turn these validated findings into an approval-ready implementation plan.

The router is not a generic audit that tries to do everything itself. It reads the request, picks the right specialist, and keeps the handoff clear. Direct specialist calls remain available when you already know the exact lane.

Install on Codex

Requires Python 3.11 or later.

git clone https://github.com/oegeyilmaz9/seo-aeo-geo-ultimate.git
Set-Location seo-aeo-geo-ultimate

# Check the suite before installing it.
python scripts/sync_contracts.py --check
python scripts/validate_suite.py
python scripts/validate_claude_plugin.py
python scripts/run_tests.py

Install the shared skills into Codex after the checks pass:

# Preview the runtime changes first.
python scripts/install_runtime.py --dry-run

# Install all 27 skills. Existing target folders are backed up.
python scripts/install_runtime.py

# Confirm the support package, runtime locators, and installed skill hashes.
python scripts/install_runtime.py --verify

The installer copies the skill trees and an immutable support package containing validators, schemas, manifests, and required documentation. By default skills go to ~/.codex/skills; versioned support packages, backups, and install state go to ~/.codex/seo-skill-suite-state. A .seo-suite-runtime.json locator beside each installed SKILL.md resolves the active package through current.json, so the repository clone does not need to be retained after installation.

Start a new Codex task after installation so skill discovery and the runtime locator refresh, then invoke $seo Audit ... or any named specialist.

Install on Claude Code

This repository is both a Claude Code plugin and a small developer marketplace. The plugin contains the same 27 skill trees used by Codex; there is no forked or reduced Claude edition.

Install from this repository

Run these commands inside Claude Code:

/plugin marketplace add oegeyilmaz9/seo-aeo-geo-ultimate
/plugin install seo-aeo-geo-ultimate@oegeyilmaz9-skills
/reload-plugins

Then use the router:

/seo-aeo-geo-ultimate:seo Audit our Turkish pricing page and tell us what to fix first.

Plugin skills are namespaced by Claude Code, so /seo-aeo-geo-ultimate:seo is the stable Claude entry point. You can use any specialist in the same namespace, such as /seo-aeo-geo-ultimate:seo-technical.

Formal validators ship inside the plugin. Claude Code substitutes ${CLAUDE_PLUGIN_ROOT} in skill content with the installed plugin path, so users do not need a separate repository clone just to run those checks.

The Markdown skills can still guide an audit without Python. Formal schema, hash, and bundle validation requires Python 3.11 or later; when Python is unavailable, treat the artifact handoff as provisional until the validator runs successfully.

Install from the official Claude plugin directory

After Anthropic approves this repository's directory submission, the plugin becomes available through Claude Code's automatically configured claude-plugins-official marketplace:

/plugin install seo-aeo-geo-ultimate@claude-plugins-official

If an existing Claude Code installation cannot find the listing, refresh it with /plugin marketplace update claude-plugins-official. Only installations missing the official marketplace need /plugin marketplace add anthropics/claude-plugins-official first. The direct repository marketplace flow above remains available independently of directory approval.

For a local development session, Claude Code can load the clone directly with claude --plugin-dir ..

One source, two runtimes

The package deliberately shares one skills/ tree across both runtimes.

Claude Code auto-discovers the skill folders at the plugin root. The package declares no MCP servers, hooks, background monitors, credentials, telemetry, or automatic network actions.

From question to approved change

flowchart LR
  Q["SEO or AI-search question"] --> R["seo routes the work"]
  R --> RS["Research or focused audit"]
  RS --> M["Optional baseline measurement"]
  RS --> P["Owned action plan"]
  M --> P
  P --> A["Explicit approval"]
  A --> I["Scoped implementation"]
  I --> C["Comparable follow-up"]

Not every request needs every phase. The suite prevents a research task from silently becoming a production change and prevents a metric from being dressed up as a causal promise.

What is inside

SEO-AEO-GEO Ultimate contains 27 focused agent skills. They share contracts where a handoff benefits from structure and stay separate where the work is meaningfully different.

Handoffs that keep work moving

Read the SEO Findings, Query Corpus, SEO Performance, Site Graph, Platform Controls, and llms.txt publisher-guide protocols. AEO and GEO retain their own audit contract because answer readiness and entity/citation readiness are different jobs.

Practical artifact and data tools

The skills can work in Markdown alone, while the repository tools make formal handoffs easier to start, validate, migrate, and review. They use Python 3.11+, require no paid API, and keep draft or imported data clearly separate from validated artifacts.

# See every artifact contract, then create an explicitly unvalidated draft bundle.
python scripts/init_artifact.py list
python scripts/init_artifact.py bundle conventional --out work/example --seed example-project --created-at 2026-08-10T00:00:00Z

# Review supported safe migrations. The source artifact is never modified.
python scripts/migrate_artifact.py paths

# Render a readable report only after the artifact's semantic validator passes.
python scripts/render_artifact_report.py examples/conventional-seo-handoff/seo-findings.json --bundle examples/conventional-seo-handoff --out work/seo-findings-report.md

# Normalize an authorized Search Console export without inventing metrics.
python scripts/import_seo_exports.py gsc-csv exports/gsc.csv --output work/gsc-source.json --property sc-domain:example.com --window-start 2026-07-01T00:00:00Z --window-end 2026-08-01T00:00:00Z

Import adapters also cover Bing Webmaster Tools CSV, organic GA4 CSV, crawler CSV, and Apache/Nginx access logs. Read Data Import Adapters for accepted fields, provenance, privacy boundaries, and exact commands. The validated example bundles show conventional SEO and AI-search handoffs end to end.

Built for useful, defensible work

The suite helps teams make stronger decisions and learn from what happens after a change. Recommendations carry an evidence class. Important changes can include approval, verification, monitoring, and rollback. Search performance and AI visibility are measured separately, so each result keeps the context needed for a meaningful comparison.

The workflows support ambitious search and AI-discovery programs while keeping claims grounded in observable evidence. The suite can create /llms.txt as a low-cost future-readiness layer when canonical public sources and a maintenance owner exist; it validates the file without presenting it as a ranking requirement. Primary-source discipline and safety checks are built in; see the source registry, platform and market review, and release checklist. As with any search program, platforms decide ranking, indexing, retrieval, and presentation outcomes.

Claude directory submission

The public repository includes the Claude plugin manifest, a developer marketplace catalog, an offline compatibility validator, and ready-to-paste listing/security copy. The maintainer can submit the repository URL through the Claude.ai or Claude Console form.

Read Claude Plugin Submission for the exact account path and copy. Anthropic’s review is independent; listing is not guaranteed.

Community

Use GitHub Discussions for setup questions, workflow ideas, and routing feedback. Use issue forms for reproducible bugs or scoped improvements. Read SUPPORT.md, CONTRIBUTING.md, and SECURITY.md before contributing or reporting a vulnerability.

Verify a checkout

Every push and pull request runs the checks below. A weekly scheduled run repeats the full suite so dated source and platform-control freshness failures surface even when the repository receives no commits. A failed scheduled run opens or updates one deduplicated review issue; the next passing scheduled run closes it.

1. Generated-contract byte and hash check
2. Suite structure and source-freshness validation
3. Claude plugin and marketplace structural validation
4. Isolated regression tests on Python 3.11

The evaluation suite covers contracts, source validation, query provenance, measurement arithmetic, repeat-aware AI observations, site graphs, platform-control freshness, operational recovery and experiment recipes, specialist behavior boundaries, artifact boundaries, action-plan evidence disconnection, installer safety, and Claude package metadata. Read CONTRIBUTING.md before changing the suite.

License

Released under the Apache License 2.0. See NOTICE for attribution and repository identity.

If you reference this project in a report, article, or implementation, GitHub can generate a citation from CITATION.cff.