Technical access and indexing
I check what search engines and AI crawlers can read, along with canonical URLs, the sitemap, robots rules, and core structured data.
The website and its technical signalsWhen a customer asks ChatGPT, Gemini, or another AI for help with a problem, your business may not appear at all—or the assistant may describe it inaccurately. The audit investigates why and shows you what is worth changing.
Discuss an AI visibility audit
My experience spans data, websites, SEO and GEO checks, and practical testing of AI answers. That helps me separate indexing or access issues from problems with content, credible sources, and unclear positioning.
The audit connects the customer’s buying situation, public evidence about the business, and the website’s technical accessibility. Each role needs a different answer.
AI visibility is not a single status light. A crawler may reach your site without it being indexed. An indexed site may not establish a clear business identity. An assistant may understand the business but lack sources it can cite.
I check what search engines and AI crawlers can read, along with canonical URLs, the sitemap, robots rules, and core structured data.
The website and its technical signalsI assess whether public pages explain who you are, who you serve, what problem you solve, and why someone should trust you.
Business identity, services, and evidenceI check which first-party and third-party sources confirm key facts about the business, its offer, and its experience—and where sources contradict one another.
Consistency and public evidenceI test a set of real questions, compare mentions, descriptions, and sources, and distinguish observations from hypotheses.
A test panel, rather than a single promptI separate technical blockers, unclear explanations, missing evidence, and dependencies on third-party sources. Each recommended step explains what it should change and how to check it later.
We start with the business context. Without it, the result would be a generic technical checklist disconnected from the customer.
Products, typical customers, competitors, and the questions that lead to choosing a provider.
Your website, public sources, and a repeatable set of tests in AI assistants.
Recommended changes, their order, and a way to track progress without false certainty.
Model answers change. I distinguish repeatable findings from a snapshot that, on its own, proves very little.
The goal and scope, the people involved, the materials or access needed, the deliverable, timing, price, and any follow-up work that would be a separate engagement. We start only when we have a shared understanding of all of these.
Before working with nonpublic data, we will agree in writing on which sources may be used, where they may be processed, who has access, and whether external AI tools are allowed. I do not work with nonpublic data without that agreement.
We choose them based on your customers, countries, languages, and buying situations. The proposal will specify the test panel’s scope, measurement date, and how the tests will be repeated.
It includes a diagnosis, priorities, and a verification approach. We can agree on small fixes as a follow-up; larger content, development, or PR projects are not automatically included.
No. We can improve technical access, the clarity of the business, and the quality of public sources. We cannot control another company’s model rankings or recommendations, so the findings make the evidence and level of confidence clear.
Tell me which business, service, and buying situation you want to examine. I will propose test questions, an audit scope, and how you will receive the results.
Prefer email? jsem@radekduha.cz