This guide sets up a Shopify store so AI systems can find it, read it, and quote it. It covers the work in the order that matters: let the crawlers in, fix the product facts, add the files and markup that describe your store, then publish content worth citing. It does not cover running ads, and it does not promise a citation or a recommendation. No vendor publishes a formula for what gets cited, and no setup step on Shopify changes that.
Shopify does a good share of the technical work for you. It hosts your pages, generates a sitemap, and produces a default robots.txt file. What it does not do is decide for you which AI crawlers to allow, write your product descriptions, or keep your prices consistent across the web. That is the work below. Screens and menu names change, so check the vendor docs in Sources for the current path before relying on a menu name or click path in this guide.
Who does which step
Two people may be involved, and the split matters. The marketer uses the Shopify admin dashboard, the theme editor, and apps. The marketer edits product titles and descriptions, sets prices and stock, writes blog posts, and installs and configures apps from the admin. The developer uses theme code, the Shopify CLI, or GitHub sync for Liquid edits. The developer edits theme files, adds or fixes structured data in the theme, and edits the robots.txt template. If you are both people, keep the split in mind anyway, because a code edit made like a dashboard edit is how stores break their theme. Test every code change in a duplicate theme before you publish it to the live store.
Step 1. Let the AI crawlers in
Shopify generates a robots.txt file automatically, and the default works for most stores. The risk is not usually the default. It is a custom robots.txt.liquid template someone added earlier, often during a wave of advice to block AI from scraping content, that still blocks the crawlers you now want. Check the live file first. Open your store domain followed by robots.txt in a browser and read it top to bottom. If you see a rule that blocks GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, or Google-Extended, that rule is a problem, and it is the first thing to fix.
If you need to change the file, the developer does it. Shopify's Help Center says you must first add a robots.txt.liquid file to the templates folder of your theme in the code editor, and then customize the content of the file. It also says that if you want to edit the robots.txt.liquid file, you should work with a Shopify Partner or have expertise in code edits and SEO, and that using Liquid to add or remove directives preserves Shopify's ability to keep the file updated automatically in the future, which is the recommended method. Shopify warns that this is an unsupported customization and that incorrect use can result in loss of traffic. That warning is the reason to test in a duplicate theme and to delete the custom template, which restores the default, if the change goes wrong.
Do not stop at robots.txt. A security app or a firewall rule can block a crawler that robots.txt allows. Check your logs for the crawlers you want: OAI-SearchBot for ChatGPT search, GPTBot for training, and PerplexityBot for Perplexity. A crawler that never arrives is blocked somewhere, even if robots.txt says it is welcome. OpenAI says it can take about 24 hours from a robots.txt update for its systems to adjust for search, and Perplexity says it may take up to 24 hours for its systems to reflect changes.
Step 2. Fix the product pages
A product page is the unit an AI system reads, quotes, and links to. Before you add any file or app, make the pages themselves worth reading.
The marketer does this part in the admin. For each product, write a title that names the product plainly, and a description that states what it is, what it is for, what it is made of, and the limits a buyer needs to know: sizes, compatibility, care, and what is included. Put the price, the options, and the stock status where a reader can see them without clicking. Keep the price current. When a sale price applies, state the sale price, the regular price, and when the sale ends. If a product is out of stock, say so on the page, and update it the day the stock changes.
Work through your best sellers first. They are the products an assistant is most likely to be asked about. Fix the pages that earn the questions, then work down the list.
Check for conflicts. If the same product shows a different price in your store, in a marketplace listing, and in a review roundup, an AI system has three answers and no reason to trust any of them. Fix the source of the conflict so they agree.
Step 3. Check the structured data your theme already outputs
Most Shopify themes output Product structured data already. Before you add an app or another block of markup, check what your theme produces. The developer opens a live product page, views the page source, and searches for the structured data block. Confirm it states the product name, price, currency, and availability, and that it matches what the visible page says. Then run a sample of product pages through a structured data validation tool and confirm the same facts are being read.
If the theme output is missing or wrong, the developer fixes it in the theme code, in a duplicate theme, and tests before publishing. If an SEO app or a review app also injects Product schema, you can end up with two conflicting blocks for the same product. Keep one source and remove the duplicate. A schema block that disagrees with the visible page is worse than no schema at all.
Google says structured data is not required for its generative AI features, and there is no special schema markup you need to add for them. It also says structured data helps with rich results and helps Google understand price, discount, and shipping costs on a page. Other engines use it to verify what a page claims. Treat schema as the confirmation of the facts on the page, not as a ticket into an answer.
Step 4. Add llms.txt and point it at your best pages
An llms.txt file is a short markdown briefing at your site root that tells models what you sell, who it is for, and where the key pages are. It is written for models generally. Google Search does not use llms.txt, and Google says so directly, but other assistants can read it. Keep the file short. Name your brand, state what you sell in one or two sentences, and link to your best category pages, your best guides, and your shipping and returns pages. Do not paste your whole catalog into it. For a large catalog, a fuller llms-full.txt file is the place for the longer list, and the short file should point to it.
Shopify does not publish llms.txt from the admin by default, so this is a developer step, using the same theme code or app route your store already uses for custom files. The marketer writes the content of the file: the brand description, the audience, and the links. The developer publishes it at the site root and confirms it loads at your store domain followed by llms.txt. Read our llms.txt guide for the file format and a complete sample.
Step 5. Publish content worth citing
A store with good product pages and no other content gives an AI system facts but no answers. Publish the guides and comparisons your customers actually ask for: how to choose between two of your products, how to use the product, and how to fix the common problem. The marketer writes these in the Shopify blog or pages editor. Open with a direct answer, then give the detail, then state the limits. Use your own first-hand experience, because Google says a first-hand review provides a unique perspective based on personal experience, while a summary of existing content simply restates information already available elsewhere.
Do not create a separate page for every possible phrasing of the same question. Google warns against creating separate content for every possible variation to manipulate rankings, since that can violate its scaled content abuse spam policy. One good guide per real question, kept current, beats ten thin pages. When a fact in a guide changes, update the fact. Do not change a page date to make it seem fresh when the content has not changed.
Step 6. Check the store the way an assistant would
After the setup steps, test the store as an outsider. Ask the assistants themselves what they say about your brand, using the questions your customers ask. If they cannot name your products or state your prices correctly, look at what they cite instead. The gap is usually in the facts: a missing price, a missing size, a blocked crawler, or a page that never states the use case.
Run the free scan as well. It checks whether AI crawlers can read your store today, and it shows where the setup is weak. Fix the failures in the order in this guide: access first, product facts second, markup third, content fourth. A store that is blocked at the edge is invisible no matter how good its content is.
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 AI systems read to verify facts, see our product schema guide
- •The complete crawler rule reference, see our robots.txt guide for AI search
Say you run a wool sock brand on Shopify
Say you run a wool sock brand on Shopify, selling hiking socks and everyday socks in three weights. The marketer rewrites the product pages so each one states the weight, the height, the sizes, the materials, and the price in plain text. The developer checks the theme output, finds the availability is missing on one template, fixes it in a duplicate theme, and publishes. The developer also finds an old robots.txt.liquid template that blocks GPTBot, removes the block, and confirms OAI-SearchBot and PerplexityBot arrive in the logs. The marketer writes one guide, how to choose a sock weight for winter hiking, opening with a direct answer. A shopper asks an assistant for a warm hiking sock in their size under a set budget. The assistant can check your price, your size range, and your stock, and it cites your guide for the weight advice.
What this guide does not cover
This guide covers the AI SEO setup for a Shopify store. It does not cover the full technical audit that checks every crawler and every page, the transaction layer that lets an agent complete a purchase, or the per-engine playbooks for getting each assistant to find you. It also does not cover Shopify apps in detail, because apps change, and the right app for your store depends on what your theme already does. Those are separate jobs, and this guide is the map, not the whole trip.
Check your own store now
Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan
Run the free scanSources
- Shopify Help Center, Editing robots.txt.liquid (specific): https://help.shopify.com/en/manual/promoting-marketing/seo/editing-robots-txt
- OpenAI, Overview of OpenAI crawlers (specific): https://platform.openai.com/docs/bots
- Perplexity, Perplexity crawlers (specific): https://docs.perplexity.ai/guides/bots
- 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, Product structured data (specific): https://developers.google.com/search/docs/appearance/structured-data/product
- Google Search Central, Share your product data with Google (specific): https://developers.google.com/search/docs/specialty/ecommerce/share-your-product-data-with-google
- Schema.org, Product type (specific): https://schema.org/Product
- llms.txt proposal (specific): 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.
