Vexal Documentation by WileyLabs

What is Vexal?

Stable

Applies to: Vexal platform, WileyLabs product ecosystem

Introduced: Platform concept (SmartBlocks 1.0.700+)

Updated: Documentation v1

Vexal is an AI Visibility Platform—machine-understanding infrastructure that helps WordPress sites become clearer to search engines, AI crawlers, and answer engines.

Summary

Vexal combines structured content signals (FAQ, JSON-LD schema, entity clarity), telemetry (crawler and agent activity), governed recommendations (evidence-backed, explainable actions), and operational tooling (visibility ledger, recovery, campaigns). It is built and distributed by WileyLabs; the primary WordPress implementation is Vexal SmartBlocks.

Use cases

  • Improve AI and search visibility without replacing your theme or page builder
  • Run governed optimization campaigns with audit trails and rollback
  • Track machine-facing changes via the Visibility Ledger
  • Measure crawler/agent activity and page readiness over time

How it works

Vexal sits as an intelligence layer on WordPress: it reads post content and meta, scores readiness, proposes recommendations through a shared registry, and applies safe changes only through governed paths with snapshots and ledger events. Display (theme) and intelligence (Vexal) stay separated.

Inputs

  • WordPress posts, pages, and post meta
  • Plugin settings and integration credentials (SearchAsist, GSC, etc.)
  • Crawler/agent telemetry and external visibility signals

Outputs

  • Structured schema and visible FAQ content
  • Admin dashboards, reports, and campaign compare views
  • Ledger events, snapshots, and recommendation trails

Admin UI location

WordPress admin: Vexal → Vexal AI Visibility hub (SmartBlocks). This documentation site has no admin UI—it is read-only reference material.

Crawler families, agent prompts, page context signals—see Telemetry Engine.

Platform-wide events are logged per product; SmartBlocks uses smartblocks_visibility_log_event() and campaign ledger helpers.

Security notes

Governed apply requires capability checks and nonces. Public docs must not contain secrets, tokens, or customer PII.

See also