Explore SEOForge

Command-line interface

Request SEO work from the terminal. Keep approval in the product.

The CLI is designed for explicit environment, workspace and site context. Public package and installation instructions will appear only after a signed release is available; commands shown here are illustrative.

Nothing publishes without approvalPaid product accessNo ranking guarantees
sf context show
sf runs request --site site_123 --workflow ranking-loss
sf runs watch run_example

Distribution status

Do not install an unverified similarly named package.

No public SEOForge CLI package is claimed as released here yet. Current documentation will provide the registry, package identity, version policy and verification method when available.

Command model

Inspect context before requesting work.

Read commands

  • sites list and health
  • runs list, show and watch
  • findings and proposals inspect
  • usage and provider status

Request commands

  • Explicit site and workflow
  • Bounded objective and optional budget
  • Idempotency key for supported requests
  • Returned run ID; no hidden wait

Authentication

Browser PKCE for people; scoped tokens for automation.

Store tokens in the OS credential store or approved secret manager. Never pass secrets in shell history when a secure prompt or environment integration exists.

Scopes

Context does not grant access.

Every command still checks token, workspace, site, environment and operation. Switching context cannot cross an unauthorized boundary.

Limits

Exit predictably on quotas and throttling.

The CLI should print request ID and retry guidance, honor Retry-After and avoid uncontrolled polling. Plan and provider capacity still apply.

Errors

Human-readable stderr and stable exit behavior.

scope_denied: token cannot access site_456 (request req_example)
exit 3

No authority commands

The CLI can never approve, merge, deploy, retrieve credentials or bypass protection.

Paid deployment · human authority

CLI access follows paid workspace authorization.

Choose a plan or talk to sales about service identities and automation volume.