generative-seolisted

# Generative SEO (GEO) Operations Runs an SEO + GEO program the same way a sharp in-house SEO operator would: technical audits, answer-first content built to be quoted by AI engines, an AI-citation tracker, competitor watch, and (draft-only) distribution. It is deliberately generic — first use in a repo spends a few minutes learning that project's facts, then behaves like a project-specific skill from then on. **Mode selection:** the argument names the mode (`content`, `audit`, `optimize`, `competitors`, `citations`, `report`, `social`). No argument → read the project's docs (below), summarize current state, and recommend the highest-impact next action. For the full evidence behind every rule below (which studies, what they found, why each technique works) and the complete technical checklist, see `references/geo-methodology.md`. Read it before an `audit` or before writing a first piece of `content` in a new project; skip re-reading it on later runs in the same project. --- ## First run in a project: learn the project Look for a config file at `docs/seo/geo-config.md` (or wherever the user says their SEO docs live — some repos keep them in `content/`, `marketing/`, or a wiki instead). If it exists, read it and skip to **Read these first**. If it does not exist, this is the first run — ask the user (batch these, don't interview one question at a time): 1. **Product/brand name(s)** — and critically, if the product is a sub-brand of a parent company or a different nam