Checking authenticated workspace, billing entitlement, connected providers, sites, and execution jobs.
Checking authenticated workspace, billing entitlement, connected providers, sites, and execution jobs.
Human-gated execution
Review, approve, reject, apply, verify, and roll back SEO recommendations before production changes happen.
Set MICRO_SEO_BACKEND_URL to enable live session, billing, provider, site, and job state branches.
Execution-capable approvals remain in mapping-required state until backend-core can map the Micro SEO site to a ProjectOS project.
Pending writes stay in review until a user explicitly approves, rejects, or requests changes.
Review low-risk recommendations firstLive writes without approval are disabled. Plugin changes create snapshots and PR changes verify previews.
Inspect write contract before applyApplied CMS changes are snapshot-backed; GitHub PR changes remain reviewable and revertible in the repo.
Verify after every applyBackend-core broker
Execution-capable approvals create a backend-core ecosystem job. Micro SEO stores the returned ecosystem_job_id and waits for ProjectOS lifecycle status instead of marking execution complete inline.
Production UI states
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.
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 routesProvider 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 executionApproval, 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, reportsApproval Queue queue
Safety
Slug, canonical, robots, pricing, checkout, and backlink purchases always require approval.
Rollback
Plugin-applied content changes create snapshots so the site can roll back safely.