# Contractor Storm Trust Badge Placement Worksheet

Use this worksheet when a storm page has the right CTA but the homeowner still needs credibility before submitting.

## Badge placement fields
- Storm CTA: emergency help, inspection request, quote form, documentation help, callback, or follow-up.
- Trust gap: license, insurance, local crew, storm documentation, review proof, before-and-after proof, city proof, service proof, or proof owner.
- Badge to place: one badge beside the CTA, not a generic badge pile.
- Placement: hero, service card, quote form, proof block, city page, service page, gallery, or thank-you page.
- Source attribution: preserve source, primary_source, search query, CTA route, badge type, proof owner, city, trade, urgency, and thank-you expectation.

## Placement checks
1. Put license proof beside high-risk repair, electrical, restoration, and inspection CTAs.
2. Put insurance proof beside liability, water intrusion, roof leak, emergency repair, and documentation CTAs.
3. Put local crew or city proof beside city-page and same-day storm-response CTAs.
4. Put review or before-and-after proof beside quote and inspection CTAs where social proof reduces form hesitation.
5. Route Webzaz-fit website fixes only when the bottleneck is trust-badge placement, proof hierarchy, CTA copy, storm landing page layout, quote-form confidence, service-page proof, city-page proof, or thank-you structure.

## Webzaz-fit website fixes
Webzaz fits when contractors need better website trust-badge placement, storm landing page layout, proof hierarchy, CTA copy, quote-form confidence, service-page proof, city-page proof, or source-preserved thank-you routing. Keep LocalKit, GBP/profile routes, review links, referral workflows, CRM, dispatch, scheduling, AI answering, estimate follow-up, and no-show workflows separate.


## Source-preserved route checklist
- Keep `primary_source=storm_trust_badge_placement` on download forms, resource cards, contextual article links, no-results recovery, and thank-you recommendations.
- Preserve source, search query, CTA route, badge type, proof owner, city, trade, urgency, and thank-you expectation in the handoff notes.
- Keep storm CTA proof badge work separate from LocalKit profile links, review asks, referral workflows, CRM, dispatch, scheduling, AI answering, estimate follow-up, and no-show controls unless the reader explicitly needs that adjacent workflow.
- Do not promise carrier decisions, claim payouts, storm response timelines, or certain results; use the badge to support confidence, not to make legal or coverage claims.

## Booked-job proof route QA — 2026-05-10 04:00 ET

- Match license, insurance, local crew, review, city, before-and-after, or storm documentation proof to the exact emergency, inspection, quote, callback, or documentation CTA.
- Preserve badge type, proof owner, CTA route, city, trade, urgency, source, search query, and thank-you expectation after submit.
- Webzaz fits website proof hierarchy, CTA copy, trust-badge placement, storm landing pages, forms, city/service proof, and source-preserved thank-you routing only.
- Keep LocalKit/profile links, review/referral asks, CRM, dispatch, scheduling, AI answering, no-show controls, estimate follow-up, and insurance claim handling separate. No exact Webzaz pricing.