Getting named when somebody asks an assistant for a local recommendation

Where an assistant gets its facts about a local business

A customer mentioned, almost in passing, that she'd found a competitor by asking an assistant for a recommendation nearby. The owner had never once thought of that as a channel worth paying attention to. A competitor was already winning it, quietly, without anyone noticing.

It's tempting to write this off as a fringe habit a handful of people have picked up, but the underlying behavior — asking a question instead of typing keywords — isn't new. It's just aimed at a different kind of tool now.

An assistant answering that kind of question isn't crawling the live web in the moment. It draws on facts it already holds some confidence in — your listing, your site, mentions from other sources — and leans toward whichever business has the clearest, most consistent facts behind it.

That's a different game from ranking in a list of ten blue links. It's closer to being the answer, or not appearing in the answer at all. There's no middle position on a results page to fall back on.

Think of it less like competing for a spot on a page and more like being the single fact someone repeats back to a friend. There's no runner-up position in a conversation.

Writing a page that states a fact plainly enough to be quoted

A page written to be persuasive, full of tone and personality before it ever states what the business actually does, is harder for a system to lift cleanly. A page that states the plain fact early — the service, the area, the specific thing that sets it apart — gives an assistant something it can quote directly without editing it first.

A simple sentence like naming the service and the towns covered, placed near the top of a page rather than buried after three paragraphs of introduction, does more of this work than any clever phrasing could.

This doesn't mean writing badly or stripping out every trace of voice. It means putting the plain, factual sentence near the top of the page. Let the personality show up in the paragraphs underneath it.

A page that buries its own service and location under three paragraphs of story before getting to the point is asking a system to do extra work it may simply skip.

The same details agreeing everywhere the assistant can look

An assistant weighing whether to trust a fact tends to look for it in more than one place. If your site says one service area and your listing says a different one, that disagreement reads as a reason for caution rather than a reason to name you confidently.

The same name, address, and details holding steady across every listing isn't just tidy bookkeeping. It's part of what makes a fact about your business trustworthy enough to repeat to someone else without hedging.

Third-party mentions you did not write yourself

A fact your own site states about itself carries less weight on its own than the same fact appearing on a source you didn't write — a local publication, an industry directory, a customer's own review. Those independent mentions are part of what an assistant cross-checks against before it trusts a claim.

This is why a page written entirely in the first person, with no outside confirmation anywhere, can still struggle to be trusted even when everything on it happens to be accurate.

This isn't something you can manufacture quickly, and trying to fake it tends to show. It builds slowly, through the same work that earns reviews and press mentions for any other reason entirely.

A short mention in a local newspaper's roundup of businesses, or a guest spot on a community group's page, counts for more here than a dozen posts written on your own site ever will.

Blocking crawlers as a decision with a cost attached

Some sites block automated crawlers entirely, sometimes without the owner even knowing the setting exists or that it was ever switched on by whoever built the site. That choice has a real cost.

A developer sometimes leaves this switched on by default while a site is still being built, then simply forgets to revisit the setting once the site actually goes live for customers.

A page a crawler can't reach is a page that can't be quoted, no matter how well it's written or how accurate the facts on it are. Check whether anything on the site is blocking access before assuming the content itself is the problem. It's a five-minute check that can explain an otherwise confusing gap.

This setting sometimes gets switched on by accident during a site rebuild, carried over from a staging environment where blocking crawlers made sense and was never turned back off.

Asking an assistant about your own business and reading what comes back

The simplest test costs nothing. Ask an assistant what it knows about your business, and read the answer closely rather than skimming it. Wrong hours, an old address, or a missing service reveals exactly which fact needs fixing first, and where.

Try asking from a couple of different angles too — by name directly, and by describing the service without naming the business at all. The two answers don't always match.

Pages a site needs before any of this can work at all is worth reading if the test comes back mostly blank. Marking up those facts in a form a machine can read directly helps the plain-language version land more cleanly too.

How this sits alongside search and the map listing explains where this newer channel fits next to the older ones. Tracking whether any of it produced an actual enquiry is the only way to know it's worth the ongoing attention it takes.

More from the blog

All posts