Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to run an AI visibility audit on your store

An AI visibility audit is a check of whether AI assistants can reach your store, read its facts, and recommend it, done in order, with the findings written down. It is not a score, because no vendor publishes a visibility score, and it is not a single tool, because no single tool shows all of it. It is a routine: the gate, the index, the facts, the agreement between them, the measurement, and the fixes in priority order. A store that runs the audit the same way twice can compare the two runs. A store that improvises each time cannot.

Run the audit in the order below. The order matters, because a failure early in the list makes the later checks meaningless. A store that blocks the crawlers does not need a content audit yet. A store with wrong prices does not need a benchmark yet.

## 1\. The gate: can the crawlers reach the store

-   Open \[yourdomain.com\]/robots.txt in a browser, replacing yourdomain.com with your actual domain. Read it as a crawler would. Check that GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, and Googlebot are not disallowed from the product and category pages.
-   Read the whole file for a broad rule that catches an AI crawler by accident. A crawler follows only the group that names it and falls back to the star group only when no group matches, so a named bot ignores everything written for the star group, and a bot with no named group inherits the star rules.
-   Confirm the store is not password protected or behind a bot wall that challenges real crawlers. Check this at the edge, not just in the file, because the file is what you declare and the edge is what enforces.
-   Check the server logs for the crawler tokens, if the store has access to them. A log line that carries the GPTBot token but an IP outside OpenAI's published range is untrusted traffic, not GPTBot, because a user-agent string on its own is easy to copy. OpenAI publishes the IP list for its bots, and the bots documentation in Sources points to it.
-   Confirm the product sitemap exists at \[yourdomain.com\]/sitemap.xml and lists the pages that matter. On Shopify, the sitemap is generated automatically and updates when you add a product or page.

## 2\. The index: are the pages in the indexes

-   Check the key pages in Search Console with the URL Inspection tool, and confirm Google has indexed them. A page Google has not indexed cannot be a supporting link in Google's AI features.
-   Check the same pages in Bing Webmaster Tools. Copilot retrieves from Bing, and a brand that only watches Google can be invisible to Copilot for months.
-   List every key page that is not indexed, and note why: blocked by robots.txt, blocked by a noindex tag, a duplicate of another page, or never crawled at all. Each reason has a different fix, and the audit should name the reason, not just the page.
-   Check for duplicate pages eating the crawl. Faceted navigation, filtered category URLs, and variant URLs can multiply the pages a crawler has to read. Note the duplicates and the canonical tags that should resolve them.

## 3\. The facts: what the pages state

-   Pick ten product pages: the five best sellers and five products that recently changed price or stock. Read each one as a buyer would, and write down whether it names the product, the price, the availability, and the shipping and returns terms in words a shopper can read.
-   Check the Product structured data on the same ten pages with the Rich Results Test. It reads the live page or a pasted code snippet and lists the structured data it finds, with errors and warnings. A pass means the markup is eligible for Google's rich results. It does not mean Google will show a rich result.
-   Check the same pages with the Schema Markup Validator. It checks the markup against the full schema.org vocabulary, not just the types Google supports for rich results.
-   Read the category pages and the About page the same way. A category page that is only a grid of images gives a system nothing to quote. An About page that does not say who the brand is, what it sells, and what it stands for gives an assistant nothing to describe.
-   Check the llms.txt file, if the store serves one, at \[yourdomain.com\]/llms.txt. Note whether it lists the pages worth citing. Google says it does not use llms.txt for Google Search, and its AI guide lists llms.txt files as one of the things you do not need for Google Search. Other assistants may read the file, so note what it says, and do not treat it as a requirement for Google.

## 4\. The agreement: do the three copies match

-   For the same ten product pages, compare the price and availability in three places: the visible page, the structured data, and the product feed. Write down every mismatch, product by product.
-   For variants, check per variant. If one size is out of stock and the others are not, the markup and the feed should say so for that size, not for the whole product.
-   Check the feed against the page on a sample that includes one product that recently sold out and one that recently came back. A single mismatch is a mistake. A pattern of mismatches is a broken routine, and the audit should say so.
-   Note whether the store's business information agrees everywhere: the same name, address, phone number, and hours on the site, on the Business Profile, and in the Organization markup.

## 5\. The measurement: what the assistants actually do

-   Open Search Console and find the Generative AI performance report. Google's AI guide points site owners to this report to see how content performs in generative AI features on Google Search and Discover. Note the impressions by page. The report shows impressions only, by page, country, device, and date. It has no clicks, no queries, and no click-through rate. Check the vendor docs in Sources for the current path to the report.
-   Ask the assistants directly with a fixed prompt set, and log the results. Use twenty to thirty buyer questions, plus a small set of branded prompts and comparison prompts. Log whether your brand was named, whether it was recommended first, which pages were cited, and whether the facts stated were right or wrong. Do this the same way every audit, so the audits can be compared.
-   Note the wrong facts separately from the missing mentions. A brand with many mentions and many wrong facts has a different problem from a brand with no mentions at all.

## 6\. The findings, in priority order

Write the findings in the order they should be fixed, not in the order you found them. The priority order is the same as the audit order: the gate first, then the index, then the facts, then the agreement, then the content.

-   Gate failures first: a blocked crawler, a password protected store, a bot wall that challenges real crawlers. Nothing else matters until the gate is open.
-   Index failures second: key pages not indexed, duplicates eating the crawl, a sitemap never submitted to Bing.
-   Fact failures third: prices or availability missing from the page, markup that disagrees with the page, a category page with nothing to quote.
-   Agreement failures fourth: the feed disagreeing with the page, variants marked at the product level, business information that differs across the web.
-   Content gaps last: missing guides, thin descriptions, an About page that does not say who the brand is. Content gaps matter, but they matter after the store can be reached, indexed, and read.

For each finding, write the page, the problem, and the fix, in one line each. A finding without a fix is a complaint. A finding with a fix is a work list.

## 7\. Re-audit after the fixes

-   Fix the gate and index findings first, then ask for a recrawl in Search Console for the pages that changed. Google's AI guide says its systems retrieve relevant, up-to-date pages from the Search index, so a corrected page that has not been recrawled is still the old page to the system that retrieves it. Check the vendor docs in Sources for the current path to the recrawl request.
-   Wait for the recrawl before re-running the measurement. Google's AI features page says crawling can take anywhere from several days to several months depending on how often its systems decide a page needs refreshing, so a fix is not instant, and the re-audit should not be run the day after the fix.
-   Re-run the same prompt set, the same way, and compare the log with the first audit. A share rising over two runs is a signal. One run can be noise.
-   Keep the audit reports in one place, with the date on each, so the store can see the direction over time. An audit that is run once and filed away is a snapshot. An audit run on a schedule is a measurement.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •The llms.txt format and a complete sample, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •The markup this engine reads, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •The complete crawler rule reference, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

### Say you run a skincare brand

Say you sell skincare, and you run this audit for the first time. The gate check finds GPTBot allowed and PerplexityBot allowed, but a broad rule disallows the path your new collection lives on. The index check finds the best selling serum indexed in Google but not in Bing. The facts check finds the price on the page and the price in the markup agree, but the feed still shows the old price from before a sale ended. The agreement check finds two variants marked out of stock at the product level when only one size is gone. The measurement finds ChatGPT names your brand in three of twenty prompts, and states a price from before the sale ended. You write the findings in priority order: fix the robots.txt rule, submit the sitemap to Bing, fix the feed, fix the variant marking, then add the missing guide. You fix the first four, ask for a recrawl, wait, and re-run the prompts. The share rises, the wrong price is gone, and the audit report shows the direction. The audit did not give you a score. It gave you a work list, in the right order.

## What this guide does not cover

This guide covers how to run an AI visibility audit on your store. It does not cover how to measure visibility in full, which is our guide to measuring your brand's AI visibility, or how to benchmark against competitors, which is our guide to benchmarking AI visibility against competitors, or the transaction layer that turns a recommendation into a sale. An audit tells you what is broken and in what order to fix it. The rest of the system has to be ready when the shopper arrives.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your pages today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   Google Search Central, Optimizing your website for generative AI features on Google Search (specific): [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
-   Google Search Central, AI features and your website (specific): [https://developers.google.com/search/docs/appearance/ai-features](https://developers.google.com/search/docs/appearance/ai-features)
-   Google Search Central, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   OpenAI, Bots documentation (specific): [https://platform.openai.com/docs/bots](https://platform.openai.com/docs/bots)
-   Perplexity, Bots documentation (specific): [https://docs.perplexity.ai/guides/bots](https://docs.perplexity.ai/guides/bots)
-   Shopify Help Center, Finding and submitting your sitemap (specific): [https://help.shopify.com/en/manual/promoting-marketing/seo/find-site-map](https://help.shopify.com/en/manual/promoting-marketing/seo/find-site-map)
-   Google Rich Results Test (general docs): [https://search.google.com/test/rich-results](https://search.google.com/test/rich-results)
-   Schema Markup Validator (general docs): [https://validator.schema.org/](https://validator.schema.org/)
-   llms.txt proposal (specific): [https://llmstxt.org](https://llmstxt.org/)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
