Updated continuously. Beta-to-Live graduations, new methodology factors, integration releases, fix packs, and the occasional honest "this didn't ship — here's why."
The AIVZ-WordPress execution adapter is now generally available through the WordPress.org plugin directory. WordPress sites are the first platform on AIVZ where Diagnose, Orchestrate, and Execute all land in production.
What's in v1.0:
The Shopify execution adapter passed validation and is now Live for all Pro, Agency, and Enterprise tier users on Shopify storefronts.
What changed: native Liquid template injection,
automatic Product schema enrichment with gtin /
aggregateRating / priceValidUntil, and FAQ
block surfacing on PDPs without theme code modification.
What stays Beta: Shopify Hydrogen / headless storefronts use the MCP/CLI path, which remains in active Beta.
Three factors moved from Indirect-Correlated to Strongly Inferred based on six months of citation observation data:
Two factors graduated from Emerging-Experimental to Indirect-Correlated:
llms.txt presencerobots.txtNo factor weights changed in this update. Confidence labels affect how AIVZ surfaces fix priority but do not affect score math. Read the full Validation Methodology →
The Webflow execution adapter is now in Beta for Pro and Agency tier customers. Diagnose runs at full fidelity; Orchestrate produces ranked fix recommendations; Execute writes Webflow CMS schema fields and meta tags via the Webflow Data API.
What's not yet covered in this Beta: custom-component schema injection inside Designer-only sites, and Webflow Localization multi-locale propagation. Both are scoped for the v2.5 release.
The Squarespace adapter on the public roadmap was scheduled for Q4 shipping. It's not going to make Q4. Squarespace's editor lock-in makes the additive (never-overwriting) execution path harder than on Shopify or BigCommerce; we're rebuilding the approach to fit their template constraints.
For Squarespace customers today: Diagnose and Orchestrate work fully. Execute requires manual application of fix recommendations through Squarespace's editor — not ideal, but the gap will close, just later than committed.
We're sorry for the slip. New target: Q2 next year.
Schema generation now respects existing storefront markup and never
duplicates Product JSON-LD. Previous v1 emitter
occasionally produced redundant blocks alongside theme-emitted
markup; resolved.
Coverage expanded to include Offer.priceValidUntil,
Offer.itemCondition, and
aggregateRating.reviewCount propagation from native
BigCommerce review data.
Perplexity citation log was capped at the most recent 50 entries on the dashboard. Resolved — full citation history (90 days for Pro, 12 months for Agency, custom for Enterprise) now paginates correctly.
The 11 Citation Core factors — the subset of the 93-factor taxonomy with the highest observed correlation to AI citation events — now render as a dedicated panel in scanner output. Previously bundled into the per-layer breakdown; now isolated as a top-of-report signal for fast-triage workflows.
Free-tier scans surface the Citation Core 11 panel in read-only form. Pro+ tiers get fix recommendations attached to each factor.
For headless and custom-stack sites without a native AIVZ adapter, the MCP/CLI delegation path is now in Beta. AIVZ produces ranked fix recommendations as machine-readable instructions; your build pipeline (or an MCP-compatible agent) executes them.
Supported MCP runtimes at Beta: Claude Code, Cursor, and the AIVZ CLI itself. Support for additional MCP-compatible clients tracked at /integrations.
Agency tier customers now operate AIVZ across an unlimited number of client domains under a single white-label brand. Features include per-client scoring isolation, scheduled per-engagement reporting, client-side viewer portals with custom domain support, and programmatic API access to all 198 REST endpoints.
Approved Agency tier customers are onboarded with a dedicated Account Manager. Apply at /agency/apply.
Per-adapter Live / Beta / Roadmap status across every supported execution surface.
See platformsIf you're tracking factor-confidence changes, the methodology hub is the canonical source.
Read methodologyDevelopers tracking REST, MCP, and webhook surface changes — separate timeline at /developers/api/changelog.