Existing client
New client
Retrograde Rescue Audit
Promises already made
Forward Pre-Flight Audit
New client onboarding
Health Clinic Diagnostic Gate
Diagnose before amplify
Core Checks
GBP status · website anchor · DNS / email · schema · sameAs · social links
Healthy enough
Cleanup needed
ICU / Hospital case
Growth Activation
Surge, Rising Tide, Veracity Anchors
Cleanup Queue
GBP links · website anchor · schema basics
ICU / Hospital Case
Entity conflict · sameAs risk patterns · suspended assets
Operator Review
Basic repair verification
Remediation Scope Reset
Reframe engagement
Calculator Estimate
Time · cost · priority
Proposal / Expectation Reset
New scope before work begins
Remediation Work
Execute repair plan
Growth Activation
Surge · Rising Tide · Veracity Anchors
Reporting / Proof / Forward Propagation
Client-facing evidence of progress
Health Clinic is the gate between promise and propagation.
Before we amplify, we diagnose.
Operating rules
If the client is already sold →
Run Retrograde Health Clinic Audit before explaining performance failure. The diagnosis reframes the conversation from "you're not delivering" to "here's what was wrong underneath."
If the client is new →
Run Forward Pre-Flight Audit before making growth promises. If the entity is sick, the offer changes before it hardens.
If Health Clinic passes →
Proceed into Growth Activation. Surge, Rising Tide, Veracity Anchors, and reporting.
If Health Clinic flags cleanup →
Repair before amplification. GBP social links, schema basics, website anchor. Operator verifies, then proceed to growth.
If Health Clinic flags ICU conditions →
Reset scope, price, timeline, and expectations. Entity conflict, sameAs risk patterns, suspended assets — these change the engagement, not just the task list. Calculator estimates remediation cost before new proposal is issued.
ICU triggers
Suspended or broken assets linked from GBP
YouTube channel suspended, social links pointing to dead or wrong profiles. Every linked property must be alive and belong to this entity.
Schema sameAs risk patterns
Wikipedia links to local destinations, excessive sameAs entries, 301 redirect chains. Three severity levels: Level 1 (too many links), Level 2 (gray hat — Wikipedia to local), Level 3 (redirect chains to unrelated destinations).
Multi-entity conflict
More than one GBP for the same practitioner with conflicting NAP or categories. Multiple Organization/LocalBusiness nodes in schema with different names. This changes the price of the engagement.
Agreement check
1. Retrograde clients
Does this flow match how you want to handle existing clients going forward? Should every existing client get a Health Clinic audit before further growth work, or only flagged accounts?
2. Pre-flight gate for new clients
Are you comfortable making the pre-flight audit mandatory before growth promises are made? This means the Health Clinic runs before Surge, Rising Tide, or reporting commitments.
3. ICU scope resets
When Health Clinic flags ICU-level conditions, should that trigger a formal scope and price reset with the client — or handle case-by-case at operator discretion?