Capabilities

Website
Command
Center

SiteCMD is built around three jobs: operate the current site, connect the services around it, and inspect it with built-in checks when you need deterministic truth.

Product model

Operate

Dashboard, Issues, History, Overview

Connect

Analytics, uptime, search, deploy, repo

Inspect

Web Scan and Code Scan signals

Local-first One place to see and act

Operate

Operate the current site.

Dashboard

Current health, important changes, and the signals that need attention now.

Issues

One queue for actionable fixes across built-in SiteCMD findings and connected follow-ups.

History

Review recent runs, compare what changed, and verify whether fixes actually held.

Overview

Roll up multiple sites into one cross-site view when you are operating more than one property.

Connect

Connect the stack around the site.

Service integrations

Pull in analytics, uptime, search, deploy, and repo context so SiteCMD is not operating from scan results alone.

GitHub and deploy context
Plausible and GA4 traffic
Cloudflare edge delivery
Search Console and Bing visibility
Uptime monitoring and incidents
Semgrep AppSec findings
CodeRabbit review workflow context

Connected signals, not disconnected tabs

Integrations are a first-class part of the product. They influence the Dashboard, add context to Issues, and help explain whether a change was a release problem, a traffic problem, or a real site regression.

Inspect

Inspect with built-in SiteCMD checks.

Web Scan and Code Scan remain inside SiteCMD as deterministic first-party signals. They support the command center instead of trying to be the product story by themselves.

Web Scan

Live-site signals

▶ Security headers, SSL, exposed files

▶ Performance and Core Web Vitals context

▶ Search and indexability signals

▶ Accessibility and semantic structure

▶ Compliance and overall polish

Code Scan

Linked-code signals

▶ Dependency vulnerabilities and package risk

▶ Database, auth, and API guardrails

▶ AI-generated anti-patterns and release blockers

▶ Architecture and operations risks

▶ Verification-ready findings for the fix workflow

Workflow

Bring SiteCMD into how you ship.

AI tools and terminal workflows

Core and Pro unlock CLI access plus MCP for Cursor, Claude Code, Codex, and other AI tools so your workflow keeps the same source of truth.

{
  "mcpServers": {
    "sitecmd": {
      "command": "node",
      "args": ["~/.sitecmd/mcp-server/index.js"]
    }
  }
}

Quality gates for releases

Use the CLI in CI/CD to block risky releases, run deterministic checks in staging, and keep the same thresholds across the app and the pipeline.

$ sitecmd scan   --url https://staging.your-site.com   --fail-under 80   --output json

Taxonomy

Detailed check areas stay underneath the operating story.

Web Scan categories

Security, Performance, SEO, Accessibility, Compliance, and Polish.

Code Scan domains

Dependencies, Database, Security, AI Safety, Architecture, and Operations.

WebsiteCommandCenter