Launch polish

Fire and Storm Restoration Launch Polish Checklist

Final visual, content, and safety QA checks for the public Fire and Storm Restoration launch site files.

Mobile polishContact QANo fake proof

Visual and mobile polish checks

Use this checklist after upload and cache clearing to confirm the public experience is readable, clear, and focused on safe restoration lead routing.

  • Mobile header readability is clean and the primary phone path is visible.
  • Sticky phone button is present on mobile and points to 1(464) 274-1476.
  • Footer contact block shows phone, email, business hours, and the Cicero address.
  • Checklist pages print cleanly without external fonts or libraries.
  • Mobile header QA page documents logo visibility, header phone link, sticky call behavior, tap target sizes, focus states, and footer contact visibility.

Content and conversion checks

Confirm that local pages, contact flow, privacy links, disclaimers, and launch routes stay connected without sending visitors to unsafe or unsupported workflows.

  • Local page links route to city/service-area pages and contact paths.
  • Contact form redirects to /service-request-confirmation/ without exposing private message content in the URL.
  • Privacy policy and site safety disclaimers are linked from footer and relevant support pages.
  • Google Business Profile asset readiness and approved-photo intake paths are visible to the operator.
  • GBP asset readiness is checked through the Google Business Profile assets page.

Proof and guardrail checks

The site should remain useful and credible while waiting for real proof assets. Do not add fake reviews, fake project photos, fake GBP links, unsupported credentials, or insurance outcome guarantees.

  • Gallery placeholder behavior remains public-safe when no approved photos exist.
  • Review link guard behavior prevents fake buttons, star ratings, review counts, testimonials, and Review schema.
  • No fake proof is visible anywhere on the public site.
  • No public upload form, external analytics, CRM webhook, map embed, or secret-bearing approved settings is present.

v2.6.0 launch evidence handoff

Final polish includes checking the deployment proof checklist and launch evidence report links.

  • Launch evidence report remains a preparation record until live deployment is manually verified.
  • Operator sign-off must happen outside the public form workflow.
  • Deployment proof checks should be recorded without files, secrets, uploads, analytics scripts, webhooks, or runtime PDF generation.

v2.7.0 route audit handoff

The v2.7.0 site files adds manual post-deployment route audit and static operator evidence bundle guidance. It does not perform live HTTP checks or generate runtime evidence files.

  • Review /post-deployment-route-audit/ after upload.
  • Use /operator-evidence-export-bundle/ to find static Markdown templates.
  • Keep completed evidence outside the public contact-form workflow.

current site live header visual review handoff

The current site site files tunes the cropped header wordmark and homepage hero full-logo presentation for desktop, tablet, and phone screenshots.

  • Verify the top menu wordmark is readable without pushing navigation out of view.
  • Verify the homepage hero full logo is prominent, not cropped, and not surrounded by excessive blank space.
  • Capture screenshots at desktop, tablet, and phone widths before further proof-asset activation.

Fire and Storm Restoration

Call Fire and Storm Restoration before damage gets harder to document.

Emergency stabilization, standards-informed mitigation, insurance-ready documentation, and restoration scope support for Chicagoland properties.

Call 1(464) 274-1476