Skip to main content

Quick Start

This walkthrough moves one article from an exported keyword row to a WordPress draft. Replace client-site, bs, and CLI-0001 with your own values.

1. Register the site and workspace​

scs init
scs add-site client-site --domain client.example --prefix CLI --name "Client Site"
scs ws bs
scs sites          # confirm the registry
scs ws --list      # confirm the workspace

A site is a domain plus its WordPress connection. A workspace is the content program that holds the CSVs and files. They are separate on purpose.

2. Import keyword data​

Export from whatever SEO tool you use, then import the CSV:

scs import-csv --site client-site --workspace bs --source Writerzen export.csv
scs score --workspace bs

--source accepts SpyFu, GKP, Writerzen, NeuronWriter, Manual, AI, or Other. SCS stores provenance; it does not call the tool.

3. Research the keyword​

scs research --workspace bs --pid CLI-0001

Fill in data/bs/research/CLI-0001/README.md and serp.md, and save the tool export (for example a NeuronWriter JSON) in research/CLI-0001/exports/.

scs research --workspace bs --pid CLI-0001 --check
scs research --workspace bs --pid CLI-0001 --check --require-export

4. Record the human decision​

In data/bs/bs-keywords.csv, set decision=go, decision_reason, decision_factors, decided_by, and decided_on. GOS is supporting evidence, not the verdict.

5. Write and approve the brief​

scs brief --workspace bs --pid CLI-0001

This creates one Markdown file:

data/bs/md/CLI-0001--your-title.md

The brief and the article share that file. The brief half sits between <!-- scs:brief --> and <!-- scs:article -->; the article goes after the article marker. Fill sections 1–10, then:

scs brief --workspace bs --pid CLI-0001 --check
scs brief --workspace bs --pid CLI-0001 --approve

6. Write the article​

Open the same file and write the article after <!-- scs:article -->. Keep the brief half intact so scs brief --check continues to pass.

nvim data/bs/md/CLI-0001--*.md
scs sync --workspace bs
scs check --workspace bs

7. Publish from the terminal​

scs publish --workspace bs --pid CLI-0001 --dry-run
scs publish --workspace bs --pid CLI-0001
scs publish --workspace bs --pid CLI-0001 --status

--dry-run is fully local. The real command creates or updates a draft keyed by scs_pid; it never publishes a live post.

note

The current CLI supports draft creation/update and --status read-back. It does not support --to or --date state transitions. Use the site's approved WordPress workflow for pending, scheduled, or live status.

8. Review and measure​

Review the rendered post in WordPress, set the review gate fields, then pull the QA snapshot:

scs qa open --workspace bs --pid CLI-0001
scs qa pull --workspace bs --pid CLI-0001
scs qa check --workspace bs --pid CLI-0001 --advance

Pull GSC query data into performance.csv on your monthly cadence.

Where things live​

data/bs/
├── bs-keywords.csv        # master row, decision, GOS, status
├── bs-clusters.csv        # pillar/cluster plan
├── bs-briefs.csv          # brief index and gate fields
├── bs-links.csv           # internal-link plan
├── bs-publishing.csv      # WordPress metadata and QA snapshot
├── bs-performance.csv     # GSC query history
├── research/CLI-0001/     # SERP evidence, exports, prompts, assets
└── md/CLI-0001--*.md      # brief + article, one file