Data Sources and Tools

No API dependency

SCS does not call SEO APIs and does not store API credentials. Data enters as manual exports from tools you already use. That keeps cost predictable and avoids a subscription becoming a hard dependency of the workflow.

Source	Access	What to export	Where it goes
SpyFu	LTD dashboard	Keyword rows: SV, KD, CPC, clicks, SERP features	staging/ → import-csv --source SpyFu
WriterZen	LTD	Keyword and cluster exports	staging/ → import-csv --source Writerzen
NeuronWriter	LTD	SERP/term analysis per query	research/<pid>/exports/
Google Keyword Planner / Ads	Free	Volumes and keyword ideas	staging/ → import-csv --source GKP
Google Search Console	Free	Query-level performance	<workspace>-performance.csv

note

Pick whichever tool you have access to. SCS uses the same columns regardless of source, and records source plus source_confidence so provenance is never lost.

Import workflow

# 1. Put the export in staging
cp ~/Downloads/keywords.csv data/bs/staging/

# 2. Import it into the workspace
scs import-csv --site fundamentalstock --workspace bs --source Writerzen \
  data/bs/staging/keywords.csv

# 3. Recompute GOS
scs score --workspace bs

The staging copy is a temporary input; the workspace CSV is the source of truth.

NeuronWriter

NeuronWriter is an optimization input, not a phase:

1. Run the analysis in the dashboard.
2. Export the result into data/<workspace>/research/<pid>/exports/.
3. Translate terms, PAA, entities, and word count into serp.md and the brief.

See Research & Content Optimization for the mapping table.

Google Search Console

GSC closes the loop after publishing. Export query rows and load them into data/<workspace>/<workspace>-performance.csv; the schema is documented in Field Reference.

Terminal toolchain

Tool	Role
SCS CLI	State, gates, front matter, publishing
VisiData	Explore and edit CSVs (vd)
Neovim	Write briefs and articles (nvim)
Yazi	Browse workspaces, research folders, and assets
opencode	Generate drafts with deepseek-v4.1-flash or deepseek-v4-pro
wp-cli	Runs on the WordPress host; SCS calls it over SSH
Git	Version CSVs, Markdown, and docs

WordPress side

The publish bridge needs WP-CLI and SSH access on each target site. Connection fields live in config/sites.csv:

scs add-site opshell --domain opshell.dev --prefix OPS \
  --wp-root /home/wp_opshell_dev/sites/opshell.dev \
  --wp-url http://opshell.dev --wp-user wp_opshell_dev --ssh-host GC-SG-M8

warning

Never put credentials in Markdown, CSV content rows, or these docs. Keep them in the server configuration and config/sites.csv only.

Optional technical audits

A separate crawler (for example Website Auditor or Screaming Frog) is useful for technical SEO checks — broken links, duplicate titles, indexability, sitemaps. SCS does not replace those tools; record the findings as research evidence when they affect a page.