Documentation Map

This site documents two things:

• the method — how to research, brief, write, and publish SEO content;
• the system — how SCS stores state, enforces gates, and talks to WordPress.

Pick a path

You are…	Read in this order
New to SCS	Overview → Quick Start → Workflow
Running the pipeline daily	Terminal Runbooks → Command Reference → Troubleshooting
Writing or editing content	Keyword Research → Research & Optimization → Content Generation → Quality & E-E-A-T
Reviewing in WordPress	QA Gate → Publishing Workflow
Setting up a new site	Multi-Site → Workspaces & Shell → WordPress Contract
Selling or packaging the service	Monetization → Data Sources and Tools
Need a quick reference	CLI Usage → Workflow & Statuses → Troubleshooting

Method vs system

Method pages	System pages
What good SEO content requires	How SCS stores and enforces it
Tool-agnostic advice	Concrete commands, CSVs, and fields
Sections 02–03	Sections 04–05

tip

If you only need to publish today, read Publishing Workflow and Terminal Runbooks. You do not need the architecture pages.

Conventions used in these docs

• data/<workspace>/ is a workspace folder; data/<workspace>/md/ holds articles.
• <pid> is a content ID such as FS-0001.
• Commands accept --workspace or the short --ws.
• Implemented means the command exists in the current SCS release.
• Contract means the command or state is documented for the agreed interface and may not be wired yet. Publishing states are currently in this category.