seo-aeo-orchestrator
seo-aeo-orchestrator is an code AI skill with a core value of Runs an audit-first SEO/AEO growth workflow from project discovery through implementation, foundational content, measurement setup, deployment verification, and optional weekly monitoring. It
helps developers solve real-world problems in the code domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
Runs an audit-first SEO/AEO growth workflow from project discovery through implementation, foundational content, measurement setup, deployment verification, and optional weekly monitoring.
Quick Facts
mkdir -p ./skills/seo-aeo-orchestrator && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/seo-aeo-orchestrator/SKILL.md -o ./skills/seo-aeo-orchestrator/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# SEO-AEO Growth Orchestrator Workflow
**File:** `.agent/workflows/seo-aeo-orchestrator/WORKFLOW.md`
**Workflow ID:** `seo-aeo-orchestrator`
**Version:** 2.0.0
**Execution Mode:** sequential gates with parallel content work where safe
Purpose
Turn a website or codebase into an evidence-backed SEO/AEO growth system. The workflow starts with an audit, implements approved fixes, confirms the business and keyword strategy, researches current search intent, creates foundational content, prepares external distribution, configures measurement, deploys, verifies, and offers weekly monitoring.
The workflow is designed for coding agents working directly in a repository. It must understand the project’s framework, routes, content storage, metadata implementation, sitemap/robots generation, deployment path, and authentication boundaries before editing or publishing.
Workflow entry point
{
"workflow_input": {
"project_path": "string — current project or repository",
"site_url": "string — optional live URL",
"business_type": "string — optional description of the business",
"target_audience": "string — optional audience",
"conversion_goal": "string — signup, demo, purchase, download, contact, or other",
"user_keywords": ["string — optional owner-approved targets"],
"location": "string — optional market or country",
"foundation_page_count": "integer — 5–10, default 10",
"research_mode": "browser | api | both | unavailable — default both",
"existing_content": ["string — optional URLs, routes, or titles"],
"tone": "professional | conversational | bold | empathetic | authoritative",
"monitoring_preference": "ask | one-time | recurring | none — default ask"
}
}Authorization gates
The agent may inspect the codebase, run local checks, and draft recommendations without additional confirmation. Before each external or material mutation, obtain the required authorization:
- implementing code/content changes: follow the user’s request and preserve unrelated work;
- deploying or pushing to Git: confirm when the user has not already requested it;
- accessing Google Search Console or Bing Webmaster: ask the user to authenticate in the browser or provide an approved connector;
- submitting URLs or sitemaps: confirm the exact property and URLs before submission;
- creating recurring monitoring: ask whether the user wants it, even if `monitoring_preference` is `ask`.
Never claim an account is connected, a sitemap is submitted, a URL is indexed, or a deployment is live without observable evidence.
Execution architecture
PHASE 0 — DISCOVERY
inspect codebase, framework, routes, live URL, deployment, and content model
│
▼
PHASE 1 — AUDIT
SEO/AEO/technical/conversion audit with evidence and prioritized fixes
│
▼
PHASE 2 — IMPLEMENTATION
apply approved audit fixes, then re-audit and verify build/routes
│
▼
PHASE 3 — STRATEGY CONFIRMATION
ask for business context, target keywords, audience, location, and conversion goal
│
▼
PHASE 4 — SEARCH-INTENT RESEARCH
browser + API research when available; semantic fallback when unavailable
│
▼
PHASE 5 — CONTENT FOUNDATION
landing/product improvements + 5–10 foundational pages, default 10 when justified
│
├───────────────┐
▼ ▼
internal content external distribution plan
│ │
└───────┬───────┘
▼
PHASE 6 — MEASUREMENT AND PUBLISHING
Search Console/Bing setup (gated), sitemap/URL submission, deploy, verify
│
▼
PHASE 7 — MONITORING
weekly analysis, refresh recommendations, optional recurring automationPhase 0 — Discover the project
1. Inspect the repository without overwriting user work.
2. Identify framework, package manager, routes, page components, content files/CMS, metadata helpers, sitemap and robots generation,
🎯 Best For
- SEO content writers
- Digital marketers
- Claude users
- Software engineers
- Development teams
💡 Use Cases
- Optimizing blog posts for search intent
- Writing meta descriptions that drive CTR
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply seo-aeo-orchestrator to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Does this account for Google algorithm updates?
The skill follows evergreen SEO best practices. Stay updated on Google core updates for additional context.
Is seo-aeo-orchestrator compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for seo-aeo-orchestrator?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install seo-aeo-orchestrator?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/seo-aeo-orchestrator/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Keyword stuffing
Modern SEO favors natural language and topical authority over keyword density.
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.