What a trades website actually needs in 2026 — and what it can skip

A trades website has one job: turn a stressed person with a broken thing into a booked visit. Every visitor arrives with the same three questions — do you do this, near me? can I trust you? what will it cost? The whole site is those three answers, in that order, as fast as possible, on a phone. Everything else is decoration.

The part that changed: who's reading

A fast-growing share of your next customers won't browse to you at all. They'll ask an AI assistant — “who's a good electrician near me?” — and the assistant will answer with a name. It picks that name by reading websites the way a very fast, very literal librarian would: structured data, clear service lists, named service areas, published prices, real answers to real questions. Sites built as image collages with “Welcome to our website!” text are invisible to it.

The fix isn't exotic. Machine-readable business facts (schema.org), one page per real question, service areas written as words instead of a map screenshot, and answers that commit — “a 40-gallon water heater, installed, runs from $1,450” beats “contact us for pricing” in front of both robots and humans.

The 2026 checklist

• Phone number that dials on tap, visible without scrolling
• Services as plain nouns — the words people actually search
• Prices, or honest “from” prices, in writing
• License number, insurance, and years — the trust block
• Service area in text: town names, not just a map
• Loads in under two seconds on a job-site phone connection
• Structured data so assistants can quote you accurately

What it can skip

Sliders (nobody waits for slide two). Stock photos of smiling models in hard hats (customers can smell them). Chat popups that open uninvited. A “blog” of filler posts nobody wrote with care. Video backgrounds that eat the data plan of the person standing in a flooded kitchen. If an element doesn't help answer the three questions, it's costing you the answer's speed.

We build every site this way — including the three rollouts we made to prove it, and the page you're reading now. View source; the receipts are in the markup.