Shopify AI Readiness Scanner - AI SEO & llms.txt Audit
Pricing
from $40.00 / 1,000 store scanneds
Shopify AI Readiness Scanner - AI SEO & llms.txt Audit
Audit any Shopify storefront for AI search: what ChatGPT, Perplexity and Claude can read. Checks robots.txt for GPTBot, OAI-SearchBot and PerplexityBot, product JSON-LD, llms.txt, sitemap and the agent-commerce endpoint. A 0-100 score, an A-F grade and a fix per check.
Pricing
from $40.00 / 1,000 store scanneds
Rating
0.0
(0)
Developer
Bruce McGinley
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
Shopify AI Readiness Scanner
Score any Shopify storefront on what AI shopping assistants can actually read from it. ChatGPT, Perplexity, Claude and Google's shopping agents recommend products they can fetch and parse; a store that blocks their crawlers, ships no product structured data, or hides its catalogue behind JavaScript is invisible to them however good its products are. This Actor runs the same checks an assistant's crawler would hit, grades the store from A to F, and returns every check with its status and the fix.
How it works
Give it a list of storefront URLs or domains. For each one the Actor fetches the homepage, robots.txt, llms.txt and the sitemap, locates a product page, and evaluates:
- AI crawler access. Whether the major AI shopping crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot and others) are allowed to reach product pages, and which robots.txt rule blocks each one that is not.
- Product structured data. Whether product pages carry
ProductandOfferJSON-LD with price, availability and identifiers an assistant can quote. - Readable without JavaScript. Whether the homepage and product page contain real content before any script runs, since most AI crawlers do not run JavaScript.
- llms.txt and sitemap. Whether the store publishes the files assistants use to find and prioritise pages.
- Agent-commerce endpoint. Whether the store's agent-facing catalogue endpoint answers, and whether its filters actually filter.
Each store becomes one dataset item with a score out of 100, a letter grade, counts of passed, warned and failed checks, the list of AI crawlers the store blocks, and the full list of checks with a plain-language explanation and a concrete fix for each.
Tutorial
- Open the Actor and paste storefront domains into Stores, one per line.
example.com,www.example.comandhttps://example.com/all work. - Click Start. A store takes a few seconds; a list of fifty takes about five minutes because the scanner is paced to be polite to the stores it reads.
- Open the Output tab, or export the dataset as JSON, CSV or Excel. Sort by
scoreto find the stores with the most to fix, or filter onfailedgreater than zero.
Any public storefront can be scanned. Stores on platforms other than Shopify get the same checks, with the platform-specific fixes left generic.
Pricing
This Actor uses pay-per-event pricing. You are charged one store-scan event for every store that returns a report. A store that could not be scanned, because it is offline, behind a bot challenge, or mistyped, still gets a row in the dataset explaining why, and is not charged. You can cap spend on any run with the maximum total charge setting; the Actor stops cleanly when it is reached and says how many stores were left. There is no charge for the run itself beyond the platform's own compute.
On the Apify free plan you can run the Actor within the free monthly usage allowance; the scanner also caps fresh scans at roughly twelve per minute per run, which the Actor respects automatically.
Input example
{"stores": ["allbirds.com", "gymshark.com", "https://www.bombas.com/"]}
Output example
One item per store:
{"store": "allbirds.com","origin": "https://www.allbirds.com","platform": "shopify","score": 82,"grade": "B","provisional": false,"scannedAt": "2026-09-03T14:02:11.000Z","passed": 6,"warnings": 2,"failed": 1,"blockedCrawlers": ["Google-Extended"],"checks": [{"id": "ai-crawlers","title": "AI shopping crawler access","status": "warn","severity": "medium","detail": "1 of 12 AI crawlers are blocked from your product pages by robots.txt.","fix": "Remove the Disallow rule for Google-Extended, or add an explicit Allow for /products/."}],"error": null}
Use cases
- Agencies auditing a client list before a pitch, or re-running it monthly to show progress.
- Merchants checking their own store and a handful of competitors.
- Researchers and journalists measuring how much of a category is readable by AI assistants.
- AI agents that need a structured readiness score for a store as one step in a longer workflow; the dataset is plain JSON and every field is documented here.
Related Actors
Pair this with a Shopify products scraper to compare what a store sells with what an assistant can see of it, or with a website content crawler to read the pages this Actor flags.
FAQ
Does it need any login or API key? No. It reads only public pages and public files.
Is the store told it was scanned? The scanner identifies itself with a named user agent and honours robots.txt. A store that disallows it is reported as such and not scored.
Why is a score marked provisional? When a product page could not be found, the structured-data checks could not run and the score covers fewer checks.
How current is a result? A store scanned recently by anyone is served from a short-lived cache; otherwise it is scanned fresh at the time of the run.
Something looks wrong. Open an issue on the Actor's Issues tab with the store domain and the check in question.

