An ecommerce store is ready for AI search when three things are true at the same time: AI crawlers can reach the pages, the pages state facts a system can read without guessing, and the store's own data agrees with what the pages say. If any one of those three fails, the other two do not save it. A store with perfect product markup that blocks the crawlers is invisible. A store the crawlers can reach, with prices that disagree between the page, the markup, and the feed, is untrusted. This checklist works through those three in order, so you fix the gate first, then the facts, then the agreement between them.
Google's own guide to generative AI features says the same thing from the other side: the best practices for SEO continue to be relevant because its generative AI features are rooted in its core Search ranking and quality systems. A page must be indexed and eligible to be shown in Google Search with a snippet to be eligible for those features. There is no separate secret list. The checklist below is that foundation, written for a store.
1. Can the crawlers reach the store
Start here, because nothing else matters if the answer is no.
- 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. The tokens are case-insensitive for matching, but spell them the way each vendor documents them so the next person reading the file is not guessing.
- Check the same file for a broad rule that catches the AI crawlers by accident. A rule aimed at one bot can catch another when a named group is missing, because a crawler follows only the group that names it and falls back to the star group only when no group matches. Read the whole file, not just the AI lines.
- Confirm the store is not password protected or behind a bot wall that challenges real crawlers. A store in private mode cannot be read by any engine, and a bot wall that challenges Googlebot will challenge the AI crawlers too. Check this at the edge, not just in the file, because the file is what you declare and the edge is what enforces.
- Confirm the product sitemap exists and lists the pages that matter. Open [yourdomain.com]/sitemap.xml and check that product pages, category pages, and key content pages are in it. On Shopify, the sitemap is generated automatically and updates when you add a product or page, and Shopify's own help page says to submit it to Google Search Console so Google can find and index the pages.
2. Can the pages be indexed
A page that is not indexed cannot be cited, and cannot be a supporting link in an AI answer.
- 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 appear in Google's AI features, and the other engines have their own indexes with the same rule.
- Check that the same pages are indexed in Bing's index too, through Bing Webmaster Tools. Copilot retrieves from Bing, and a brand that only watches Google can be invisible to Copilot for months.
- Look for duplicate pages eating the crawl. Faceted navigation, filtered category URLs, and variant URLs can multiply the pages a crawler has to read. Reduce the duplicates with canonical tags and by keeping filtered URLs out of the sitemap, so the crawl goes to the pages that should be cited.
- Confirm the pages are not blocked by a noindex tag or a robots meta tag that was left over from a staging copy or a seasonal page. One stray noindex on a category page can remove a whole section from the index.
3. Do the pages state the facts
AI systems retrieve relevant, up-to-date pages from the Search index and review the specific information on those pages to generate an answer. Google's AI guide describes exactly that retrieval step. The facts on the page are what get reviewed, so they have to be complete and plain.
- Every product page names the product, the price, the availability, and the shipping and returns terms in words a shopper can read. A price hidden behind a click, or a shipping cost that only appears at checkout, is a fact the system cannot read.
- Every product page carries Product structured data with the same price and availability the page shows. Google's Product structured data docs say that when you add structured data to product pages, users can see price, availability, review ratings, shipping information, and more right in search results.
- Every category page says what the category is for, who it is for, and how the products in it differ. A category page that is only a grid of images gives a system nothing to quote.
- Every brand page, the About page and the key content pages, says who the brand is, what it sells, and what it stands for, in plain sentences. An assistant that cannot describe your brand will describe a competitor instead.
- Product descriptions give the facts a buyer asks about: materials, size, fit, compatibility, care, and what is in the box. A description that only says a product is great gives a system nothing specific to cite.
4. Do the three copies of the truth agree
Availability and price live in three places: the visible page, the structured data, and the product feed. All three must say the same thing.
- After a price or stock change, check all three, not just the one you edited. A feed that updates slowly while the page updates fast, or markup that is cached while the page is fresh, is a mismatch, and a mismatch is a product that gets disapproved or a recommendation that ends in a sold-out page.
- For variants, the rule applies per variant. If one size is out of stock and the others are not, mark that size as out of stock and leave the rest alone. A product-level status that hides a variant-level shortage sends shoppers to a size that does not exist.
- Check the feed against the page on a sample of products, including one that recently sold out and one that recently came back. A single mismatch is a mistake. A pattern of mismatches is a broken routine.
5. Is the store's own house in order
These are the checks that do not belong to a single page.
- The llms.txt file, if the store serves one, lists the pages worth citing and links to them. 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, and the llms.txt proposal is the document that defines the format. Treat the file as a helpful summary for the tools that read it, not as a requirement for Google.
- The store's business information is the same everywhere: the same name, the same address, the same phone number, the same hours, on the site, on the Business Profile, and in the Organization markup. Inconsistent business information is a trust problem, and it is covered in full in our guide to fixing inconsistent business info across the web.
- Reviews on the product pages are real, visible on the page, and match the aggregate rating the markup claims. A rating in the markup that a shopper cannot see on the page is a claim the page does not support.
- The store is fast enough and readable enough on a phone. Google's AI guide lists a good page experience as part of the technical structure, including a site that displays well across devices and keeps its main content easy to tell apart from the rest of the page.
6. What not to chase
Google's AI guide has a mythbusting section, and it is worth reading before spending money on any of these:
- Do not create llms.txt files or special markup for Google. Google says you do not need new machine readable files, AI text files, markup, or Markdown to appear in Google Search, including its generative AI capabilities, as Google Search itself does not use them.
- Do not break content into tiny pieces for AI. Google says there is no requirement to chunk content, and its systems can understand the nuance of several topics on a page.
- Do not rewrite copy just for AI systems. Google says AI systems can understand synonyms and general meanings, so you do not need to capture every variation of how someone might seek content like yours.
- Do not seek inauthentic mentions. Google says its core ranking systems focus on high quality content while other systems block spam, and its generative AI features depend on both.
- Do not overfocus on structured data for Google's AI features. Google says structured data is not required for generative AI search, and there is no special schema.org markup you need to add. Keep using it as part of overall SEO, because it helps with eligibility for rich results on Google Search.
None of that means the checklist above is wrong. It means the checklist is the foundation, not a set of tricks on top of it.
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
- •The markup this engine reads, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a cycling apparel brand
Say you sell cycling apparel, and you work through this checklist for the first time. The robots.txt check finds GPTBot allowed and PerplexityBot allowed, but a broad rule disallows the path your new collection lives on, because the collection was built from a template that carried a staging block. You fix the rule. The index check finds the best selling jersey indexed in Google but not in Bing, so you submit the sitemap in Bing Webmaster Tools and request a recrawl. 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, so you fix the feed. The house check finds the store's phone number differs between the site and the Business Profile, so you fix the profile. None of those fixes is dramatic. Together they are the difference between a store an assistant can reach, read, and trust, and a store it cannot.
What this guide does not cover
This guide covers the checklist for a store that wants to be found by AI search. It does not cover how to measure whether the checklist is working, which is our guide to measuring your brand's AI visibility, or how to run a full audit, which is our guide to running an AI visibility audit on your store, or the transaction layer that turns a recommendation into a sale. A checklist gets you readable. 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 scanSources
- Google Search Central, Optimizing your website for generative AI features on Google Search (specific): 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
- Google Search Central, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- OpenAI, Bots documentation (specific): https://platform.openai.com/docs/bots
- Perplexity, Bots documentation (specific): 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
- llms.txt proposal (specific): https://llmstxt.org
- RFC 9309, Robots Exclusion Protocol (general standard): https://www.rfc-editor.org/rfc/rfc9309.html
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.
