Google Search Console and GA4 feed real-world signal into your AI Visibility Score. HubSpot and GoHighLevel sync scores into deal records and client pipelines. Slack, Teams, Zapier, Make, and Looker Studio route alerts and reports where your team already lives. Every integration's status disclosed openly — same discipline we apply to platform coverage.
AEO tools usually flatten "integrations" into a single grid of logos. AIVZ separates them into three classes — because the three classes have genuinely different relationships to your site, your team, and the AI Visibility Score itself.
Where AIVZ pushes changes into your site. When AIVZ acts on an Execution Surface, your public-facing output changes — new schema, new copy, new meta tag, new llms.txt entry. CMSes and storefront platforms.
Coverage detail at /platformsWhat AIVZ pulls into the score. Signal flows one direction: into AIVZ's diagnosis. Data Sources don't change your site — they make AIVZ's scoring more accurate by adding real-world data the on-page scan alone can't see.
Where AIVZ sends signal out to your workflow. Notifications land in Slack or Teams. Scan completion triggers a HubSpot pipeline event. Score changes route through Zapier or Make. Reporting flows into Looker Studio.
A complete AEO engagement uses all three. Execution Surfaces are where the work lands. Data Sources make the scoring faithful to real-world outcomes. Orchestration Endpoints make the work routable through the systems your team already trusts.
AIVZ's structural scan answers: is this content built right? Data Sources answer the next question: is the world actually finding it? Two integrations — both Live — connect AIVZ to the systems that hold that real-world signal.
Connecting GSC turns the AI Visibility Score from a structural prediction into a structural prediction cross-checked against actual indexed presence. Permissions are read-only — AIVZ never writes to GSC.
AIVZ correlates AEO score against engagement outcomes. URLs scoring well that show poor engagement are flagged as potential mismatch between structural quality and content fit. Read-only — AIVZ never writes to GA4.
The Integrations canon constrains Data Sources to surfaces that meaningfully sharpen AEO diagnosis. GSC and GA4 are the two systems that hold the load-bearing signal for AEO scoring at scale. Heatmap tools, session replay, behavioral analytics — they don't carry signal that materially changes the AI Visibility Score, so AIVZ doesn't surface them as Data Sources. The disclosure discipline applies to scope just as much as it applies to status.
The AI Visibility Score is most useful where your team already works. AIVZ surfaces six Live Orchestration Endpoints — covering CRM pipeline triggers, agency client workflow automation, alerts in Slack and Teams, low-code routing through Zapier and Make, and reporting through Looker Studio. Each one shipped, each one operational.
Pipeline triggers on scan completion. Contact and deal record creation. Custom property syncing — ai_visibility_score, ai_visibility_tier, scan-history fields — populated against contact or company records.
Agency client pipeline triggers. Contact and opportunity creation. Custom field syncing for AEO score data. Native automation builder support. Location and company mapping for multi-tenant agency operations.
REST hook connector wired to six AIVZ events: scan.complete, score.changed, crawl.complete, credits.low, tier.changed, alert.created. Event-level filtering. Sample payloads for downstream mapping.
Webhook-based notifications with rich message formatting. Three event types wired by default: scan-complete summaries, score alerts (changes above configurable thresholds), and weekly digests aggregating activity across all monitored domains. Outbound dispatcher in the AIVZ worker process.
Same event surface as Slack, adapted for Teams' message-card formatting. Webhook-based, rich formatting, scan-complete + alerts + weekly digests. Same outbound dispatcher in the AIVZ worker.
Data connector with schema definitions for AIVZ scans, crawls, and historical score data. HMAC-SHA1 embed URL generation for secure dashboard sharing. BigQuery-compatible data fetching with date-range filters — historical AEO trends render natively inside Looker Studio reports.
A subscriber-list-sync and content-recommendation-trigger framework is documented for eight Email Service Providers — Mailchimp, ConvertKit, Beehiiv, Mailgun, Klaviyo, ActiveCampaign, plus HubSpot's and GoHighLevel's marketing-email surfaces. The framework is published in canon. Native ESP-specific code has not been built.
What works today: Zapier and Make cover ESP routing for most workflows — when AIVZ fires score.changed or scan.complete, the routing layer can deliver that signal into virtually any ESP. HubSpot's CRM-side integration also covers HubSpot-as-marketing-email use cases.
Why it's surfaced honestly: Documented-but-Unbuilt is a deliberate status. The framework exists in canon; the native build hasn't shipped. Surfacing the gap honestly — rather than including the ESPs in the integration grid as if they were Live — is the disclosure discipline.
The complete matrix across all three classes. Statuses are accurate as of May 1, 2026; the Integrations canon is the authoritative source. Execution Surface depth lives at /platforms; Data Sources and Orchestration Endpoints depth is in this page's earlier sections.
| Integration | Class | Status | Tier | Direction |
|---|---|---|---|---|
WordPress via AnswerEngineWP |
Execution | Live | Free / Pro / Agency | ⇄ Bi-directional |
Shopify |
Execution | Beta | Pro+ | → Outbound (write) |
Wix |
Execution | Beta | Pro (planned) | → Outbound (write) |
Webflow via MCP/CLI |
Execution | Beta | Agency+ | → Outbound (via agent) |
BigCommerce |
Execution | Beta | Pro+ | → Outbound (write) |
Headless / Custom via MCP/CLI |
Execution | Beta | Agency+ | → Outbound (via agent) |
WooCommerce inherits from WP adapter |
Execution | Beta | Pro+ | → Outbound (write) |
Squarespace |
Execution | Roadmap | Pro (planned) | — |
Google Search Console |
Data Source | Live | Pro+ | ← Inbound (read) |
Google Analytics 4 |
Data Source | Live | Pro+ | ← Inbound (read) |
HubSpot |
Orchestration | Live | Agency+ | ⇄ Bi-directional |
GoHighLevel |
Orchestration | Live | Agency+ | ⇄ Bi-directional |
Zapier / Make |
Orchestration | Live | Pro+ | → Outbound |
Slack |
Orchestration | Live | Pro+ | → Outbound |
Microsoft Teams |
Orchestration | Live | Pro+ | → Outbound |
Looker Studio |
Orchestration | Live | Agency+ | → Outbound |
REST API |
Orchestration | Live | Agency+ | ⇄ Bi-directional |
Newsletter ESPs 8 named: Mailchimp, ConvertKit, Beehiiv, Mailgun, Klaviyo, ActiveCampaign, HubSpot, GoHighLevel |
Orchestration | Documented | Pro (planned) | → Outbound (intended) |
SSO / SAML |
Infrastructure | Live | Agency / Enterprise | Authentication |
For teams running deeper engineering integrations — embedding AEO into custom dashboards, white-label reporting, agency client portals, programmatic monitoring at scale — the REST API exposes the entire AIVZ surface.
SDK code samples in JavaScript, Python, PHP, Ruby. API calls consume the same credit pool as dashboard usage. Rate limits are tier-dependent.
For tools that aren't in the directory — internal systems, vertical-specific tools, less common SaaS products — three universal paths cover most workflows.
AIVZ fires webhooks on every meaningful event: scan completion, score changes, crawl completion, credit thresholds, tier changes, alert creation. Any system that can receive a webhook can integrate — no named adapter required.
For tools that don't accept raw webhooks but are listed in Zapier or Make, the AIVZ connector becomes the bridge. Hundreds of downstream tools — including most common SaaS products — are reachable through the standard catalog.
For Enterprise-tier engagements with specific requirements not covered by webhooks or Zapier/Make — typically internal proprietary systems, regulated-environment integrations, or compliance-bounded workflows — AIVZ offers custom integration development.
These boundaries are deliberate. The integration scope is shaped by what's actually load-bearing for AEO outcomes — not by chasing logo count.
Scanning starts free, no signup required. Once your AI Visibility Score lands, integration setup happens inside your dashboard — OAuth flows for GSC, GA4, HubSpot, GoHighLevel, Looker Studio; webhook configuration for Slack, Teams, Zapier, Make. Most agencies have their core integrations connected within fifteen minutes.
