What does the SEO-AEO Growth Orchestrator Workflow do?

It turns a website or codebase into an evidence-backed SEO/AEO growth system by running through a complete process: auditing, implementing fixes, confirming strategy, researching search intent, creating content, preparing distribution, configuring measurement, deploying, verifying, and providing weekly monitoring.

What technical requirements does this workflow need from my coding agent?

The coding agent must be able to access and modify your repository directly, and must understand your project's framework, routing system, content storage, metadata implementation, sitemap/robots generation, deployment path, and authentication boundaries.

When should I NOT use this workflow?

Do not use it if your coding agent cannot access or modify the repository directly, or if your project structure doesn't support programmatic understanding of framework conventions and content storage patterns.

What do I need to provide to use this workflow?

You need to provide access to your website or codebase repository along with your business context and keyword strategy approval.

Skill

Orchestrate end-to-end SEO/AEO growth from audit to deploy

Name: Orchestrate end-to-end SEO/AEO growth from audit to deploy
Availability: OnlineOnly
Author: Antigravity

An audit-first workflow for improving SEO and AEO through technical fixes, search-intent research, content planning, publishing checks, and optional monitoring.

Get skill

Works with github

Antigravity

Own this? Claim it

Spark score

out of 100

Updated last month

Source checked Oct 10, 2026

Version 19.2.0

Add to Favorites

Why it matters

Transform a website or codebase into a complete, evidence-backed SEO and Answer Engine Optimization (AEO) growth system by auditing technical foundations, implementing fixes, aligning keyword strategy, creating optimized content, and deploying with continuous measurement.

Outcomes

What it gets done

Audit site architecture, routes, metadata, and sitemap generation to identify SEO gaps

Research current search intent and align keyword strategy with business goals

Generate and deploy foundational SEO-optimized content directly into the repository

Configure measurement tools, verify deployment, and enable weekly performance monitoring

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-seo-aeo-orchestrator | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

A sequential workflow for auditing a website, prioritizing and verifying fixes, researching search intent, planning foundational content, and preparing measurement and publishing with explicit authorization gates. Use it to coordinate an audit-first SEO/AEO engagement across a codebase or website when technical fixes, content work, measurement, and publishing need to be managed together.

What it does

An audit-first SEO and AEO workflow that runs in sequential gates: audit, approved fixes, keyword and intent research, foundational content, measurement setup, deployment verification, and optional weekly monitoring.

When to use it

Use it to coordinate technical fixes, content, and measurement for a website or repository. External changes require explicit authorization.

Source README

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.

FAQ

Common questions

Discussion