Lead with trust
Make the owner-operated model, diagnostic policy, review proof, service boundary, and warranty easy to understand.
Case study · Website & booking system
Wonkeeland Appliance Repair
Replacing a burdened WordPress site with a fast, focused platform built around local trust and real customer action.
ClientWonkeeland Appliance Repair
MarketHuntington-area appliance repair
LaunchAugust 2026
PlatformStatic site + signed booking bridge
Wonkeeland is an owner-operated appliance-repair business serving homes around Ceredo, Huntington, Ashland, Ironton, and nearby communities. Its website needed to work like an extension of the business: explain the service clearly, establish confidence quickly, qualify the right jobs, and make scheduling straightforward.
01
The challenge
The old website carried more baggage than value.
The previous WordPress installation had accumulated theme and plugin overhead, irrelevant cleaning-template content, old archive pages, and a public URL structure that could not simply be discarded. The presentation also needed to better communicate Wonkeeland’s actual advantages: Leon performs the work, customers receive an upfront diagnosis, and local accountability matters.
A simple redesign was not enough. The replacement needed to preserve useful search equity, remove obsolete content truthfully, support online scheduling, and remain faster and easier to maintain than the system it replaced.
02
The strategy
Build around customer decisions—not a page template.
Answer useful questions
Create substantive appliance, symptom, brand, warranty, service-area, and customer-guide pages instead of filler articles.
Preserve the migration
Inventory the existing WordPress URLs, preserve useful paths, redirect moved resources, and return honest removal statuses for irrelevant content.
Connect the operation
Keep the public pages static while routing scheduling through a small signed bridge to Wonkeeland’s Front Desk system.
03
What we built
A lean public site with a secure operational connection.
- 36 canonical pagesCommercial service pages, customer guides, service-area resources, proof, policies, and conversion destinations.
- Complete WordPress exitA root cutover that removed WordPress from the public request path while retaining a recoverable private backup.
- Deliberate URL handlingA migration inventory covering the old sitemap with permanent redirects, preserved routes, and correct removals.
- Standalone booking bridgeSame-origin scheduling through an HMAC-signed, rate-limited PHP bridge with private configuration outside the web root.
- Search architectureUnique metadata, canonicals, structured data, breadcrumbs, internal-link checks, sitemap coverage, and entity consistency.
- Privacy-safe measurement hooksEvents for calls, scheduling progress, and completed bookings without putting customer details into analytics payloads.
Measured before launch
A structural performance change.
These figures are controlled local and hosted-preview measurements, not production field data. They demonstrate the change in page architecture without pretending laboratory results are customer outcomes.
Homepage requests139 → 5WordPress versus static preview
Transferred page weight~990 → ~90 KBInitial controlled comparison
Hosted mobile performance98Lighthouse preview score
Accessibility100Hosted desktop and mobile preview
04
The outcome
The website became part of the operating system.
The production cutover completed on August 28, 2026. WordPress no longer sits in the public path, obsolete template URLs are handled deliberately, and the booking experience connects the public site to Brandi without exposing application credentials to the browser.
The result is a much clearer expression of the business and a maintainable foundation for ongoing search content, conversion measurement, and operational integration.
Have a website carrying old baggage?