Learn how the scan funnel works, how the connector pairs, how approvals are handled, and what the audit trail captures when WordpexAI touches a live site.
The user journey is intentionally guided and low-friction.
Read-only first, then paired, then governed. That order keeps the product trustworthy.
These are the main objects and controls you’ll see throughout the app.
A temporary onboarding record that tracks the form submission, pairing code, waiting state, and readiness to hand off to the dashboard.
The WordPress plugin installation that sends signed heartbeats and receives signed action requests.
The rules layer that decides whether an action is allowed, requires approval, or needs rollback readiness.
Append-only evidence of critical transitions, pairing, approvals, action proposals, and execution results.
Each step should be understandable on its own, but connected to the next step.
The website captures the site URL, email, and contact details and creates a scan session.
The WordPress plugin exchanges the pairing code for connector credentials and marks the site as connected.
Heartbeats and inventories feed the control plane with site state and risk signals.
Approvals, rollback checks, and audit records keep every action explainable and reversible.
The docs should preempt the same buying questions people ask in demos.
No. The system recommends by default and only executes when policy and permissions allow it.
Both. Free Inspect is built for a single site flow, while agencies and teams can grow into multi-site operations.
Approvals are explicit queue items tied to a proposal, a risk level, and the required role.
Rollback readiness is part of the recommendation and execution flow, not a separate afterthought.
Run the free scan and let the connector flow tell the rest of the story.