Search consoles are the most underused integration. Most teams check Search Console once a month, then ignore it until a ranking drops. SiteCMD wires it into your scan output so a thin meta description or a broken canonical tag gets paired with the actual impact: clicks lost, impressions dropped, queries you’re not ranking for anymore.

You don’t have to use both. Connect whichever search consoles you actually look at.

Google Search Console

Search Console connects via OAuth, using the same Google sign-in as Google Analytics. If you’ve already connected GA4, you can authorize Search Console without going through the consent flow again.

Setup

Settings → Integrations → Google Search Console, click Connect.
Pick the Google account that has access to the property you want to use.
Approve the Search Console read-only scope.
Pick the property (verified site) for this project. The property must match the URL you’re scanning, or be a parent of it (e.g. sc-domain:example.com covers https://example.com/anything).
Click Save.

What it pulls

30-day totals: clicks, impressions, CTR, average position
Top 5 queries you’re showing up for
Top 5 pages by impressions
Day-by-day stats so SiteCMD can flag drops

Cross-source correlation

This is where Search Console earns its keep. When SiteCMD detects an indexability issue in a live-site scan (e.g. a noindex meta tag, a 404 in your sitemap, a broken canonical), and Search Console shows a corresponding drop in impressions or clicks for the affected URLs, the dashboard links them directly. You see one finding with both signals attached: “this canonical is wrong, and Search Console shows impressions for /products/ down 38% in the same window.”

This requires Core or above.

Scope and permissions

The OAuth scope is read-only. SiteCMD can’t submit URLs for indexing, can’t change site settings, can’t delete properties, and can’t read anything outside Search Console.

Bing Webmaster Tools

Bing connects via API key. Bing’s API is similar to Google’s but the dashboard for getting a key is hidden one or two layers deeper.

Setup

Sign in to Bing Webmaster Tools.
Click the gear icon in the top right, then Settings.
Open API Access, then API Key.
Copy the API key.
In SiteCMD, Settings → Integrations → Bing Webmaster, click Connect.
Paste the API key.
Enter the site URL for this project. It must match a site you’ve verified in Bing Webmaster Tools (typically the full origin, e.g. https://example.com).
Click Save.

What it pulls

30-day totals: clicks, impressions, CTR, average position
Top queries and top pages
Crawl errors and indexed page counts

Bing’s data lags slightly behind real-time (typically 1-2 days). That’s a property of the API, not SiteCMD.

Why connect both

Google and Bing don’t share their indexes. A query that Google ranks you for might be invisible on Bing, and vice versa. If your audience leans even slightly toward Bing (more common in B2B, enterprise, and over-40 demographics than people assume), running with only Google data is misleading.

The dashboard merges both. When you have GSC and Bing connected, the search card shows combined impressions and clicks, with per-engine breakdowns one click away.

Where the data shows up

Dashboard → Search card. Clicks, impressions, top queries, top pages.
Events timeline. Significant ranking or visibility drops appear as events.
Issues page. Indexability and SEO findings get correlated against search data on Core and above.

Privacy

Search-console requests go from your machine to Google’s APIs or Microsoft’s APIs directly. They don’t pass through SiteCMD servers. SiteCMD stores only what it needs for the dashboard: aggregate totals, top queries/pages, and day-level series. Individual user search behavior isn’t accessed and isn’t part of either API.