All articles
AI SearchLocal SEOGoogle Search Console

If an AI Answers Your Customer Before Your Website Does, What Is Your Website Still For?

Mehr Farooq·2026-11-13· 6 min read
A smartphone with a softly glowing, completely blurred and unreadable screen lying on the worn wooden counter of a small shop, a hand resting beside it and a plain blank notebook and pen nearby in warm window light

What did my own Search Console show me this month?

One of my websites is a fee calculator for homeowners' associations. Its Search Console report holds the strangest pair of numbers I own: the site has now passed a hundred thousand impressions, with nine hundred and eleven clicks, at an average position of about eight. Shown a hundred thousand times. Visited nine hundred and eleven. Both figures are real, both are mine, and the distance between them is where this post lives.

The usual reading is that the site is failing. I do not think that is right, and last week I wrote about the nine hundred and eleven — the people who clicked past a finished AI answer because they came to use a tool, not to read a summary. This post is about the other ninety-nine thousand: the impressions that never became visits, because the answer was completed above my site, in a box I do not control, in words I did not choose. If that is the new normal — and my own numbers say it is — then an honest question follows about what my websites are actually for now.

Read next
If AI Answers Everything, Why Did 911 People Still Click?
Open

What exactly does the answer engine take, and what does it leave behind?

What it takes is the errand visit: the simple, settled question. What is this fee? What does this job pay? What does that repair roughly cost? Those questions used to end at a website like mine, and the visit they brought was shallow but real — a page viewed, a name remembered, a chance to be useful again later. The machine now completes that errand on the spot, and the visit simply never happens. Nobody did anything wrong. The answer was just finished before my door.

What it leaves behind is everything that cannot be finished by a paragraph. It cannot run your figures through a calculator and hand you your number — only the average of strangers. It cannot answer a telephone. It cannot stand in a flooded kitchen, or put a crew on a roof, or sign its name under a figure it is willing to be wrong about. The visit the machine takes was the visit that wanted information. The visit that remains wants an outcome — and outcomes still live on websites, and behind phone numbers, exactly where they always did.

Why did one nine-minute phone call pay me ninety-eight dollars?

On 3 November, my Houston roofing website earned its first money: one converted phone call, nine minutes and four seconds long, worth ninety-eight dollars. Nobody clicked an advertisement. No summary was involved. A homeowner with a real roof and a real problem found the site, read enough to trust it, and did the oldest thing in commerce — picked up the phone and talked about a physical job at a physical address.

Hold that call next to the hundred thousand impressions, and the whole argument settles itself. The impressions are the part of my work the machines are absorbing — the describing, the summarising, the rough ranges. The call is the part they cannot absorb, because a leak does not care how well it has been described. The closer a need sits to the physical world, and to right now, the less an answer engine can finish it. The website's job, for that visitor, was never to be read. It was to be found, believed, and called.

What can an answer engine not copy from your website?

It cannot copy work it has to cite. My UAE salary site now carries a Domain Rating of 31, with forty-six other websites linking to it — not because I chased links, but because the site did a job nobody else had done patiently: profession after profession, salary figures gathered from named sources, with the disagreements printed instead of hidden. When an answer engine replies to a salary question, it replies from somewhere. Being the somewhere — the page the answer had to be built from — is a position no summary can take from you, because the summary needs you to exist.

It also cannot copy a working tool, or a number with a name behind it. An engine can quote an average; my calculator produces your figure, from your inputs, on a page that stands behind the result. That is the difference between an echo and a source. Echoes are free and infinite, and worth exactly that. Sources are scarce, they take months, and — this is the part I keep coming back to — they are the one thing the machines must keep pointing at in order to answer at all.

A sturdy black desk telephone with a coiled cord on a contractor's workbench beside a yellow tape measure, a hammer, work gloves and a blank open notebook with a pencil, rolls of plans blurred behind

So what should a small website owner actually do about it?

Four things, all of them unglamorous. Answer the question in the first lines of the page, in plain words, so that when the machine quotes somebody, it quotes you accurately and by name. Build at least one thing that does something — a calculator, a checker, a tool — because doing cannot be summarised the way saying can. Gather one set of numbers nobody else has bothered to gather, and publish it with its sources showing. And make the human door impossible to miss: the phone number, the profile, the proof, placed where the visitor lands the moment the finished answer stops being enough.

Then change what you count. I still watch impressions and clicks, but I no longer let them grade the work alone — a call, a calculation completed, a citation earned are worth more than a thousand shallow visits, and my own sites have now shown me all three. The owners who will suffer are not the ones the machines answer for; they are the ones who never built anything the answer could not replace. Everyone else has simply been promoted: from leaflet to workshop, whether they wanted the promotion or not.

A tall stack of plain unmarked notebooks and blank printed pages on a wooden desk by a window, a magnifying glass and reading glasses resting on top, a small potted plant and a chipped mug beside them in soft daylight

If an AI answers your customer before your website does, what is your website still for?

For everything the answer cannot finish. The calculation with a real person's real figures. The nine-minute call about a real roof. The figure that somebody had to gather, check and sign. My impressions taught me that being read is no longer the job; my first ninety-eight dollars taught me what the job became. The website is not where my business is described any more. It is where my business is done — and where the machines themselves have to come when they need something true to say.

So here is today's question, and I am asking it of my own sites first: if the next person who needs what you sell receives a complete, confident answer from a machine before your name ever appears — what have you built that the machine itself has to point to, and if the honest answer is "nothing yet", what will you build first?

Want SEO built on proof, not promises?

I build and rank websites for home service businesses — and I test everything on my own sites first.