Site operations
Sites
Connect and manage WordPress, WooCommerce, headless frontend, GitHub, Vercel, and Google data for every SEO property.
Set MICRO_SEO_BACKEND_URL to enable live session, billing, provider, site, and job state branches.
Backend-core session context is required before site, opportunity, approval, or report data is shown.
Verify /api/seo/v1/onboardingAudioVideoNation has CMS data online, but GitHub execution mode still needs a connected repository grant.
Connect GitHub or continue plugin-onlyRecommendation generation, report exports, and backlink previews require micro_seo:paid entitlement.
Keep upgrade CTA visible for free usersProduction 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, reportsSites queue
Current work
Connection model
One site, many executors
Each site stores CMS, frontend, repo, deployment, and provider status so recommendations can route safely.
Headless support
Verify rendered output
Headless WordPress and Astro sites are checked from the public frontend HTML, not only from CMS fields.