Connecting data sources
How integrations work in SiteCMD, what they add, and where to set them up.
SiteCMD connects to the tools you already use: analytics, search consoles, uptime monitors, hosting providers, and repositories. 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
Two 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.
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.” Correlation is part of the complete free local workbench.
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 |
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). You generate the key in the service’s dashboard, paste it into SiteCMD.
- No required setup for PageSpeed Insights. SiteCMD calls Google’s public PageSpeed endpoint directly, no account needed. The shared public endpoint is rate-limited, so the Integrations page offers an optional card for a free Google API key that raises the limit substantially.
All credentials, OAuth tokens, and API keys are stored in your operating system’s credential store, not in SiteCMD’s database. See Why local-first 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.
Commercial boundary
Every desktop integration, its local data view, cross-source correlation, and fix guidance for integration-sourced findings are included in the complete free local workbench. The connected service adds hosted deploy watches, scheduled scans, shared baselines, alerts, and delivery while your laptop is closed. See Pricing & connected service.