SEO Content Systems
SCS is a local-first, terminal-first system for SEO content operations. It works for any owned site, client site, or project: register the site, create a workspace, and run the same workflow.
Keyword data can come from any SEO tool — SpyFu, WriterZen, NeuronWriter, Google Keyword Planner, or a manual export. SCS does not depend on a paid API.
info
WordPress is the visual review surface. Draft, pending, scheduled, and published state are controlled from the terminal. See Publishing Workflow.
Documentation map
| Section | What it covers |
|---|---|
| Start Here | Overview, reading paths, quick start |
| Method | Keyword research, research & optimization, generation, quality |
| Publishing | Terminal publishing, bridge, QA gate, WordPress contract, XML sitemaps |
| Operations | Workspaces, runbooks, keybindings, performance, multi-site |
| System Reference | Architecture, CSV model, front matter, gates, commands, fields |
| Business & Tools | Monetization and data sources |
| Cheatsheet | One-page references: CLI, statuses, front matter, publishing, troubleshooting |
| Changelog | Development history |
New here? Read Overview, then Quick Start, then the Documentation Map to pick your path.
Core principles
- Files over databases — plain CSV and Markdown, Git-friendly, terminal-first.
- CSV is the control plane — Markdown is a rendered, self-describing view.
- One file per article — the brief and the draft live together under
md/. - Human in the loop — GOS is supporting; the operator records the decision.
- Gates, not vibes — research, brief, QA, and publish checks fail closed.
- Any site, any tool — register a site; import exports from whatever SEO tool you use.