SEO GEO Radar Workflow
Weekly SEO, GEO, and AEO radar promotes only evidence that changes search visibility strategy or implementation guidance.
The seo-geo-radar automation tracks AI search optimization and traditional SEO frontier. Source: automations/seo-geo-radar.md, 2026-05-31
Routing
Use this workflow for search, answer-engine, and crawler behavior. Use Content Pipeline Workflow for social posts and Frontend Frontier Radar Workflow for frontend implementation trends.
Trigger
- Weekly automation from
automations/seo-geo-radar.md. - Manual request after official crawler/platform changes, competitive search teardown, or a public-site launch.
- Before shipping changes to public docs,
llms.txt, sitemap, JSON-LD, or content architecture.
Inputs
- Writing and Content Skills and relevant SEO/GEO skill docs.
- Official crawler docs for Googlebot, Bingbot, GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, and related AI agents.
- Google Search Central, Ahrefs, Semrush, Search Engine Land, GitHub tools, reproducible studies, and competitive teardowns.
- Sources published or materially updated in the last 30 days unless Kevin asked for a historical review.
Promotion criteria
Promote only sources that add at least one of:
- a scoring or measurement framework
- deployable implementation: schema, config, crawler handling, test harness, or code
- official platform behavior
- reproducible data study
- firsthand competitive teardown with concrete methodology
Reject anecdotal "AI SEO hack" material unless it contains a reproducible method. The internet will survive the rejection, somehow.
Runbook
- Read Writing and Content Skills and the current playbook before scanning.
- Collect candidate sources and record exact publish/update dates.
- Classify each candidate as promoted, rejected as hype, watchlist, or no-op.
- For promoted items, name the implementation or strategy change.
- Update Writing and Content Skills only when guidance changes.
- Propose Dedalus or portfolio-site tasks only when the change is concrete and testable.
Output
Write outputs/<YYYY-MM-DD>/seo-geo-radar/<agent>.md with promoted sources, rejected hype, playbook updates needed, and one optional implementation recommendation. A no-op run should still list sources checked and rejected.
Validation
Every promoted item needs a dated source link and a reason tied to crawler behavior, ranking visibility, entity strategy, schema, or measurement. If no official or reproducible evidence exists, the run should not update the wiki page.
Run Contract
This workflow follows Workflow Run Contract: name the sources, write output or no-op proof, promote only durable facts, update state only when the run really completed, refresh generated surfaces when durable pages or skills change, and log user-visible work.
Timeline
- 2026-07-01 | Expanded into a weekly search-visibility radar contract with routing, trigger, inputs, strict promotion criteria, runbook, output, and validation. Source: User request, 2026-07-01
- 2026-05-31 | Workflow page created from seo-geo-radar automation. Source: automations/seo-geo-radar.md, 2026-05-31