Integrations
What you connect, what bisibility makes of it, where it shows up.
Connect your own accounts and see exactly what each one feeds, and where it shows up in the product.
How your data flows
Three source segments show what you connect or enable, what bisibility produces, and where it appears.
SERP providers
The only source of rank positions.
1. You connect
- DataForSEOLogin and password
- SerpApiAPI key
2. bisibility produces
- Rank checks
Position and ranking URL for every tracked keyword.
3. You see it in
- Overview
- Keywords grid
- Keyword detail
- Timeline and alerts
Analytics sources
Traffic and index context for keywords you track - never used for rank positions.
1. You connect
- Search ConsoleOAuth, read-only
- Google Analytics 4OAuth, read-only
- PlausibleStats API token
2. bisibility produces
- Traffic snapshots
Clicks, impressions, CTR, and sessions next to each keyword.
- Index presence
Whether your pages are indexed, with alerts when that changes.
- Keyword suggestions
Queries you already rank for, offered when you add keywords.
3. You see it in
- Keyword detail: traffic card
- Keywords grid: Clicks · Impr. · CTR
- Search Console
- Timeline and alerts
- Onboarding: Add keywords
Sitemap checks
One public XML is checked daily. No account needed.
1. You enable
- Sitemap monitoringYour public XML, no account needed
2. bisibility produces
- Sitemap changed events
Checked daily, 04:45 UTC by default. A change shows up as a “Sitemap changed” event on your Timeline.
3. You see it in
- Timeline
Sitemap changes beside rankings, analytics, and deploys.
SERP providers
DataForSEO
Login and password
- Rank positions
- Ranking URL
Pay as you go. We use the cost reported for each completed check.
SerpApi
API key
- Rank positions
- Ranking URL
Has a monthly free tier - requests are counted against your plan.
Analytics sources
Google Search Console
OAuth, webmasters.readonly
- Top queries
- Clicks · impressions · CTR
- Average position context
- Index status
Google Analytics 4
OAuth, analytics.readonly
- Site-search terms
- Organic landing-page sessions
- Engagement rate
Plausible
Stats API token
- Organic page stats
- Visitors · bounce · scroll depth
- Works with your self-hosted Plausible instance.
Analytics adds context to your rank data - clicks, impressions, sessions, and page context. Rankings still come from completed SERP checks.
Where you'll see it
Every connection lands somewhere concrete. Here is each surface on its own.
Position trend and distribution
The dashboard that opens on every rank check, showing how you are trending at a glance.
- Four KPI cards
- Position-trend chart over time
- Data-source panel showing which provider answered
Avg. position6.2
Tracked keywords248
In top 10143
Visibility38%
Traffic card beside position history
The one place rank and traffic sit together: SERP position on top, your own data underneath.
- SERP position history from rank checks
- GSC clicks, impressions, CTR, and average position
- Matched to the target or ranking page
headless cms#3
Clicks1,284
Impressions26.7k
CTR4.8%
Avg. position6.4
Every change as a signal
One filterable feed where all pipelines converge, and any signal can drive an alert.
Timeline
ranking.changed · headless cms1m
url.indexed · /pricing3h
Sitemap changed · 4 new URLs5h
Your credentials, your requests
Self-hosted requests use your provider keys directly. The hosted service stores the credentials you configure encrypted, and uses them only for your checks.
Read-only Google scopes
Search Console and Google Analytics 4 connect with read-only scopes. bisibility can read data, never write it.
Self-hosted, no middleman
Run it on your own infrastructure - your keys, your requests, no middleman.
Billed directly by each provider
Bring your own keys and pay providers directly. No markup and no resale of rank data.