A search strategist with wet shoes
I work where search results meet ordinary business language: service pages, home pages, location pages, evidence, and the small claims that decide whether a business is understood or passed over. The work is close to the page, the owner's wording, and the proof that makes a service easier to trust.
About
A vague page does not become trustworthy because a machine has learned to summarise it.
Rain on a shop awning, a half-empty café, and a laptop full of search results: that is where most of my work begins. I am from Ireland, raised between practical tradespeople and people who could argue over one sentence for an hour. That mix has stayed with me. One side asks whether the thing works. The other asks whether the wording can survive being read closely.
Before this work took its current shape, I spent years inside search strategy for small service firms: content architecture, paid-search cleanup, website audits, analytics interpretation, and editorial planning for commercial blogs. I have seen good businesses hide behind flat language. Composite examples I see often: a dental clinic describes "quality care" but never explains the first appointment; a legal office lists practice areas but gives no sign of what sort of client situation fits; a training provider says "flexible learning" and leaves the real constraints in someone's inbox. Search does not fix that. AI search makes the problem more visible, because answer systems compress what they can safely understand.
What I am strongest at now is finding the sentence a business has avoided writing: what it does, who it helps, why it should be trusted, and what proof makes that claim less fragile. I keep a private ledger of answer patterns, rewritten by hand after every audit, because hand-copying slows the eye down. The niche may sound technical, and parts of it are. But my stance is plain enough: AI Overview visibility is built from clear definitions, local evidence, named constraints, process detail, review language, credentials in ordinary wording, and examples that sound like real client situations. The owner should be able to explain every recommendation aloud without sounding like software.
If the page is muddy, the answer will be muddy too.
I help turn vague service claims into pages that people and AI systems can read without strain.
Send your site