The Global Fix Plan: From 200 Issues to a Prioritized Roadmap
SiteNexis audits surface dozens or hundreds of findings across twelve modules. The Global Fix Plan aggregates every issue into a single P0/P1/P2 queue, maps cross-module dependencies, and estimates total effort — so you know what to fix first and why.
A typical SiteNexis audit on a mid-size domain surfaces 80–200 individual findings across twelve intelligence modules. SEO issues, schema gaps, entity inconsistencies, trust signals, retrieval failures, surface blockers. Each module reports its own findings. Without a unification layer, you face a fragmented list with no guidance on sequencing or relative priority. The Global Fix Plan solves this by pulling every issue — from the Issues table and from every v3 sub-report — into a single ranked queue.
What Gets Aggregated
The Fix Plan engine pulls from six sources: the core Issues table (SEO, schema, content, performance, entity, citation, semantic trust), Machine Trust sub-report trust issues, Temporal Authority sub-report temporal issues, Retrieval Simulation failure records, Recommendation Surface coverage gaps, and Synthetic Entity detected patterns. Every source normalizes into the same FixPlanItem shape — with priority, module, severity, page URL, message, recommendation, impact scores, and effort estimate.
How Priority is Assigned
Priority is a composite score: severity (critical=10, warning=5, info=2) × 3, plus module weight (SEO=8, entity=7, schema=7, AI visibility=7, down to synthetic entity=3) × 2, plus total impact score (SEO impact + AI visibility impact + trust impact, each 0–9). Critical issues on high-weight modules score P0. Warning-level issues on mid-weight modules land at P1. Info-level findings on lower-weight modules become P2. Every critical-severity issue is always at least P0 regardless of module weight.
- 1P0 — Fix immediately. Critical severity or composite score ≥ 55. Blocks AI visibility or trust formation.
- 2P1 — Fix this sprint. Warning severity or composite score ≥ 30. Meaningful impact on scores.
- 3P2 — Fix when able. Informational findings or lower-weight module issues.
Dependency Chains
Not all fixes can be applied in any order. The Fix Plan maps six cross-module dependency rules: schema fixes must precede trust score improvements (schema data feeds the trust alignment calculation), H1/title fixes must precede AI extractability improvements, entity fixes must precede citation probability improvements, crawlability issues block everything downstream, content quality must improve before recommendation surfaces expand, and semantic trust issues must resolve before temporal authority stabilizes.
▲If you have critical crawlability issues (noindex directives on key pages, robots.txt blocking important sections), these create dependencies for every other fix. The AI system cannot analyze content it cannot access. Fix crawlability first — it appears as a P0 dependency chain in the Fix Plan.
Effort Estimation
Every fix item includes an effort classification: low (0.5h — issues with generated fix code, or simple tag additions like missing H1/meta), medium (2h — structural changes requiring template or content edits), or high (6h — content creation, entity coverage expansion, contradiction resolution). The Fix Plan sums estimated effort hours across all items, giving you a total remediation time estimate before you begin.
Impact Scoring by Dimension
Each fix item carries three impact scores: SEO impact (0–9), AI Visibility impact (0–9), and Trust impact (0–9). Schema issues score across all three dimensions. SEO module issues score primarily on SEO impact. Machine Trust issues score primarily on Trust impact. The Fix Plan dashboard shows these impact bars per item, letting you filter and prioritize by the dimension you care most about improving.
Run a full audit and see your Fix Plan in one click.
Generate your Fix Plan