WordPress fully Live with native execution. Five surfaces — Shopify, Wix, Webflow, BigCommerce, Headless — in Beta. Squarespace on the roadmap. Marketplaces documented. Every adapter's status disclosed openly so you know exactly what's operational before you commit.
AEO platform claims are routinely overstated across the industry. AIVZ uses a four-status taxonomy with strict definitions — published in our Integrations canon, applied across every customer-facing surface. The status of every adapter is disclosed in marketing pages, sales decks, contracts, and the dashboard itself. No surface drops the disclosure.
The adapter is shipped, fully operational, and supports the full canonical execution scope. "We Do It" claims in marketing are permitted without qualification.
Shipped and operational for a documented subset of the canonical execution scope. Claims must surface the Beta status explicitly.
Planned and prioritized but not yet shipped. Recommendations surface via manual-implementation path; native execution does not yet operate.
Execution framework documented; native adapter has not yet been built. Recommendations surface; execution requires manual implementation.
Agencies and enterprises evaluating AEO tools need to know whether an adapter actually runs or whether the marketing page is forward-looking. The status taxonomy makes the difference visible at evaluation time, not after contracts are signed.
When AIVZ says WordPress is Live, the disclosure discipline on every other status is what makes that "Live" claim credible. Without the discipline, every claim becomes ambiguous; with the discipline, every claim is exact.
The status taxonomy is also a build-management tool. "Documented-but-Unbuilt" surfaces gaps between what we've published and what we've shipped — internal pressure to close those gaps stays visible to the team.
The full status matrix. Each row surfaces what AIVZ executes natively on that platform — the canonical "We Do It" disclosure. Statuses are accurate as of May 1, 2026; the Integrations canon is the authoritative source.
| Platform | Status | Native Execution Scope |
|---|---|---|
WordPress |
Live | Schema markup (Organization, Article, FAQPage, Speakable, Person, HowTo, Product); meta descriptions; FAQ blocks; summary blocks; llms.txt manifests; robots.txt updates; sitemap optimization; structured data validation; AEO score widgets; content rewrites for L3 factors; per-page recommendations panel embedded in the editor. Full canonical scope. |
Shopify |
Beta | Product schema; collection schema; FAQ blocks for product detail pages; meta description optimization; structured data validation. Subset of canonical scope; deeper coverage on roadmap. |
Wix |
Beta | Schema markup; meta descriptions; structured content blocks via the Wix Studio integration. Subset of canonical scope. |
Webflow |
Beta | Schema markup via embedded JSON-LD; FAQ blocks via component substitution; meta description optimization. Subset of canonical scope. |
BigCommerce |
Beta | Product/category schema; meta description optimization; FAQ blocks for product detail pages. Subset of canonical scope. |
Headless / Custom |
Beta | Via MCP server + CLI integration; bring-your-own-stack execution path. Output is structured-data updates, content recommendations, and orchestration calls — applied by the consuming application. |
Squarespace |
Roadmap | Native adapter planned; not yet shipped. Recommendations available through manual-implementation path. |
Marketplaces |
Documented | Marketplace-listing optimization framework documented in canon; native adapter build pending. Recommendations surface; execution requires manual implementation. |
Regardless of native execution scope, every connected platform supports full 93-factor scanning, the composite AI Visibility Score, three-layer Stack breakdown, six per-platform readiness scores, and the recommendations queue. The differentiator across the matrix is direct-execute capability.
WordPress is the flagship — the surface where AIVZ has full canonical execution scope, the longest adapter history, and the deepest editor integration. The plugin is published, fully operational, and runs the full set of native fix capabilities.
Five surfaces are currently in Beta — operational for documented scope; deeper coverage in active development. Each Beta surface is suitable for current use within its scope; users should expect feature additions over time.
Product schema, collection schema, FAQ blocks for product detail pages, meta description optimization, structured data validation. Custom theme integration available; checkout-flow execution is out of scope.
Schema markup, meta descriptions, structured content blocks via the Wix Studio integration. Suitable for content-driven Wix sites; commerce-heavy Wix Stores get a subset of capability. Wix Velo integration available.
Schema markup via embedded JSON-LD, FAQ blocks via component substitution, meta description optimization. Suitable for Webflow CMS-driven sites; collection-list optimization works through symbol substitution.
Product/category schema, meta description optimization, FAQ blocks for product detail pages. Suitable for BigCommerce storefronts of all sizes; large catalog operations supported through batch scanning.
For sites running on headless CMS architectures (Sanity, Contentful, Strapi, Storyblok, Prismic) or fully custom stacks. AIVZ integrates via MCP server and CLI. Bring-your-own-stack execution path.
The adapter is operational for the documented scope; rely on it for client work. Feature additions ship periodically. Coverage gaps surface as "generate instructions" recommendations rather than direct-execute fixes.
The eight platforms above cover the majority of current web publishing surfaces. For sites running on stacks not represented in the matrix, AIVZ supports two paths: the Headless / Custom Beta adapter (works for most cases) and Enterprise-tier custom adapter development.
The universal path. It works for headless CMS architectures (Sanity, Contentful, Strapi, Storyblok, Prismic, Hygraph), fully custom stacks, hybrid architectures, and API-first content workflows.
For Enterprise-tier engagements with specific platform requirements not covered by the matrix or the Headless / Custom adapter, AIVZ offers custom adapter development as part of the Enterprise tier scope — appropriate when the platform has scale-specific requirements, platform-specific compliance constraints, or custom rendering pipelines.
Scanning, scoring, and recommendations work across every platform AIVZ supports — including platforms where native execution isn't shipped yet. If your platform supports native execution, fixes are direct-execute. If not, you get generate-instructions recommendations that work everywhere.
