What is AI search visibility?
AI search visibility is how reliably your pages are found, understood, and cited when people ask questions in Google’s AI features and in assistants such as ChatGPT, Perplexity, and Claude. Google’s own AI optimization guide treats this as ordinary SEO: a page must be indexed and eligible for snippets, and the same quality systems apply. This audit checks those fundamentals against the AI surfaces.
What Google says you do and do not need
Google’s guidance is plain about the shortcuts. You do not need special machine-readable files, AI-specific markup, or content chopped into fragments for AI, and you do not need to rewrite pages in a particular style for it. What it asks for is content that is genuinely useful and distinctive, on pages that are accessible to crawlers and users. Its helpful content guidance frames the test as who made the page, how, and why.
What an AI search visibility audit checks
- Indexing and snippet eligibility. Pages are indexed, canonical, and not blocked by robots rules, noindex, or snippet restrictions, confirmed in Search Console.
- Crawler access. Your robots.txt and any CDN or firewall rules for Googlebot and for AI crawlers such as GPTBot, OAI-SearchBot, ClaudeBot, and PerplexityBot. Allowing or blocking each is your decision, and I document it.
- Rendered content. Key content is present in the server-rendered HTML. Googlebot runs JavaScript, but many AI crawlers do not, which matters for React, Next.js, and headless WordPress builds.
- Content worth citing. First-hand, specific, answer-first passages with a real author, dates, and sources, instead of generic summaries anyone could write.
- Entity and brand signals. A consistent name, author and about pages, Organization and Person markup, and profile links that agree with each other.
- Agent-friendly pages. Semantic HTML, labelled forms and buttons, and a clean accessibility tree, so assistants acting for a user can actually use the page.
- Measurement. GA4 reporting for traffic from AI assistants, Search Console data for AI features where it is available, and a short list of target questions to re-check over time.
What this audit will not do
- It will not promise citations or rankings. Nobody controls what an AI assistant says.
- It will not sell an llms.txt file as a ranking lever. Google has said it does not use one, and studies of AI crawler traffic have not shown such files driving citations. Publishing one is harmless, just not a priority.
- It will not recommend chopping pages into fragments, mass-producing AI content, or manufacturing mentions across forums. Those are the tactics Google’s guidance and spam policies warn against.
What you receive
- A written audit with prioritized fixes, each with the evidence behind it and an effort estimate.
- A short list of target questions and the pages that should answer them.
- An optional implementation sprint for the fixes, on WordPress, WooCommerce, or Next.js.
- A re-check after 60 to 90 days, when crawling and indexing changes have had time to show.
Who this is for
Sites with real expertise that are indexed but rarely surfaced: agencies, SaaS, ecommerce, and professional services. It also suits JavaScript-heavy or headless builds, and teams planning a rebuild who want AI search visibility designed in rather than patched on. It sits alongside my technical SEO work and the wider AI integration services.
Other services
Frequently asked questions
Is AI search visibility different from SEO?
Google treats optimizing for its AI features as the same work as SEO. Some assistants use their own crawlers and sources, so the audit also covers their access and rendering requirements.
Do I need an llms.txt file?
No. Google says no special AI files are needed, and there is no evidence they drive citations. It is optional and low priority.
Can you guarantee my site will be cited by ChatGPT or Google AI?
No, and anyone who does is overpromising. I fix the things within your control: access, rendering, content quality, and signals, then measure.
How long before I see changes?
Crawl and rendering fixes show up as pages are recrawled, usually within days to weeks. Content authority takes months. I re-check at 60 to 90 days.
Do you also fix what the audit finds?
Yes, as an optional implementation sprint for WordPress, WooCommerce, and Next.js sites. The audit is useful on its own if your team will implement it.
Is it worth it for a small or new site?
If your core pages are not yet indexed or ranking, classic SEO fundamentals come first, and I will tell you so rather than sell you an audit you do not need.
Tell me about your AI Search Visibility Audit project
Share the site and the questions you want it to be found and cited for.
- Site URL and the platform it runs on (WordPress, Next.js, other)
- Whether the key pages are indexed in Search Console today
- Any firewall, CDN, or robots rules that may block crawlers
- Audit only, or audit plus implementation