Connectors Overview
Connectors bring external data into VisibilityIQ so your audit findings are grounded in real-world signals — not just what the crawler found. Without connectors, you know a page has a canonical issue. With connectors, you know that page gets 5,000 visits per month from Google and ranks for 47 keywords, which tells you it’s urgent.
flowchart LR
C[Crawl finding<br/>canonical issue on /page] --> J{Join with<br/>connector data}
GSC[(Search Console)] --> J
GA4[(Analytics 4)] --> J
CRUX[(CrUX)] --> J
J --> P([Prioritised finding<br/>5,000 visits/mo · 47 keywords<br/>→ High priority])
Available connectors
Section titled “Available connectors”| Connector | What it provides | Required for |
|---|---|---|
| Google Search Console | Index coverage, search performance (clicks/impressions/CTR/position), sitemap status, URL inspection | GSC-reconciled canonical findings, traffic-weighted issue prioritization |
| Google Analytics 4 | Landing page sessions, engaged sessions, conversions, revenue | Traffic-weighted prioritization, conversion impact |
| CrUX | Field LCP/INP/CLS by origin and URL, mobile/desktop | Real-user performance data (vs Lighthouse lab data) |
| Bing Webmaster Tools | Bing index coverage, diagnostics, sitemap submission | Bing-specific crawlability findings |
| Rank tracking & keyword data | Keyword rankings (via rank tracking), backlinks (referring domains, Authority Score, toxic links, link gap) | Rank tracking, backlink data |
How connectors enrich findings
Section titled “How connectors enrich findings”When a connector is connected, VisibilityIQ joins its data with crawl findings in several ways:
Traffic weighting — A broken internal link on a page that gets 0 sessions per month is Low priority. The same issue on a page with 10,000 monthly sessions from organic search is High. Connector data lets VisibilityIQ prioritize what matters to your business, not just what exists technically.
External truth reconciliation — Your crawl may show a canonical tag pointing to URL A. GSC shows Google has selected URL B as the canonical. That discrepancy — Google overriding your declared canonical — is a separate finding that only appears when GSC data is connected.
Performance benchmarking — CrUX field data tells you what real users on real devices experience, across the full range of network conditions. Lab data from Lighthouse is reproducible but doesn’t capture the long tail of real-world variability.
Connecting Google — one click
Section titled “Connecting Google — one click”Google connectors (Search Console and GA4) use one-click “Sign in with Google.” VisibilityIQ owns and operates the Google OAuth application, so there’s no Google Cloud setup on your end — no project to create, no API to enable, no Client ID or Client Secret to paste. This means:
- You sign in with Google, approve read-only access, and pick which property to sync from a property picker
- You can connect whatever GSC and GA4 properties your Google account has access to
- Revoking is one click — Disconnect in VisibilityIQ, or remove the app from your Google Account → Security → Third-party access
See Connect Google for the setup walkthrough.
Sync cadence
Section titled “Sync cadence”| Connector | Default sync | Manual trigger |
|---|---|---|
| GSC | Daily | Yes |
| GA4 | Daily | Yes |
| CrUX | Daily | Yes |
| Bing | Weekly | Yes |
| Rank tracking & keyword data | Weekly | Yes |
All syncs are resumable — if a sync is interrupted, it picks up where it left off rather than starting over.
Connector health
Section titled “Connector health”Go to Project → Connectors to see the status of each connector: last sync time, records synced, and any errors. A connector with a red status means the last sync failed — common causes are expired OAuth tokens or revoked permissions.