Checking authenticated workspace, billing entitlement, connected providers, sites, and execution jobs.
Checking authenticated workspace, billing entitlement, connected providers, sites, and execution jobs.
Organic execution command center
Detect SEO, content, ecommerce, local, technical, AI visibility, and backlink opportunities, then route each fix to the safe executor.
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/onboardingOnboarding confirms at least one workspace-scoped site is available for scans and execution routing.
Continue to provider readinessRecommendation generation, report exports, and backlink previews remain gated until backend-core reports a paid Micro SEO entitlement.
Upgrade to Micro SEO Pro2 providers need backend-core OAuth setup before complete launch readiness.
/integrations/google-search-console/connectBackend-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.
Recommendation generation, report exports, and backlink previews require micro_seo:paid entitlement.
Keep upgrade CTA visible for free usersPending 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 applyExports 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
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, reportsOpportunity engine
Approval Queue
Low-risk metadata can be bulk approved. High-risk canonical, robots, pricing, checkout, and backlink purchase actions stay explicitly approval-gated.
Rankings
wordpress_plugin
Safe CMS updates for titles, meta descriptions, WooCommerce copy, schema fields, snapshots, and rollback.
github_pr
Developer PR mode for Astro, Next.js, schema rendering, sitemap, canonical, and template fixes.
hybrid_operator
Plugin stores clean SEO fields while GitHub PRs update headless frontend rendering and verification.
Launch flow readiness
The dashboard keeps the launch path explicit: authenticate with backend-core, load /api/seo/v1/onboarding, connect the first site, then unlock paid execution flows.
ProjectOS execution mapping
GitHub PR and hybrid recommendations create a ProjectOS ticket proposal before work starts.
Frontend execution CTAs should map recommendation id, site id, workspace id, execution mode, and risk level into the ProjectOS ticket handoff.
Map to ProjectOS ticketCanonical, robots, pricing, checkout, and backlink purchases stay in human QA until approved.
ProjectOS automation can draft PR work, but approval and merge remain human-gated for these records.
Send to human QAApplied recommendations must attach preview/live checks before client reporting claims are unlocked.
Report export blocked until paid entitlement, connected site data, and verification evidence are present.
Review evidenceAI / AEO Visibility
Generate /llms.txt, /llms-full.txt, and AI Markdown files for products, services, FAQs, policies, and locations.
BacklinkBase
Marketplace browsing, AI article drafts, target site metrics, sandbox previews, and explicit approval before task submission.
Provider graph
not_configured · backend_core_oauth_placeholder
OAuth credentials are not stored by Micro SEO; connect through backend-core.
Connect Search Consolenot_configured · backend_core_oauth_placeholder
OAuth credentials are not stored by Micro SEO; connect through backend-core.
Connect GA4