How jeetpatel92/seo-aeo-geo-aio-optimization-agent-system works
SAGO is an unattended website optimization system for SEO, answer-engine and generative-search visibility, and performance. Its main workflow is scheduled orchestration: gather a site snapshot, run specialist audits, prioritize findings, draft and review changes, apply them, verify the live result, and roll back failures. A learning loop measures outcomes and tunes future decisions. The map includes the documented specialist roles and integrations; relationships not established by the excerpts or README are omitted. Several agent implementations were not sampled, so their edges reflect the README’s documented pipeline.
Main entry points: conductor.py Conductor · llm.py Claude interface · scout.py Scout · agents Specialist auditors
Components 21
Run orchestration
- Conductor
engine/sago/agents/conductor.py - Scout
engine/sago/agents/scout.py - Shared context
engine/sago/core.py
Audits and planning
- Specialist auditors
engine/sago/agents - Strategist
engine/sago/agents/strategist.py - Detectors and recipes
engine/sago/knowledge.py
Change lifecycle
- Copywriter
engine/sago/agents/copywriter.py - Theme engineer
engine/sago/agents/engineer.py - Gatekeeper
engine/sago/agents/gatekeeper.py - Operator
engine/sago/agents/operator.py - Verifier
engine/sago/agents/verifier.py - Action policy
engine/sago/policy.py
Site and data adapters
- Claude interface
engine/sago/llm.py - WordPress connector
connector/sago-connector/sago-connector.php - Crawl and data adapters
engine/sago/io - Notifications
engine/sago/notify.py
Other components
- Daily schedule
- WordPress site
- Search and performance data
Connections 30
- Daily schedule → Conductor: starts run
README.md - Conductor → Scout: runs first
README.md - Scout → Specialist auditors: provides snapshot
README.md - Specialist auditors → Strategist: send findings
README.md - Strategist → Conductor: plans actions
README.md - Conductor → Copywriter: drafts copy
README.md - Conductor → Theme engineer: builds theme
engine/sago/agents/conductor.py - Conductor → Gatekeeper: submits action
README.md - Gatekeeper → Action policy: checks policy
engine/sago/agents/gatekeeper.py - Conductor → Operator: dispatches approved
README.md - Operator → WordPress connector: applies changes
README.md - WordPress connector → WordPress site: updates site
README.md - Conductor → Verifier: checks live change
README.md - Verifier → WordPress site: checks as guest
README.md - Verifier → Operator: failure rolls back
README.md - Conductor → Coach: runs learning
README.md - Coach → Run state: reads outcomes
engine/sago/agents/coach.py - Strategist → Run state: uses change history
engine/sago/agents/strategist.py - Conductor → Run state: tracks run state
engine/sago/agents/conductor.py - Scout → Crawl and data adapters: collects snapshots
engine/sago/agents/scout.py - Crawl and data adapters → Search and performance data: fetches metrics
README.md - Crawl and data adapters → WordPress site: crawls pages
README.md - Specialist auditors → Detectors and recipes: uses detectors
engine/sago/agents/ai_visibility.py - Theme engineer → Detectors and recipes: uses recipes
engine/sago/agents/engineer.py - Copywriter → Claude interface: generates copy
engine/sago/agents/copywriter.py - Theme engineer → Claude interface: requests edits
engine/sago/agents/engineer.py - Gatekeeper → Claude interface: requests review
engine/sago/agents/gatekeeper.py - Coach → Claude interface: tunes outcomes
engine/sago/agents/coach.py - Conductor → Shared context: uses shared context
engine/sago/agents/conductor.py - Conductor → Notifications: sends alerts
README.md