Action items
A curated queue of what to do next, separate from the main issue list.
350+ hard pass/fail checks across your code and your site, correlated with the third-party tools you already use. Seeing every signal together catches issues a single tool would miss, and regressions before your users notice.
It's all there the moment the app opens: current health, what changed since the last scan, and what needs fixing first. Every tool you've connected feeds in right alongside it. No tabs to flip. No dashboards to stitch together.
A curated queue of what to do next, separate from the main issue list.
Background scans push notifications when something changes. Every alert opens into a full dossier.
Sparklines on the overall score and each category. See what's improved and what's slipped since your last scan.
The dashboard is the overview. These are the close-ups. A purpose-built view for traffic, search, security, and deploys, with context raw integration data can't give you on its own.
GA4 and Plausible sessions, top pages, and source shifts, lined up next to your scan health.
Clicks, impressions, ranking shifts, and indexability. Caught the moment they happen.
Web scan, code scan, and npm audit findings combined into a single security posture view.
Recent GitHub Actions runs, release status, and deploy-correlated regressions in one timeline.
Unified activity feed of every scan, deploy, uptime incident, and anomaly across the project.
Pending dependency updates across npm, pip, composer, cargo, and go. Severity, breaking-change risk, and post-fix verification tracked over time.
A scan is only useful if you act on it. SiteCMD pulls every finding into one list, opens each with full context and a ready-to-send fix prompt, then keeps watching so the same problem doesn't ship twice.
Scanning is just the start. SiteCMD keeps every scan in your local history, diffs new scans against old ones, exports reports for stakeholders and pipelines, and rolls everything up across every site you manage.
Every scan stored locally with its findings. Sort and filter by date, severity, or category to see exactly what changed and when.
Diff any two scans side by side. See which issues appeared, which got fixed, and which regressed between them.
Generate PDF reports for stakeholders or JSON exports for downstream pipelines. A custom builder shapes the report for client deliverables.
Manage every site you own from one workspace. The Sites overview rolls up health, issues, and recent activity across the whole portfolio.
SiteCMD runs its own checks through two engines. Web Scan audits your running site, whether that's local dev, staging, or production. Code Scan reads your source tree. Both run 100% locally on your machine, and together they cover 350+ distinct issue types.
Sees your site the way the internet does.
Point Web Scan at any URL. SiteCMD pulls the page, parses the HTML, probes the response, and runs every check in parallel.
Headers, SSL, CSP, mixed content, exposed files, cookies, clickjacking
Core Web Vitals, compression, cache policy, render blocking, image optimization
Canonicals, robots, sitemap, structured data, indexability, meta tags
axe-core WCAG 2 A/AA engine plus native checks: contrast, ARIA, focus order, headings, landmarks
Privacy policy, cookie consent, data retention, legal footer
Framework defaults, placeholder copy, AI aesthetic, HTML quality, meta gaps
Reads your code the way an engineer does.
Point Code Scan at any local source folder. SiteCMD walks the project, parses package manifests, inspects database access patterns, and flags the issues live scans can't see.
Timeouts, rate limits, spend caps, and observability on your AI integrations. Loop detection, output caps, and concurrency safety on every model call.
Vulnerable packages, outdated majors, license risk, lockfile drift
Hardcoded secrets, exposed .env files, broken auth flows, unsafe request validation, webhook gaps
Migration drift, missing foreign keys, unsafe ORM patterns, schema-vs-runtime mismatch
Tight coupling, circular deps, dead code, leftover scaffolding
console.log as error handling, debug code in production, missing rollbacks, broken error reporting
When traffic drops or rankings slip, the symptom shows up in one tool and the cause hides in another. SiteCMD pulls signals from the services you already use and correlates them against its own scan findings, so symptom and cause sit side by side.
Deploy history, CI status, and PR context.
Edge cache, threat events, and bandwidth.
Privacy-first traffic and top pages.
GA4 sessions and source breakdown.
Clicks, impressions, and ranking shifts.
Visibility and crawl data.
Lighthouse lab metrics and real-user CrUX data.
Availability and incident history.
Issue ownership and follow-ups.
Coming soon: pull your CodeRabbit review findings into the unified list.
Coming soon: surface your Semgrep AppSec findings alongside SiteCMD's own scan.
The desktop app is the primary command center, but the same engine runs from your terminal, inside your CI/CD pipeline, and through any AI editor with MCP support. Wherever you ship, SiteCMD goes with you.
For your terminal and your CI.
A standalone binary runs the full scan engine without the desktop app. Drop it into GitHub Actions, fail builds on severity thresholds, output JSON for downstream gates, or run a focused scan from staging in your terminal.
For Cursor, Claude Code, Windsurf, and any other MCP-compatible editor.
Built-in MCP server exposes scan results, issue data, and fix prompts to AI coding agents. Your editor stops guessing because it can actually read what's broken and where. The fix it writes is grounded in real findings, not vibes.
Your scans, your credentials, your source code all stay on your machine. SiteCMD has no cloud backend, no upload pipeline, no shared infrastructure. There's nothing to breach because there's nothing in the cloud.
Tauri-based, runs natively on macOS, Windows, and Linux. Tiny binary, no Electron weight.
API keys and OAuth tokens live in your system keychain, encrypted by your OS. They're never stored in a database file.
Scan history, code findings, dossiers, and pulled-in integration data live in a SQLite file on your machine. Back it up like any other file.
License checks and app updates are minimal. Optional usage analytics and crash reports only run if you opt in from the desktop app.