Surge V3.6 Framework — Practitioner Reference
Common Surge Errors
Purpose
This artifact exists to show where practitioners commonly fail when implementing Surge — so mistakes can be prevented before they compound.
Why These Errors Matter
Surge creates corroboration networks. Errors don't stay local — they propagate across nodes, formats, and platforms. A mistake in Phase 1 becomes a systemic problem by Phase 6. Prevention beats correction.
Foundation Failures
AP-01
Publishing Before Entity Fact Sheet Lock
The Trap
Starting content production before canonical facts are verified and approved.
Why It Happens
Pressure to show progress. The Entity Fact Sheet feels like "paperwork" blocking real work.
Consequence
Contradictions propagate across your corroboration network. Fixing requires retracting and republishing across all nodes.
Phase
Phase 0.5 → Phase 3
Severity
CRITICAL
AP-02
Trusting AI Drafts Without Verification
The Trap
Publishing AI-generated content without checking against the Entity Fact Sheet.
Why It Happens
AI output sounds confident and plausible. Verification feels redundant. Speed pressure.
Consequence
Hallucinated facts become "corroborated" across your network. You've built machine confidence in something false.
Phase
Phase 3, Phase 5
Severity
CRITICAL
AP-03
No Baseline Screenshots
The Trap
Starting work without capturing baseline visibility state across all surfaces.
Why It Happens
Feels like busy work. "We know they're not ranking." Eager to start producing.
Consequence
No proof of progress. Cannot demonstrate ROI. Client disputes become unresolvable.
Phase
Phase 0
Severity
HIGH
Coverage Failures
AP-04
Volume Over Coverage
The Trap
Producing many assets of one dataset type (usually Correlative) while ignoring other types.
Why It Happens
Blog posts are familiar. Collaborative and Amplifying require outreach. Easier to stay in comfort zone.
Consequence
Unbalanced coverage. Missing third-party validation (Collaborative) or authority inheritance (Amplifying) caps entity recognition.
Phase
Phase 2, Phase 3
Severity
HIGH
AP-05
Single-Surface Optimization
The Trap
Measuring only web rankings while ignoring Maps, Video, Images, Audio, and AI features.
Why It Happens
Traditional SEO habits. Web rankings are familiar. Other surfaces feel like "extras."
Consequence
Incomplete visibility picture. Misses where actual users discover the entity. Parallel dataset gaps undetected.
Phase
Phase 0, Phase 10
Severity
HIGH
AP-06
Inconsistent Asset Naming
The Trap
Asset Pack components (page, video, audio, GBP post) use different titles/phrasing for the same intent.
Why It Happens
Different team members create different assets. No template enforcement. "Creative variation."
Consequence
Breaks the corroboration signal. Machine sees different titles as different topics, not reinforcement of same intent.
Phase
Phase 3
Severity
HIGH
Distribution Failures
AP-07
Random Distribution (Ignoring Trust Tiers)
The Trap
Pursuing S3+ platforms (easy to access) while ignoring S1 hubs (harder but higher value).
Why It Happens
S1 hubs require outreach or earned placement. S3+ platforms accept submissions immediately. Activity feels like progress.
Consequence
Low trust inheritance despite high activity. Corroboration network lacks authority anchors. Citation eligibility stays low.
Phase
Phase 6
Severity
HIGH
AP-08
Tertiary Nodes Publishing Unreviewed Content
The Trap
Automation flows publishing to tertiary nodes without human QA gate.
Why It Happens
"It's just RSS/syndication." Tertiary feels low-stakes. Automation is set-and-forget.
Consequence
Errors amplify at scale. Tertiary nodes propagate wrong information faster than you can correct it.
Phase
Phase 7, Phase 8
Severity
CRITICAL
AP-09
Broken Canonical Link Chains
The Trap
Secondary/tertiary nodes link to each other or to orphan pages instead of back to primary nodes.
Why It Happens
Copy-paste errors. URL changes without redirect. "Any link is a link."
Consequence
Trust signal doesn't flow back to canonical source. Corroboration network is fragmented, not reinforcing.
Phase
Phase 5, Phase 7
Severity
MODERATE
Compliance Failures
AP-10
Schema Invention
The Trap
Adding structured data for reviews, credentials, pricing, or awards that don't exist on the visible page.
Why It Happens
"Richer schema = better rankings." Wanting to match competitors' rich results. AI generates plausible-sounding schema.
Consequence
Google penalty risk. Structured data must represent visible content. Invented schema is spam.
Phase
Phase 4
Severity
CRITICAL
AP-11
NAP Inconsistency (Local)
The Trap
Name, Address, or Phone formatted differently across citations (Suite vs. Ste., LLC vs. no LLC, etc.).
Why It Happens
Different team members submit to different directories. No canonical format enforced. "Close enough."
Consequence
Breaks entity recognition for local. Machine sees variations as different businesses, not corroboration of one.
Phase
Phase 0.5, Phase 5
Severity
HIGH
Scaling Failures
AP-12
Scale Before Proof
The Trap
Expanding to more intent packs or geos before pilot intent packs reach Visibility Level 2+ and generate leads.
Why It Happens
Client pressure for volume. "More content = more chances." Impatience with proof cycle.
Consequence
Scaling a broken approach. If the pilot doesn't work, doing 10x of it won't help. Wastes resources and delays correction.
Phase
Phase 9, Phase 10
Severity
HIGH
AP-13
Opinion-Based Scaling
The Trap
Deciding what to scale next based on gut feel, client preference, or "what competitors are doing" instead of Phase 10 data.
Why It Happens
Data takes time to analyze. Stakeholders have opinions. "We know our business."
Consequence
Resources allocated to wrong priorities. Winning intents under-invested. Losing intents over-invested.
Phase
Phase 10
Severity
MODERATE
AP-14
Phase Skipping
The Trap
Jumping to later phases without completing outputs and passing QA gates for earlier phases.
Why It Happens
"We already know that." Impatience. Some phases feel like overhead. Stakeholder pressure to show activity.
Consequence
Missing dependencies surface later as blockers. Work must be redone. Creates compounding errors downstream.
Phase
Any transition
Severity
HIGH
Quick Reference
| Code | Anti-Pattern | Phase | Severity |
|---|---|---|---|
| AP-01 | Publishing Before Entity Fact Sheet Lock | 0.5 → 3 | Critical |
| AP-02 | Trusting AI Drafts Without Verification | 3, 5 | Critical |
| AP-03 | No Baseline Screenshots | 0 | High |
| AP-04 | Volume Over Coverage | 2, 3 | High |
| AP-05 | Single-Surface Optimization | 0, 10 | High |
| AP-06 | Inconsistent Asset Naming | 3 | High |
| AP-07 | Random Distribution | 6 | High |
| AP-08 | Tertiary Nodes Unreviewed | 7, 8 | Critical |
| AP-09 | Broken Canonical Link Chains | 5, 7 | Moderate |
| AP-10 | Schema Invention | 4 | Critical |
| AP-11 | NAP Inconsistency | 0.5, 5 | High |
| AP-12 | Scale Before Proof | 9, 10 | High |
| AP-13 | Opinion-Based Scaling | 10 | Moderate |
| AP-14 | Phase Skipping | Any | High |
Pre-Scale Self-Check
Before expanding to new intent packs or geos, verify:
Entity Fact Sheet is locked and approved
Baseline screenshots exist for all target surfaces
All AI-generated content verified against Fact Sheet
Dataset coverage is balanced (not just Correlative)
Trust Neighborhood mapped; S1 hubs identified
All secondary/tertiary nodes link back to canonical primaries
Schema represents visible content only
Pilot intent packs at Visibility Level 2+ with leads rising