Client-ready exports
Reports
Generate weekly SEO wins, monthly performance, ranking movement, technical fixes, applied AI changes, backlinks, GBP, and WooCommerce SEO reports.
Set MICRO_SEO_BACKEND_URL to enable live session, billing, provider, site, and job state branches.
Exports depend on authenticated workspace scope, paid entitlement, connected site data, and verified applied changes.
Export weekly wins or monthly performanceClient summaries must cite provider metrics, approval history, execution status, backlinks, or verification results.
Attach evidence to every claimMissing providers, plugin disconnects, failed verification, and entitlement errors route users to setup/support actions.
Open setup/support checklistProduction UI states
Readiness states to preserve when live APIs are connected
These shared states document the user-facing contract for loading, empty, error, auth, provider, plan, sandbox, verification, and rollback paths before static scaffold screens are wired to live data.
Data lifecycle states
Every route should show users whether data is loading, absent, unavailable, or blocked by access.
Skeleton cards and tables while provider, workspace, or report data is syncing.
All dashboard and module routesFirst-run workspace guidance when no sites, providers, opportunities, approvals, backlinks, or reports exist.
Sites, integrations, opportunities, approvals, BacklinkBase, AI visibility, reportsRecoverable provider/API failures with retry copy and support-safe diagnostics.
All provider-backed routesBackend-core session, workspace membership, and role denial states before showing SEO data.
All workspace-scoped routesCommercial and provider states
Provider health, plan gates, sandbox boundaries, and entitlement limits must be visible before users can act.
Google, WordPress, GitHub, Vercel, DataForSEO, and BacklinkBase disconnect/expired/rate-limited states.
Integrations plus dependent module routesStarter/Pro/Agency gates for sites, reports, provider syncs, users, credits, and automation rules.
Sites, reports, BacklinkBase, approvals, integrationsBacklinkBase and destructive writes must identify sandbox versus production execution before approval.
BacklinkBase, approval queue, technical executionExecution safety states
Approval, verification, and rollback states should stay visible through the full SEO change lifecycle.
Applied changes that did not verify on preview/live HTML need retry and rollback affordances.
Approval queue, technical SEO, schema, WooCommerce SEO, reportsWordPress snapshots, GitHub PR reversions, and backlink audit trails must stay tied to an approved action.
Approval queue, WordPress plugin actions, reportsReports queue
Current work
Evidence
Reports should not hallucinate
Every claim should be backed by stored metrics, applied changes, provider status, or verification results.
Agency
Client portal ready
Reports are designed for agency-client workflows with approvals and audit history.