A family flooring contractor off WordPress and onto something it owns

WordPress to a statically built Astro site, 297 legacy URLs preserved, launched 26 October 2026.

  • Astro
  • GitHub Actions
  • Migration
  • Technical SEO
  • GA4

Situation

A family flooring contractor in New York City had a WordPress site that was slow, hard to change, and held together by plugins. The gallery lived in the WordPress media library, the quote form went through a third party, and nobody on the business side could tell whether the site produced leads.

Constraint

Years of accumulated search history could not be thrown away. Every address the old site had ever answered needed to keep working, and the business needed to be able to go back if the launch went wrong.

What I built

A statically built Astro and Tailwind site, deployed to Hostinger over FTPS by GitHub Actions on every merge. 297 legacy URLs mapped to single 301 redirects, smoke-tested across 1,440 requests before and after launch. The gallery migrated out of WordPress into typed local data with real alt text. Google Business reviews pulled at build time. GA4 wired so a submitted quote registers as a lead. Build-time gates that fail the build on a broken link, a wrong canonical, a malformed sitemap, an uncovered redirect, or two service pages that have drifted into near-duplicates.

What I owned

All of it: the audit, the architecture, the build, the migration, the deployment pipeline, the launch run sheet, and the rollback plan.

Result

Live at 12:41 PM New York time on 26 October 2026, with a 30-day rollback window held open to 25 November. The old WordPress install was archived rather than deleted, out of the web's reach. The first release after launch shipped the same afternoon.

297 legacy URLs preserved, 1,440 redirect assertions green, 32 of 32 CDN edge checks serving the new site