# Clinic Proof Refresh System

## Why this exists
Most clinics do not need more generic marketing. They need a repeatable way to keep trust current. Reviews, provider credibility, care-process proof, and local visit cues all decay when no one owns them.

## Proof Source Map
Track proof in five lanes:
- Provider credibility: bios, training, certifications, speaking, media, association memberships
- Patient confidence: reviews, testimonials, frequently praised staff/process moments
- Treatment credibility: before-and-after patterns, outcomes framing, care explanations
- Operational trust: parking, paperwork, visit flow, wait-time framing, after-hours instructions
- Local proof: photos, community presence, location freshness, service-area accuracy

## Monthly Refresh Workflow
Week 1:
- Pull recent reviews and categorize them by trust signal.
- Identify one strong patient-language phrase worth reusing.

Week 2:
- Refresh one provider or treatment proof block.
- Update one location or visit-expectations section.

Week 3:
- Add one new proof element to a high-intent page.
- Retire one stale proof element that no longer feels current.

Week 4:
- Review which proof elements influenced bookings, consults, or higher-confidence calls.

## Surface Routing
Route proof intentionally:
- Service pages: treatment credibility and provider trust
- Location pages: arrival confidence and local proof
- FAQ blocks: fear reduction and process clarity
- Consult follow-up: social proof plus next-step confidence
- Ad and social snippets: short, credible trust phrases drawn from stronger source material

## AI and Local Surface Sync
Keep the same proof facts synchronized across:
- Google Business Profile descriptions, photos, and review-response themes
- location pages and service pages
- FAQ blocks and patient-facing answer hubs
- AI-readable summaries, structured data, and downloadable guides

If one surface says the clinic is current, calm, and well organized while another looks stale or contradictory, the weaker surface quietly undermines trust everywhere else.

## QA Checklist
- Is the proof current enough to feel believable?
- Does it reduce a specific fear?
- Is it visible at the decision moment where patients hesitate?
- Does it sound like this clinic, or like generic healthcare copy?
- Can the same proof support search, maps, and AI-readable surfaces cleanly?

## Operating Notes
- Review freshness beats volume.
- Proof should explain, not merely decorate.
- Stale proof quietly trains patients to distrust the rest of the page.