SiteCMD connects to the tools you already use: analytics, search consoles, uptime monitors, hosting providers, and issue trackers. Each connection gives the scan engine more evidence to work with, and each is configured per-project.

This page explains the model. The pages that follow cover individual integrations.

What integrations do

Three things, in order of how much value they add.

1. They show up as raw data. Once connected, you can see your traffic, uptime, search performance, and deploy history directly in SiteCMD. This works on every tier.

2. They correlate with scan findings. When traffic drops after a deploy and your scan catches a broken canonical tag in the same window, SiteCMD ties them together. The dashboard shows “traffic dropped 22% after deploy abc123, and these issues appeared in the same window.” This is what turns scan data from a checklist into a useful tool. Cross-source correlation is gated to Core and above.

3. They become fix destinations. Issue tracker integrations (GitHub Issues, Jira) let you mirror findings out of SiteCMD into your existing workflow, so the work doesn’t sit in a separate tool. Ticket mirroring is gated to Core and above.

What you connect

Category	Integrations
Analytics	Google Analytics 4, Plausible
Search	Google Search Console, Bing Webmaster
Uptime	UptimeRobot
Hosting / CDN	Cloudflare
Repository / Deploys	GitHub
Performance	PageSpeed Insights
Issue tracking	GitHub Issues, Jira
Code review (optional)	Semgrep, CodeRabbit

Most projects connect 3-4 of these. You don’t need all of them.

How auth works

SiteCMD uses the simplest auth method each service supports:

OAuth for Google services (Analytics, Search Console) and GitHub. You click Connect, the service’s auth page opens in your browser, you approve, you’re done.
API key for everything else (Plausible, Cloudflare, UptimeRobot, Bing, Jira, Semgrep, CodeRabbit). You generate the key in the service’s dashboard, paste it into SiteCMD.

All credentials, OAuth tokens, and API keys are stored in your operating system’s credential store, not in SiteCMD’s database. See Local-first architecture for the details.

Where you set them up

Open Settings → Integrations from the sidebar. Each integration has a row with its current status (Connected, Disconnected, Error) and a button to add or edit credentials. You can connect, test, and disconnect from this page.

Once connected, the integration’s data starts showing up in two places:

Dashboard. The relevant cards (analytics, uptime, deploys) populate with live data.
Issues page. Findings from the integration get merged into the unified Issues list, ranked alongside scan findings.

Removing an integration

Click Disconnect on the integration’s row. SiteCMD asks for confirmation, then:

Deletes the saved credential from your OS keychain.
Removes the integration record from the local database.
Invalidates any cached responses.

The integration’s own data on the third-party service is untouched. Disconnecting SiteCMD does not delete anything in Google Analytics, GitHub, etc.

Tier summary

Tier	What you get
Free	Connect any integration. See raw data in the dashboard.
Core	All Free features, plus cross-source correlation, fix guides for integration-sourced findings, and ticket mirroring (GitHub Issues, Jira).
Pro	All Core features, plus webhooks and automation triggered by integration events.

See Pricing for the full breakdown.