One page that sells dealer-level diagnostics at your door
Mobile auto electrician covering Lancashire and Greater Manchester, sold on one page with a callback form styled around a UK number plate.
- Client
- HM Mobile Auto Electrical
- Trade
- Mobile auto electrician
- Based
- Lancashire and Greater Manchester
- Live since
- 2026
What the business needed
HM Mobile Auto Electrical Ltd does dealer-level diagnostics, ECU coding, key programming, immobiliser faults, tracker and dashcam fitting and general auto-electrical repair, at the customer's address, across Lancashire and Greater Manchester. It is a trade where someone is letting a stranger work on their car unsupervised, so the credentials, SERMI accreditation, IMI qualification and a DBS check, carry real weight and had to be visible.
The business did not need a dozen pages. It needed one that a driver with a warning light could read on their phone and act on, with the phone number and a quote form never more than a thumb away.
What was built
A single long-scroll homepage plus the legal pages. The quote form appears twice, compact in the hero and in full at the bottom, and asks for name, phone, email, postcode, vehicle registration and the fault. The registration field is styled as a real UK plate, yellow with the blue band, because it is an object people recognise on sight.
There are no UI or animation libraries. Carousels are CSS scroll-snap with a small hook, the FAQ is a native details element that works with JavaScript off, and the form validates UK phone numbers and postcodes with the browser's own constraint API rather than a schema library.
Every word of copy, every image path and every piece of structured data lives in one content file, with a note at the top telling the next editor not to touch the components. Changing a price or a service is a one-file edit.
Consent done to the letter
Nothing loads before a visitor agrees, reject is as easy as accept, and the banner reads its state in a way that cannot mismatch between server and browser. Built for PECR rather than for the appearance of compliance.
Legal identity in the markup
Company name, Companies House number and registered office appear in the copy and in the AutoRepair structured data, not just in a footer line.
One floating button, by decision
WhatsApp is the only floating element. The header's call button is always in view, so a second sticky bar would just cover content. The reasoning is in a code comment for whoever comes next.
Images built for a static host
The hero uses a hand-cut small variant behind a picture element because a static export has no image server to resize on the fly. It is documented inline so nobody 'fixes' it back.
Getting it found
The title and description name the trade and both regions. AutoRepair and FAQPage structured data are generated from the same content file as the visible page, so the questions Google reads are the questions visitors see. There are no location sub-pages on this build; it is one market sold on one page, and the Business Profile does the local work.
Under the hood
What the site runs on. The same approach is described on the service pages it came from.
- Next.js 16, static export
- React 19 and TypeScript
- Tailwind CSS v4
- Formspark forms with native validation
- Native details FAQ, scroll-snap carousels
- Consent-gated GA4
- AutoRepair and FAQPage schema
- Single content module