# Contractor Storm Page Proof Checklist

Use this before publishing a storm page, storm offer, storm landing page, or storm website proof section.

| Proof asset | Capture | Permission | Website placement |
| --- | --- | --- | --- |
| Before-and-after photos | Service type, city/service area, repair outcome, caption, date range | ___ | Service page / city page / landing page / gallery |
| Review proof | Customer quote, review source, storm problem, communication detail | ___ | Review block / reputation section / landing page |
| Testimonial proof | Customer story, problem, result, service, location cue | ___ | Testimonial section / project page / homepage trust |
| City proof | Neighborhood/city, storm context, service-area boundary | ___ | City page / local SEO section / landing page |
| Service proof | Roof leak, no-heat/no-cool, electrical hazard, water intrusion, inspection type | ___ | Service page / FAQ / quote form support |
| Insurance-process documentation | Photos, scope notes, documentation handoff, owner responsibilities | ___ | FAQ / landing page process / quote form context |

## Guardrails

- Do not imply insurance claim approval, coverage, payout, or guaranteed timeline.
- Webzaz fits website trust placement across service pages, city pages, landing pages, galleries, FAQs, quote forms, and homepage trust sections.
- LocalKit, QR/profile routes, emergency call routing, AI answering, scheduling, dispatch, estimate follow-up, and no-show controls stay separate.

## Owner growth route

- Collect the proof that makes storm pages trustworthy before the CTA asks for a lead.
- Match every storm-page claim to a photo, review, testimonial, city cue, service proof, permission note, or process boundary.
- Preserve `primary_source=storm_page_proof_checklist` through proof downloads, website placement maps, local proof routes, and Webzaz-fit conversion requests.
- Webzaz fits service page, city page, landing page, gallery, FAQ, quote-form, and homepage trust placement. Keep LocalKit/profile, QR cards, review/referral operations, emergency routing, AI answering, scheduling, dispatch, estimate follow-up, and no-show controls separate.