Connect your own accounts and see exactly what each one feeds, and where it shows up in the product.
DataForSEO, SerpAPI
The only source of rank positions. Priority-ordered fallback, bring your own keys, and a configurable project budget cap.
Search Console, GA4, Plausible
Owned-data context for queries, clicks, impressions, sessions, and index status. They never determine rank positions.
Your accounts on the left, Bisibility pipelines in the middle, product surfaces on the right.
The only source of rank positions.
Self-hosted: enable the daily sync worker with one environment flag.
Login and password
Reports the actual cost for each completed check. Current Live estimates depend on depth: about $0.0020 for Top 10 and $0.0155 for Top 100.
Setup docsAPI key
Does not report a response cost, so your configured per-check estimate is used.
Setup docsOAuth, webmasters.readonly
OAuth, analytics.readonly
Stats API token
Analytics adds context to your rank data - clicks, impressions, sessions, and page context. Rankings still come from completed SERP checks.
Logos provided by Logo.dev
Beyond providers, here is where Bisibility plugs into the rest of your stack and what it looks like in practice.
Wire your host or CI to POST on every release. Each deploy lands as deploy.completed on the timeline, so ranking moves line up with what you shipped.
POST /api/ingest/deploy
Authorization: Bearer bsk_live_...You will be able to select Slack on an alert rule. When a keyword drops or a competitor overtakes you, the message will post to your channel.
headless cms on acme.dev: #8 → #12
View keywordConnect an AI assistant to the MCP endpoint to read rankings and trigger checks, or use REST API v1 from your scripts. OpenAPI and CSV exports are included.
curl -H "Authorization: Bearer bsk_live_..." \
your-instance.example.com/api/v1/keywords/kw_123/rank-checksEvery connection lands somewhere concrete. Here is each surface on its own.
The dashboard that opens on every rank check, showing how you are trending at a glance.
The one place both lanes sit together: SERP position on top, owned-data context underneath.
One filterable feed where all pipelines converge, and any signal can drive an alert.
Provider keys are encrypted in your own database. Bisibility never proxies provider requests.
Search Console and GA4 connect with read-only scopes. Bisibility can read data, never write it.
Run it on your own infrastructure. On Cloud, the same provider-data boundaries apply.
Bring your own keys and pay providers directly. No markup and no resale of rank data.
Deploy Bisibility, connect your keys, and keep your rank data on infrastructure you control.