Does Shopify block AI bots by default?

By Matt Kerr·Published 12 November 2026

Shopify Help Center says: Shopify does not state the starting access rule for each of these six bots. It describes a built-in robots.txt file for stores and separate network bot management. A public-page Allow rule is not a named-bot promise at both layers.

Shopify theme instructions says: Read your store’s current robots.txt before editing robots.txt.liquid in the published theme. Shopify warns that adding the template replaces its generated output. Compare the old file with the rendered result before you publish the change.

Rules for each bot

GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot

Shopify Help Center and Shopify theme instructions say: The docs do not say for this bot. They describe a generated robots.txt and separate network controls. Inspect robots.txt.liquid in the published theme, compare its output, and edit the named user-agent rule.

The two controls have different reach

Shopify Help Center says: The Help Center says Shopify handles bot management directly for stores at the network layer. It does not recommend putting a proxy in front of Shopify and says it cannot support that setup. For robots.txt, owners can allow or block user-agent names through the theme template. Those rules are advisory and not every crawler is guaranteed to follow them.

Shopify also separates open-web crawling from Shopify Catalog. Activated agentic storefronts can receive product data through Catalog independently of robots.txt. Blocking an open-web crawler does not stop that sharing. If your concern is products appearing through an activated channel, read its agentic storefront settings as well as the bot rules served on your store domain.

Preserve the file before changing the theme

Shopify Help Center and Shopify theme instructions say: From Online Store, select the relevant theme and Edit code. The Help Center describes adding a robots template. The developer instructions describe creating robots.txt.liquid in Templates. Both lead to a template that can add or remove directives. Work in the published theme when you intend the public file to change, and save a copy of its current output first.

The Help Center recommends Liquid so Shopify can keep rules updated. It also warns that a template using built-in groups can retain rules the current generated file no longer has, including /search and /policies/. The developer guide likewise says rendered template output does not always equal the generated file. These details qualify the update advice. Compare the actual text instead of assuming that using built-in groups makes the two outputs identical.

Allow or exclude only the crawler you chose

Shopify theme instructions says: The developer examples add a named user-agent group outside the Liquid that prints existing groups. They show both Disallow and Allow forms. Apply that method only after checking whether the name is already covered in your output. Keep the other groups intact. The six bot reference links above let you review each bot before selecting the name and the paths you want to change.

Shopify Help Center says: After saving, fetch the live store file and use the browser and six headers below on a public product or page URL. Compare the same address before and after the edit. The Help Center says file changes are instant but crawlers may react later. Your test records what is served now. It does not measure when an outside crawler will return or which Catalog channels receive product data.

curl -sS -L https://example.com/robots.txt
curl -sS -L -D - -o /dev/null -A 'Mozilla/5.0' https://example.com/
curl -sS -L -D - -o /dev/null -A 'GPTBot' https://example.com/
curl -sS -L -D - -o /dev/null -A 'ClaudeBot' https://example.com/
curl -sS -L -D - -o /dev/null -A 'PerplexityBot' https://example.com/
curl -sS -L -D - -o /dev/null -A 'Google-Extended' https://example.com/
curl -sS -L -D - -o /dev/null -A 'Applebot-Extended' https://example.com/
curl -sS -L -D - -o /dev/null -A 'CCBot' https://example.com/