Connect your own accounts and see exactly what each one feeds, and where it shows up in the product.
SERP providers: DataForSEO and SerpApi, with your own keys. The only source of rank positions.
Analytics sources: Search Console, Google Analytics 4, and Plausible, read-only. They never determine rank positions.
Two lanes, three steps each: the accounts you connect, what bisibility makes from them, and where it shows up.
The only source of rank positions.
Position and ranking URL for every tracked keyword.
Self-hosted: enable the daily sync worker with one environment flag.
Clicks, impressions, CTR, and sessions next to each keyword.
Index status for your pages, as signals you can alert on.
Queries you already rank for, offered when you add keywords.
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.
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 bsb_key_live_...Connect 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 bsb_key_live_..." \
your-instance.example.com/api/v1/keywords/kw_a00000000000000000000000/rank-checksYou 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 keywordEvery 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.
Self-hosted requests use your provider keys directly. The hosted service securely uses the provider credentials you configure.
Search Console and Google Analytics 4 connect with read-only scopes. bisibility can read data, never write it.
Run it on your own infrastructure. On the hosted service, 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.