Explore SEOForge

Documentation

From paid workspace to trustworthy first baseline.

This implementation path keeps account setup, provider authorization, evidence ingestion and production permissions separate. Commands are illustrative until the relevant public distribution is released.

Nothing publishes without approvalPaid product accessNo ranking guarantees
sf auth login --environment live
sf context set --workspace ws_123 --site site_123
sf sites health

Quickstart

Reach baseline before autonomous activation.

  1. 01

    Subscribe and create the workspace

    Evidence, owner and next state remain visible.

  2. 02

    Add a site without granting production authority

    Evidence, owner and next state remain visible.

  3. 03

    Authorize analytics and search providers

    Evidence, owner and next state remain visible.

  4. 04

    Authorize GitHub or WordPress with least privilege

    Evidence, owner and next state remain visible.

  5. 05

    Run readiness and baseline checks

    Evidence, owner and next state remain visible.

  6. 06

    Configure budgets, reviewers and schedules before activation

    Evidence, owner and next state remain visible.

Authentication

Use the identity flow that matches the caller.

Interactive

Use browser authorization with PKCE. Never paste provider credentials into commands or agent prompts.

Service

Create a revocable token inside an authorized workspace and restrict it to required operations, site and environment.

Scopes

Start read-only, then add the smallest request scope.

  • sites:read · runs:read · findings:read · proposals:read
  • runs:request for bounded agent assignments
  • webhooks:manage for endpoint configuration
  • No approve, merge, deploy, credential-read or bypass scope exists

Rate limits

Handle limits as normal control flow.

Published limits can vary by plan and endpoint. Read returned limit, remaining, reset and Retry-After headers; use backoff with jitter and never retry non-idempotent requests blindly.

Errors

Log the request ID without logging the token.

{
  "error": {
    "code": "scope_denied",
    "message": "Token cannot access this site",
    "request_id": "req_example"
  }
}

Paid deployment · human authority

Connect production only after the baseline and authority model pass review.

Product and developer access require a paid plan.