Connect the data your AI search decisions need
Bring first-party search and analytics evidence into CiteLadder, configure supported model providers and add optional research when it is useful. Each connection has a defined purpose—not just a logo on a page.
Inside Integrations
Integrations · Property mapping
Zernovelle · Google Search Console
- Project domain
- zernovelle.example
- Selected property
- sc-domain:zernovelle.example
Connection management requires an Owner or Admin. A mapped property does not establish complete reporting coverage.
| Connection | Purpose | Setup / availability |
|---|---|---|
| Google Search Console | Query and page evidence | Verified property and saved mapping |
| Google Analytics 4 | Sessions and reported outcomes | Consent and property mapping |
| Bing Webmaster Tools | Bing search evidence | Separate consent and saved datasets |
| Model providers | Available audits and Agent workflows | Account access and provider configuration |
| DataForSEO | Optional external research | Scope, maximum cost and explicit confirmation |
| MCP | Read saved project evidence | Authorized compatible client |
First-party search and analytics
Google Search Console: Import supported query, page and search-performance evidence for your verified property. Use it in Performance and applicable Demand Intelligence workflows.
Google Analytics 4: Import supported traffic and session-attribution evidence. Use AI Referral Analytics to inspect recognized AI sources, landing pages and available engagement or outcome measures.
Bing Webmaster Tools: Connect supported Bing search data using its separate consent flow. Available reporting depends on the saved datasets and their coverage.
Model providers and optional research
Supported model-provider accounts: Configure the providers required by your available audit and Agent workflows. Engine access and usage depend on your account configuration. Provider/API collection does not reproduce every consumer-app experience.
DataForSEO: Add supported keyword, competitor and backlink research through the explicit scope-and-cost review workflow. This is optional research, not an automatic background purchase.
Use saved evidence in external assistants
MCP: Read authorized persisted project context through the supported read-only tools. Consult the current setup documentation for compatible clients and connection requirements.
Know what is connected and what is missing
A saved connection is not proof that every report has complete data. Review property mapping, imported windows, freshness and any quality notices before interpreting a missing number as zero.
Frequently asked questions
Must I connect every service?
No. Start with the sources needed for the workflow you want to use, subject to its access and setup requirements.
Does the website advertise native Shopify sync or universal automatic log collection?
No. Retired or release-gated connections must not be presented as generally available integrations.