Hard Wire Construction
Visit the site
The need
Hard Wire was rebranding from an electrical contractor into a full construction company, and the move meant a new domain — hwconstruction.net — in place of the established electricianbarstowca.com. They needed a site that could carry years of search visibility across to a new brand, while also consolidating service information, project galleries, reviews, FAQs, financing details, and estimate requests that had been spread across separate channels.
What I built
Built a mobile-first marketing and business platform for an electrical and remodeling contractor serving Barstow and the High Desert. Service information, project galleries, customer reviews, FAQs, financing details, and a seven-step estimate request now live in one branded experience. The estimate form gathers project details, location, timing, contact preferences, and optional photos, while attribution information connects incoming leads to their marketing source. Behind it sits Hard Wire HQ, a private admin area for managing leads, website content, FAQs, pricing, estimates, scheduling, and SEO redirects. Public service and location pages are structured around individual URL slugs with their own page metadata and canonical URLs to support search visibility. To bridge the old site, a Cloudflare bulk-redirect file maps legacy URLs to their new counterparts using permanent 301 redirects — including both www and non-www versions of the homepage, About, Contact, FAQ, galleries, blogs, service pages, and location pages, with query strings preserved. A URL normalizer inside the new site also strips trailing slashes, so legacy-style paths such as /about/ resolve to the new /about route. An admin URL Migration Map tracks old-to-new pairs and their status, with the Cloudflare file holding the actual rules.
What changed
One branded experience from first visit through estimate request, with leads arriving with the project details, timing, and photos needed to quote accurately, and a private HQ where the team updates content, pricing, and FAQs without a developer. The legacy domain's key URLs are mapped to the new site with 301 redirects, configured to carry established pages and their query strings across the rebrand. The redirect rules are documented as configured mappings in the migration setup.
What I learned
A rebrand doesn't have to cost you your search history, but the migration has to be designed as part of the build rather than patched on after launch. Map every legacy URL deliberately, and keep the path from visitor to estimate short enough to finish on a phone.
Next up
Verifying each deployed redirect in production and monitoring for soft 404s, routing new leads automatically by service area, and triggering review requests once a project is marked complete.


