Does every Potions integration crawl product pages?

No. Potions documents server-side catalog retrieval through a CMS connection or feed and says this can avoid crawling the storefront for catalog data.

Is Potions an AI training bot?

It is not documented as a general model-training crawler. Potions uses customer catalog and analytics data for its own recommendation algorithms.

Does the Potions crawler honor robots.txt?

The available record does not confirm that behavior. Publish a rule if needed, then verify the result in logs or use an enforceable access rule.

What could break if I block Potions?

A configured feed, recommendation, or merchandising workflow may stop refreshing. Check the Potions account and integration owner before blocking expected traffic.

Potions: AI Crawler Guide & robots.txt

What is Potions?

Potions traffic belongs to an ecommerce service used by its own customers. The bot record covers product-feed retrieval and website data collection rather than open-web search indexing.

Potions' current integration documentation puts the catalog or CMS connection at the center of the workflow. It pulls catalog data from systems such as Shopify, Prestashop, or a custom feed, then combines that data with connected analytics to produce recommendation and merchandising lists. The docs specifically say catalog retrieval does not require crawling the storefront, so not every Potions installation should generate page-crawl traffic.

When the crawler does appear, the recorded user agent is Potions/1.0.0. Requests should correspond to a known customer integration and its product or feed URLs. An unexpected visit is worth checking with the ecommerce team because this bot provides neither a signature endpoint nor a verified source range.

Potions uses catalog and behavioral data in recommendation algorithms, but this bot is not documented as a public AI search or foundation-model training crawler. Blocking it will not remove a store from general AI answers. It may instead interrupt a Potions integration that the store intentionally configured.

Relevant for AI search

Is Potions relevant for AI search?

Yes. Potions collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

Potions feeds a search index that also powers that engine's AI answer features and overviews. One crawl can serve a classic results page and a generated summary, so blocking it costs you both the rankings you would expect and a growing share of AI answers built on the same index.

How to handle Potions

If your store uses Potions, identify the exact catalog feed or public paths the integration needs and avoid a blanket bot exception. Keep private feed credentials in the integration itself rather than exposing protected data to any client that claims the user agent.

To request that the crawler stop across the site, publish:

User-agent: Potions
Disallow: /

Potions does not publish a robots.txt commitment for this crawler in the available material. Check whether requests stop after the rule changes. If they do not, disable the integration or enforce the restriction at your server or edge.

Examples

A Shopify merchant traces `Potions/1.0.0` requests to a recommendation integration configured by its ecommerce team.
A retailer moves its catalog to a server-side feed and confirms that Potions no longer needs to crawl storefront product pages.
A company that has never contracted with Potions blocks the token and investigates the source of repeated feed requests.

Frequently asked questions about Potions

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

The recorded purpose is to fetch product feeds and collect website data for Potions ecommerce services. Confirm that someone managing the store configured the integration.