{"id":3371,"date":"2026-10-07T01:37:38","date_gmt":"2026-10-07T01:37:38","guid":{"rendered":"https:\/\/ewebtoolz.com\/blog\/an-ai-visibility-audit-checklist-you-can-actually-use\/"},"modified":"2026-10-07T01:37:38","modified_gmt":"2026-10-07T01:37:38","slug":"an-ai-visibility-audit-checklist-you-can-actually-use","status":"publish","type":"post","link":"https:\/\/ewebtoolz.com\/blog\/an-ai-visibility-audit-checklist-you-can-actually-use\/","title":{"rendered":"An AI Visibility Audit Checklist You Can Actually Use"},"content":{"rendered":"


\n<\/p>\n

\n
\"A<\/figure>\n

An AI visibility audit compares what buyers ask, what AI systems say, and what your public evidence actually supports.<\/strong> Its output should be a short list of defensible fixes, not a single score that hides the cause of the problem.<\/p>\n

You can run the first pass in a focused working session. Reserve more time for a large site, multiple markets, or regulated claims. The checklist below is designed to produce a useful baseline before you buy more content or another reporting tool.<\/p>\n

The audit also gives you a clean brief if you later hand execution to someone else. If it identifies valuable questions but your agency needs delivery support, AEOFAST<\/a> is a managed-service option to evaluate against that question list. Keep your audit worksheet as the independent record of scope and results rather than replacing it with selected success examples.<\/p>\n

Define the audit boundary before collecting answers<\/h2>\n

Write down the brand, products, audience, market, language, and decision you are investigating. \u201cOur AI visibility\u201d is too broad. \u201cHow UK agency buyers discover our client-reporting product\u201d gives the audit a manageable boundary.<\/p>\n

Choose a small initial set of questions spanning discovery, comparison, verification, and purchase constraints. Use the exact same wording during the baseline. Identify each question with a stable ID, such as A01 or A02.<\/p>\n

Record engines separately. A response from one product is not evidence about another. Where the interface exposes a model, search mode, location, or account context, record it. Where it does not, mark the field unknown rather than guessing.<\/p>\n

Even within one company, engines differ. Google says AI Overviews and AI Mode may use different models and techniques, so their responses and links vary, and AI Overviews appear only when Google\u2019s systems judge them additive, which means they often do not trigger at all. Log \u201cno AI Overview shown\u201d as its own outcome rather than as an absence of your brand.<\/p>\n

The audit worksheet<\/h2>\n

Create one row per response, not one row per brand. A response can mention the brand while citing only third-party sources, or cite your page without recommending the product.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n\n
Field<\/th>\nWhat to record<\/th>\nWhy it matters<\/th>\n<\/tr>\n<\/thead>\n
Question ID and exact wording<\/td>\nUnedited buyer question<\/td>\nPrevents quiet changes to the test<\/td>\n<\/tr>\n
Timestamp and engine<\/td>\nDate, time zone, product, visible mode<\/td>\nMakes comparisons interpretable<\/td>\n<\/tr>\n
Context<\/td>\nLanguage, location, account state, prior conversation<\/td>\nIdentifies confounders<\/td>\n<\/tr>\n
Brand mention<\/td>\nPresent, absent, ambiguous<\/td>\nSeparates visibility from a citation<\/td>\n<\/tr>\n
Owned-domain citation<\/td>\nExact linked URL<\/td>\nShows which page was used<\/td>\n<\/tr>\n
Accuracy<\/td>\nCorrect, incomplete, wrong, not assessable<\/td>\nPrevents celebrating misleading exposure<\/td>\n<\/tr>\n
Evidence<\/td>\nSaved answer and source links<\/td>\nLets another person review the result<\/td>\n<\/tr>\n
Next action<\/td>\nSpecific page or fact to investigate<\/td>\nConnects reporting to work<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Preserve unsuccessful checks too. If the product is unavailable or the tool errors, log the failure separately. Do not turn a failed test into an absence, and do not quietly remove failures from the report.<\/p>\n

Generated answers vary between runs. As a working rule, run each baseline question at least three times on different days, in a fresh session with no prior conversation, and report the range (\u201ccited in 2 of 3 runs\u201d) rather than the best result. This is our recommended method, not a platform requirement, but it prevents a single lucky or unlucky answer from setting the agenda.<\/p>\n

Before Check 1: settings that can remove a site silently<\/h2>\n

Several switches outside the content itself can exclude a site from AI answers. None of them shows up when you simply read a page, so check them first. Each one takes minutes, and finding one can save weeks of rewriting.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Setting<\/th>\nWhere to look<\/th>\nWhat goes wrong<\/th>\n<\/tr>\n<\/thead>\n
Search generative AI control<\/td>\nSearch Console, Settings, Search generative AI<\/td>\nA site set to \u201cexclude\u201d receives no links or impressions from AI Overviews or AI Mode<\/td>\n<\/tr>\n
Inherited control<\/td>\nParent properties in Search Console<\/td>\nA URL-prefix or subdomain property inherits its parent\u2019s choice unless configured directly<\/td>\n<\/tr>\n
CDN AI-bot policies<\/td>\nCloudflare Security settings, or your CDN\u2019s bot rules<\/td>\nA \u201cBlock\u201d policy for training can now block mixed-use crawlers such as Googlebot and Bingbot<\/td>\n<\/tr>\n
robots.txt per crawler<\/td>\n\/robots.txt<\/code><\/td>\nBlocking OAI-SearchBot or PerplexityBot removes you from those engines\u2019 search answers<\/td>\n<\/tr>\n
Snippet controls<\/td>\nPage source and HTTP headers<\/td>\nnosnippet<\/code>, max-snippet<\/code>, or a broad data-nosnippet<\/code> wrapper limits what Google can show, including in AI features<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
\"Search<\/a>
Google’s Search generative AI control decides whether a site can appear in AI Overviews and AI Mode. Check it before auditing content. Source: Search Console Help<\/a>.<\/figcaption><\/figure>\n

The Search generative AI control<\/a> became available to all sites on 31 August 2026. Google says a change typically takes effect within one to two days, and that the setting does not affect model training; Google-Extended handles training separately.<\/p>\n

The CDN item deserves special attention in 2026. Cloudflare\u2019s explanation of its September 15 changes<\/a> states that its \u201cBlock\u201d and \u201cBlock on pages with ads\u201d settings for training now apply to mixed-use crawlers, including Applebot, Bingbot, and Googlebot, so either setting affects search as well as training. Cloudflare\u2019s alternative for sites that want to keep search visibility while refusing training is a setting called \u201cDisallow AI Training\u201d.<\/p>\n

\"Cloudflare<\/a>
Since 15 September 2026, Cloudflare’s Block settings for AI training also affect mixed-use crawlers such as Googlebot and Bingbot. Source: Cloudflare Blog<\/a>.<\/figcaption><\/figure>\n

Cloudflare also changed defaults for new domains on that date: training and agent bots are blocked on pages that display ads<\/a>, while search crawlers remain allowed. If a client moved a domain onto Cloudflare recently, confirm which policy it inherited instead of assuming the old behavior.<\/p>\n

One small robots.txt detail also catches teams out: Google\u2019s robots.txt documentation<\/a> says Google does not support the crawl-delay<\/code> rule. A Crawl-delay<\/code> line may matter to other crawlers, but it does nothing to slow or prioritize Googlebot.<\/p>\n

\"Audit<\/a>
Keep the evidence connected, from the exact question to a checkable source and an assigned next action. View full size<\/a>.<\/figcaption><\/figure>\n

Check 1: can the important pages be reached?<\/h2>\n

Select the homepage, your main product or service page, a pricing or process page, and two substantive resources. For each, inspect the final status, redirects, canonical URL, indexing directives, and whether the main content is readable when logged out.<\/p>\n

A homepage that loads is not proof that a deep article or login-free help page works. Check the exact URLs cited or expected to answer your questions.<\/p>\n

OpenAI\u2019s publisher guidance<\/a> identifies OAI-SearchBot access as relevant to inclusion in ChatGPT summaries and snippets. Inspect both crawler rules and any edge security rules; changing robots.txt cannot fix every access problem.<\/p>\n

Save technical failures as separate tickets. If the page is inaccessible, it is premature to conclude that its writing style is the reason it does not appear.<\/p>\n

Test as the crawler, then verify with logs<\/h3>\n

A quick first test is to request each URL with a crawler\u2019s user-agent string and compare the result with a normal browser request:<\/p>\n

curl -s -o \/dev\/null -w \"%{http_code} %{size_download}\\n\" \\\n  -A \"Mozilla\/5.0 AppleWebKit\/537.36 (KHTML, like Gecko); compatible; OAI-SearchBot\/1.4; +https:\/\/openai.com\/searchbot\" \\\n  https:\/\/www.example.com\/pricing\/\n<\/code><\/pre>\n
Repeat with the Googlebot, Bingbot, and PerplexityBot strings. A different status code or a much smaller response is a red flag worth investigating.<\/p>\n
Understand the limits of this test. It proves only how your stack treats the user-agent string. Bot-management systems often verify crawlers by IP address, so a spoofed request can be treated differently from the real crawler in either direction. For Google, the URL Inspection tool<\/a> shows the HTML that Googlebot actually received, which is the stronger evidence.<\/p>\n
The definitive check is your logs. Real crawlers come from published addresses: Google documents a reverse DNS method and IP lists<\/a>, OpenAI publishes searchbot.json<\/code>, and Perplexity publishes perplexitybot.json<\/code>. Anything claiming to be a crawler from another address is an impostor and should not be counted as a visit.<\/p>\n
\"Google<\/a>
Google publishes reverse DNS patterns and IP lists so you can separate real Google crawlers from impostors in your logs. Source: Google Search Central<\/a>.<\/figcaption><\/figure>\n
When we ran this check on seopressor.com, the origin server\u2019s access log turned out to be the wrong place to look. It recorded the CDN\u2019s edge addresses instead of the visitors\u2019 addresses, and its log format had no user-agent field at all, so it could not show which AI crawlers had visited. Many sites behind a CDN have the same blind spot. Ask for CDN logs or enable a log format that records the user agent and the original client IP before you draw conclusions about crawler access.<\/p>\n
Check 2: does the page contain the answer?<\/h2>\n
Read the page as a skeptical buyer. Highlight the exact passage that resolves the question. If you cannot identify it, a title containing the right keyword is not enough.<\/p>\n
For a service comparison, look for fit criteria and tradeoffs. For pricing, look for the billing unit and meaningful exclusions. For a local business, look for actual service boundaries and current availability. For a technical product, look for version-specific instructions and failure conditions.<\/p>\n
Use three editorial labels:<\/p>\n