A customer looking for a plumber at nine at night used to open a search engine, scan three or four results, and click the one that looked least alarming. A growing number of them now ask an assistant instead, read one paragraph, and call whoever it named. Your website is still doing the work of convincing them — it is just doing it in a room you cannot see, to a reader who never loads the page.
That reader has different habits from the human one. It does not care about your hero video. It cannot be moved by a photograph. It reads structure, it reads specifics, and it strongly prefers a page that answers one question completely over a page that gestures at six. Most small business sites are built the other way around.
What is actually being read when nobody loads your page?
Text, mostly — and the relationships between pieces of text. An assistant answering “who does emergency plumbing in my area” is drawing on pages that state a service, a place and a circumstance in plain language, close together, in a structure that makes clear which is which. A heading that says Emergency call-outs, evenings and weekends followed by two sentences of specifics does more work than a beautifully set paragraph about your commitment to quality.
The unglamorous parts matter more than they used to. Headings that describe what follows them. Structured data that states your hours, your service area and your prices as data rather than as decoration. Pages that resolve one topic instead of scattering it across a services page, a blog post and a PDF. None of this is new advice — it is just that the cost of ignoring it changed.
Why specificity beats polish here
Vagueness is expensive now. “We serve the greater metro area” cannot be turned into an answer; a named list of suburbs can. “Competitive pricing” cannot be quoted; “call-outs from $180, quoted before we start” can. Every sentence a model cannot verify or attribute is a sentence it will route around on its way to a competitor who wrote the specific version.
This is the part small businesses are unusually well placed to win. A national chain writes in hedged, legal-reviewed generalities because it has to. You do not. The details that felt too small to put on the site — that you answer the phone yourself, that you do not charge for the first visit, that you have worked on that particular type of building for eleven years — are exactly the material an assistant needs to justify naming you.
“Every sentence a model cannot verify is a sentence it routes around on its way to a competitor who wrote the specific version.”
What this does not mean
It does not mean writing for machines. Copy stuffed with keywords reads badly to both audiences and has been penalised by search engines for a decade; models are not more forgiving. It does not mean adding a chatbot to your own site, which solves a different problem entirely and does nothing for the customer asking somewhere else.
And it does not mean abandoning design. The human reader still decides whether to call after they land on the page, and a site that looks neglected will lose them even when the assistant sent them. Structure is what gets you named; the page is what converts the visit. Both have to work.
Where to start if the site already exists
Take the five questions customers actually ask you on the phone and check whether any single page on your site answers one of them completely. Usually none do — the answers exist, scattered. Consolidating each into its own page, with a heading that states the question and a first paragraph that answers it outright, is the highest-value change most small sites can make, and it improves the page for human readers at the same time.
After that: put your hours, service area, and contact details in structured data rather than only in an image or a footer; name your locations and services explicitly; and delete the paragraphs that say nothing. The work is closer to editing than to marketing.
ANCHOR CASE STUDY Swift Plumbing — one page per question customers actually ask