Aizii Learn · AI Search

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

# AEO checklist for Shopify brands

Shopify handles a large part of the technical work for a store by default: the sitemap, the SSL certificate, the mobile responsive theme, and the canonical tags. The work that is left is the work Shopify cannot do for you: deciding which crawlers may read the store, writing product facts that a system can read without guessing, and keeping the page, the markup, and the feed in agreement. This checklist covers the Shopify specific version of that work. It does not repeat the general ecommerce checklist in full; it covers what is different on Shopify, and points to the general checklist for the rest.

Platform screens change, so check the vendor docs in Sources for the current path before relying on a menu name or click path in this guide.

## 1\. Robots.txt, through the theme

Shopify generates a robots.txt file automatically, and you can override it by editing the robots.txt.liquid template in the theme. That file is a developer job: a marketer can ask for the change, but the edit itself lives in theme code.

-   Open \[yourdomain.com\]/robots.txt in a browser, replacing yourdomain.com with your actual domain, and read the file Shopify is serving right now. Check that GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, and Googlebot are not disallowed from the product and collection 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. Adding one AI bot group to the theme's robots.txt can reopen the default cart, checkout, and filter blocks to that bot by accident, because those blocks live in the star group. Check the full file after every edit, not just the lines you added.
-   Keep the default blocks that protect checkout, cart, and admin. Those paths should stay disallowed. The checklist is about opening the product and collection pages to the AI crawlers, not about opening the whole store.
-   After a change, ask for a recrawl in Search Console rather than waiting. 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.

## 2\. Sitemap, submitted once

Shopify generates the sitemap automatically. Every Shopify store has one, and it updates when you add a product, collection, page, or blog post.

-   Open \[yourdomain.com\]/sitemap.xml and confirm it lists the products, collections, pages, and blog posts that matter. Shopify's own help page says the file contains links to all your products, primary product image, pages, collections, and blog posts.
-   Submit the sitemap to Google Search Console. Shopify's help page says to submit it so Google can find and index the pages, and that you need to verify the domain first to confirm you own the store. The file name to enter is sitemap.xml.
-   Submit the same sitemap in Bing Webmaster Tools. Copilot retrieves from Bing, and a store that only submits to Google can be invisible to Copilot for months.
-   Do not create a second sitemap by hand and submit both. Two sitemaps that disagree will confuse the index, not help it. Shopify's generated file is the one to use.

## 3\. Product facts, in the theme and the apps

Shopify themes write Product structured data for product pages, and apps can add to it or replace it. The risk on Shopify is not missing markup. It is two sources of markup disagreeing with each other.

-   Pick one source for Product markup and stick to it. If the theme writes it, do not also run an app that writes a second Product block for the same product. If an app writes it, check that the theme is not writing a conflicting block. Two Product blocks for one product, with different prices, is a mismatch a system has to resolve by guessing.
-   Check a real product page 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 vendor docs in Sources for the current path to the test.
-   Check the same page with the Schema Markup Validator. It checks the markup against the full schema.org vocabulary, not just the types Google supports for rich results. A page can pass one and fail the other, and both results are useful.
-   Confirm the price, availability, and shipping information in the markup match the words on the page and the values in the product feed. 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. A mismatch between the three is the most common Shopify failure in this checklist.
-   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. Shopify tracks stock per variant, and the markup should follow the same rule.

## 4\. The llms.txt file Shopify already serves

Shopify serves a default llms.txt file for every store. Most Shopify teams have one without trying, because Shopify manages a default agents.md file and points the llms.txt address to the same content unless the theme adds its own template.

-   Open \[yourdomain.com\]/llms.txt and read what Shopify is serving. If it is the default file, it is a short summary of the store. That is a starting point, not a finished file.
-   Decide whether to replace it with a file written for your store. A custom file can list the pages worth citing: the best sellers, the category pages, the About page, the shipping and returns pages, and the guides that answer buyer questions. Keep it short. No vendor publishes a link count or size limit for the file, and none is claimed here.
-   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. Treat it as a helpful summary for the tools that read it, not as a requirement for Google.
-   Serving the file is a developer job if it needs a theme template. A marketer can write the content, but the file lives in theme code, not in the dashboard.

## 5\. Collections, search, and the store's own pages

-   Every collection page says what the collection is for, who it is for, and how the products in it differ, in plain sentences above or below the product grid. A collection page that is only a grid of images gives a system nothing to quote.
-   The store's search page is not a page to optimize for AI search. Googlebot does not type into site search, and a search results page is not a page an assistant should cite. Keep the search page out of the sitemap and out of the index.
-   The About page, the shipping page, and the returns page state the facts in plain sentences: who the brand is, how long shipping takes, what returns cost, and how long a customer has to return a product. An assistant that cannot state your shipping and returns terms will not recommend a product that depends on them.
-   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.

## 6\. What Shopify already does, so do not pay twice

Shopify's defaults cover the following, and a store should not pay an app or an agency to add them:

-   The sitemap, generated automatically and updated when products and pages change.
-   SSL, enabled by default, so the store serves over HTTPS.
-   Canonical tags on products, collections, and pages, set automatically by the theme.
-   A mobile responsive theme, required for themes in the Theme Store.
-   A robots.txt file, generated automatically, editable through the theme when you need to change it.

What Shopify does not do for you is the content: the product descriptions, the collection introductions, the About page, and the decision about which crawlers to allow. That is the store's own work, and it is the work this checklist is about.

### 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 coffee gear store on Shopify

Say you sell coffee gear on Shopify, and you work through this checklist. The robots.txt check finds the default file allows the AI crawlers, so nothing to change there. The sitemap check finds the sitemap was never submitted to Bing, only to Google, so you submit it in Bing Webmaster Tools. The markup check finds the theme writes a Product block and a review app writes a second one, with different prices on a product that went on sale, so you turn off the app's markup and keep the theme's. The llms.txt check finds Shopify's default file, which lists the store's pages but not the brewing guides that answer buyer questions, so you replace it with a short custom file that links to them. The collection check finds the grinder collection is only a grid, so you add three plain sentences about who the grinders are for and how they differ. 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 Shopify specific checklist. It does not cover the general ecommerce checklist in full, which is our AI search optimization checklist for ecommerce, or how to measure whether the checklist is working, which is our guide to measuring your brand's AI visibility, 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 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, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   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)
-   Shopify Help Center, Editing robots.txt.liquid (specific): [https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt](https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt)
-   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)
-   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.
