AI Visibility

Your buyers changed how they search. They ask ChatGPT, Claude, or Perplexity a question and take the answer. No page of links, no scrolling past ads.

And those tools don't list everybody. They recommend a few names. If your site is vague, unstructured, or unreadable to AI crawlers, the recommendation goes to someone else. I wrote about why your competitors show up in ChatGPT when you don't.

Being invisible there doesn't feel like losing. That's the trap. The deals just quietly go somewhere else.

An llms.txt file. A plain text file on your site that tells AI tools what you do, who it's for, and why you, in words they can lift directly.

Structured data. Schema markup across your key pages: Organization, Service, FAQ. Machine-readable proof of who you are, which both AI tools and Google read.

AI search setup. The technical layer: AI crawlers welcomed, clean structure, fast pages. If a tool can't read your site, nothing else on this list matters.

Content tuned to be quoted. Your key pages reworked with direct answers and a clear category, so AI can quote you instead of skipping you.

And all of it done for you, in the site itself. I don't sell an audit and wave goodbye. I build the fixes in.

I rebuilt webodew.com with AI. 67 commits, mobile speed from 64 to 98, and every piece of this package running live on it. The whole story is on the blog.

And I've been publishing on AI search since the shift started: how to get cited by AI, a full llms.txt guide for Webflow, and a stack of posts around them.

A lot of agencies added "AI" to their pitch deck last quarter. This page isn't a pivot. It's the work I already do, written down.

1. Send me your site. A URL and one call, and you get the exact price.
2. I check how AI sees you. I ask ChatGPT, Claude, and Perplexity about your business and note what they say, and what they miss.
3. I build the fixes in. llms.txt, schema, technical setup, content tuned to be quoted. In your site, not in a slideshow.
4. You get the record. A plain-language summary of what changed, why it matters, and what keeps the visibility compounding.

• An llms.txt file written for your business, live on your site
• Structured data on your key pages: Organization, Service, and FAQ schema
• Technical AI-search setup: crawler access, clean structure, fast pages
• Key pages tuned so AI can quote you: direct answers, clear category, no fluff
• A plain-language summary of what changed and why
• Everything implemented by me, not a deck of recommendations

Consultants, SaaS founders, and service businesses where being the recommended name wins the deal. You know what you do and who it's for. You're just not in the answer yet.

Not for you if you want a guaranteed spot in ChatGPT's answer. Nobody can sell that, and the people who do are selling smoke.

And not yet for you if your own homepage can't say what you do. AI can't recommend a business it can't understand. Start with a Sound Check instead: €250, a recorded review of your site, credited toward any project within 90 days.

Partly, and that's good news. The foundations overlap: clean structure, fast pages, clear content. Nothing you've earned in Google gets thrown away.

But AI engines don't hand back ten blue links. They read, they synthesize, and they recommend one or two names. Getting into that answer takes structured data they can parse, content they can quote, and zero ambiguity about what you do.

People call it GEO, generative engine optimization. Or AEO, answer engine optimization. I call it being the name that comes up.