AI search optimization
Your buyers ask an assistant before they ask a search box. If the assistant cannot retrieve your pages, cannot work out which company you are, or has nothing worth quoting, you are absent from the answer it gives. We measure that first and fix what the measurement found.
What the engagement covers
Open the door to the crawlers that answer
GPTBot, ClaudeBot, PerplexityBot and the rest each read robots.txt on their own terms. We audit what your policy actually allows against the crawlers that matter, rather than against a template somebody copied.
Make the identity resolvable
An assistant that cannot tell which company you are will not name you. llms.txt, the Schema.org graph and the identity files get written so the entity behind the site reads the same way twice.
Fix the pages an engine cannot retrieve
Content that only exists after the browser runs is content an engine has nothing to quote from. We find the pages that never reach the server HTML and say which are worth moving.
Measure the same thing twice
The audit that opened the engagement runs again at the end, on the same checks. Anything we claim to have changed is a number visible on both reports.
What you get out of it
- A crawler policy written against the assistants that answer, not a template
- llms.txt, the schema graph and the identity files in one consistent state
- The list of pages an engine cannot retrieve, with the reason for each
- Opening and closing audits side by side, run on the same checks
Put your own visibility on the table
One to two weeks: crawler policy, the schema graph and the convention files put right, then the same audit run again so the change is measured. Thirty minutes first, to work out whether that is what your site needs.
Book a call about visibilityThirty minutes, free.
- Fee
- $1,500
- Length
- 1-2 weeks
Re-audited at the end against the same checks, so the change is measured rather than claimed.