Case file, website
The website was gone. The archive still had it.
A local flooring retailer lost its site with no backup. The words came back from the Wayback Machine. Everything underneath them is new.
- The business's own wording, recovered from the archive and checked against current services.
- Contact email corrected to the current address.
- A new contact form with service options.
- Rebuilt as a fast static site.
- Starting problem
- Site gone, no backup
- Role
- Recovery, rebuild, contact form, launch audit
- What shipped
- A fast static site with a working form
- Verified outcome
- Live, with current contact details
Recover the words before writing new ones.
The business had already described its own services, in its own voice, on a site customers had used for years. Starting from a blank page would have meant inventing that again. The Wayback Machine still had the pages, so the rebuild started there.
Build it static.
The site had to stay simple enough for a small retail business to run for years without a developer on call. A static HTML and CSS build has no database and no plugins, so there is nothing that needs patching between visits, and it loads fast.
Fix what the archive got wrong.
An archive preserves a site exactly, including what had gone stale. The recovered pages still carried an old contact email and had no working way to reach the business. The email was corrected, and a new contact form with service options was added, built with Claude Code and relayed through a mail provider.
True now.
- The site is live again on a fast static build.
- Its contact information is current.
- The contact form works.
- The business's own words are back online.
Not measured.
A rebuild restores presence. It does not by itself restore search visibility lost while the site was down, and that recovery has not been measured.
Have something that should be on this page?
Tell us what's broken, slow, or stuck. The first conversation is free.