# Contractor Storm Proof Website Map

Use this map when storm proof belongs on website pages, not just QR cards or profile links. The goal is to place service-page storm proof, city-page storm proof, project-gallery proof, quote-form proof, review/testimonial proof, before-and-after proof, insurance-process proof, and Webzaz-fit website trust where homeowners decide whether to call or request a quote.

## 1. Service-page storm proof

- Service page:
- Best proof asset:
- Review/testimonial snippet:
- Before-and-after photo set:
- Insurance-process note:
- Quote CTA nearby:
- Owner:

## 2. City-page storm proof

- City/neighborhood:
- Real completed storm job:
- Local photo proof:
- Review mentioning city:
- City FAQ:
- Internal links needed:

## 3. Project-gallery proof

- Project title:
- Damage context:
- Repair outcome:
- Materials or equipment:
- Before photo:
- After photo:
- Permission status:
- Caption:

## 4. Quote-form proof

- Form location:
- Trust gap before submission:
- Proof to place nearby:
- Response-time expectation:
- Insurance-process clarity:
- Mobile CTA check:

## 5. Review/testimonial proof

- Review snippet:
- Approved testimonial:
- Job type:
- City:
- Customer permission:
- Best placement:

## 6. Website proof hierarchy

- Service page: answer whether the contractor handles this exact repair, emergency, inspection, or restoration job.
- City page: prove local relevance with real neighborhoods, completed jobs, reviews, and FAQs.
- Quote form: add one confidence cue near the form: approved photo, testimonial, insurance-process note, city proof, or callback expectation.

## 7. Product-fit routing

- Use Webzaz when storm proof needs to support service pages, city pages, galleries, FAQs, quote forms, thank-you routes, and website conversion paths.
- Use LocalKit or a lightweight profile route when the job is QR, referral, review, invoice, GBP, or social routing.
- Keep storm estimates, emergency calls, AI answering, scheduling, dispatch, and no-show controls in their own funnels.