Integrations
Connect Digispot to Google Search Console, GA4, and the MCP server so findings are ranked by real traffic and queryable by AI agents.
Digispot integrates with external data sources so findings are not just graded by severity — they are ranked by the traffic, rankings, and coverage that actually matter to the site.
Google Search Console
Search Console is the highest-leverage integration. Once connected, every page's issues are weighted by the queries and clicks that flow through it, so a broken page on a top-ranking URL rises above a broken page on an orphan.
What it unlocks:
- Clicks, impressions, CTR, and position by query, URL, country, and device
- URL Inspection verdicts — live indexing status per page
- Indexability gap — pages that Search Console isn't indexing, correlated against the crawl
- High-traffic pages at risk and striking-distance queries
- Query cannibalization detection
How to connect on the Desktop Spider:
- Open the Spider app and load a project.
- Go to Google integrations in the project sidebar.
- Click Connect Search Console and complete the OAuth flow in the browser window that opens. Grant at least Read permissions for the property you want to track.
- Select the GSC property matching your project's domain. Data loads on the next crawl.
How to connect on the Cloud Platform:
- Go to Settings → Projects & Integrations.
- Select your project and click Add integration → Google Search Console.
- Complete the OAuth flow. The property appears in the project's Google Insights section after the next scheduled crawl.
Google Analytics 4
GA4 adds the engagement layer to technical findings. A page with 10,000 monthly sessions and a broken heading structure is a higher-priority fix than the same issue on a page with 10 sessions.
What it unlocks:
- Sessions, users, and engagement per URL
- Traffic sources — organic vs direct vs referral breakdown
- Mobile vs desktop split, so device-specific issues are prioritized against real device traffic
How to connect on the Desktop Spider:
- In the Spider project, open Google integrations.
- Click Connect GA4 and complete the OAuth flow.
- Select the GA4 property and the data stream matching your site. The Spider imports up to 16 months of historical data on first sync.
How to connect on the Cloud Platform:
- Go to Settings → Projects & Integrations → Integrations.
- Click Add integration → Google Analytics 4.
- Complete the OAuth flow and select the GA4 property.
Google Business Profile
Google Business Profile (GBP) data powers the Local SEO checks in both the Spider and the extension. Connecting it lets Digispot verify NAP (name, address, phone) consistency, detect duplicate listings, and confirm opening-hours markup against the live profile.
GBP connection is managed through the same Google OAuth flow as Search Console. On the Desktop Spider, go to Google integrations and click Connect GBP. On the Cloud Platform, add it under Settings → Projects & Integrations.
MCP server
The MCP server is the integration for AI assistants and coding tools. It lets Claude Code, Cursor, or Windsurf query your crawl data directly — so an agent can pull the top issues, start a crawl, or surface content opportunities without any copy-paste.
The MCP server comes in two forms:
- Desktop Spider — a local stdio server, bound per project, with 60+ tools. See MCP server docs.
- Cloud Platform — an HTTP server with API keys managed under Settings. See API access.
For setup instructions and a tool reference, see MCP server.
Which integrations are available per product
| Integration | Chrome extension | Desktop Spider | Cloud Platform |
|---|---|---|---|
| Google Search Console | Via Extension Key (CrUX/PageSpeed only) | Full OAuth, per project | Full OAuth, per project |
| Google Analytics 4 | — | Full OAuth, per project | Full OAuth, per project |
| Google Business Profile | — | Full OAuth, per project | Full OAuth, per project |
| MCP server | — | stdio, 60+ tools | HTTP, via API key |
| HTTP API | — | — | Available on Starter+ |