Serving Chicagoland, Cicero, Berwyn, Oak Lawn, and surrounding suburbs.Hours: 10:00 AM to 6:00 PM, seven days a week

1(464) 274-1476 claims@fireandstormrestoration.com
FireandStormRestoration.com
Call 1(464) 274-1476

Production launch checklist

Production Launch Checklist for Fire and Storm Restoration

A practical operator checklist for uploading the website, activating it, validating created pages, testing the contact flow, checking mobile calls, and preparing search and local-business readiness.

Call 1(464) 274-1476 Request Restoration Help
WordPress uploadPermalink refreshLaunch validation

WordPress website launch steps

Use this checklist after backing up the live site and before considering the production launch complete.

  • Upload the production ZIP through Appearance > websites > Add New > Upload website.
  • Activate the Fire and Storm Restoration site.
  • Refresh permalinks from Settings > Permalinks by saving the current permalink structure.
  • Assign the homepage if WordPress does not automatically show the site filesd front page.
  • Verify primary navigation and footer navigation after activation.

Visitor-flow checks

Confirm the site works for emergency visitors, insurance visitors, adjusters, and future AI/search discovery systems.

  • Test the mobile call button and header phone link on a phone-sized screen.
  • Submit a safe test contact message and confirm redirect to the service request confirmation page.
  • Review the emergency dispatch guidance, insurance help, proof and trust, FAQ, and privacy policy pages.
  • Confirm no public file upload field is present.
  • Confirm business hours display as 10:00 AM to 6:00 PM, seven days a week.
  • Open /mobile-header-qa/ and confirm the desktop, tablet, and phone header states before final launch sign-off.

SEO, sitemap, and schema checks

the website outputs page metadata and JSON-LD, but XML sitemap generation should be handled by WordPress core sitemap support or an approved SEO plugin.

  • Check WordPress core sitemap or approved SEO plugin sitemap output after deployment.
  • Validate representative LocalBusiness, BreadcrumbList, Service, and FAQPage JSON-LD output.
  • Confirm canonical URLs, Open Graph, Twitter card metadata, and page titles render correctly.
  • Do not hardcode a created sitemap file inside the website unless a future safe mechanism is intentionally added.
  • Do not block important restoration, service-area, contact, privacy, or FAQ pages through robots rules.

Local proof and asset checks

Only add proof items after verification. the website intentionally avoids fake reviews, fake gallery results, fake ratings, and unsupported credential claims.

  • Confirm Google Business Profile status and add the verified profile URL only after it exists.
  • Confirm real review URLs before displaying review-profile buttons.
  • Approve real project photos before adding them to the local gallery approved settings.
  • Confirm licenses, certifications, insurance certificates, or partnerships before public claims are added.
  • Review the privacy policy and site safety disclaimers before launch.

Operator asset and polish follow-up

Before final launch, review the operator asset handoff and launch polish checklist so GBP links, review URLs, approved photos, credentials, and analytics decisions stay verification-based.

  • Use /operator-asset-handoff/ for pending proof assets.
  • Use /launch-polish-checklist/ for final public review.

v2.6.0 launch evidence handoff

Use the launch evidence report, operator sign-off packet, and deployment proof checklist after upload to record live verification without collecting private documents.

  • 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.

Recommended next step

Ready to launch?

Finish a backup, upload the ZIP, refresh permalinks, test phone and form flows, then review schema and sitemap output.

Privacy policy Safety and claim disclaimers GBP readiness Contact test Mobile header QA

Related Restoration Help

Keep moving through the restoration path.

Privacy policy Site safety and claim disclaimers Google Business Profile readiness Photo documentation standards Contact Live deployment verification Google Business Profile assets Approved photo intake Review-link readiness /operator-asset-handoff/ /launch-polish-checklist/ Mobile header QA Proof intake checklist Service-area finalization Operator verification workflow Asset readiness status Launch evidence report Operator sign-off packet Deployment proof checklist Post-deployment route audit

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.

1(464) 274-1476Request Restoration Help
Call 1(464) 274-1476