What we measure — and what we do not
This page exists so you can check our claims. It describes every check, its source and its limits.
The most important limit
We measure only what your shop publishes publicly. We do not observe whether an AI assistant mentions, recommends or knows your shop — we have no access to that, and nobody claiming otherwise can substantiate it.
Concretely: if your robots.txt blocks GPTBot, that is an instruction you published. It does not mean your shop is “invisible to AI assistants”. Those two statements are not the same, and we only make the first.
What is measured
Five checks, all on publicly retrievable data. No account, no Shopify access, no AI evaluation.
- AI crawler access
- We read your robots.txt and determine which of the four major AI crawlers are allowed to read the shop. A block is only reported when the entire shop is disallowed — an excluded cart is not a block.
- Source: /robots.txt
- Structured product data
- On product pages we check whether schema.org/Product data is present and complete (price, availability, brand, description).
- Source: Product pages (HTML)
- Titles and meta descriptions
- We check whether the page title and meta description exist and are a sensible length.
- Source: Product pages (HTML)
- Product count
- We determine your product count via /products.json or sitemap.xml. Where only part is determinable we report it as a lower bound rather than asserting an exact figure.
- Source: /products.json, /sitemap.xml
- llms.txt
- We check whether an llms.txt exists. We do not claim it has any effect — no provider publicly commits to reading it.
- Source: /llms.txt
Crawlers checked: GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot.
At most 20 product pages are fetched per check. Results for larger catalogues are labelled as an extrapolation.
What is explicitly not measured
Our check cannot determine these things. We list them so it is clear what you are not paying for.
- Whether an AI assistant mentions your shopWe do not query ChatGPT, Claude, Perplexity or Gemini, and we do not evaluate their answers.
- Rankings or positionsWe do not measure a position in any search result and do not promise one.
- Visitors or revenueWe have no access to your analytics and do not extrapolate a revenue effect.
- Comparison against competitorsWe do not check other shops and do not build leaderboards.
- The quality of your copyWe check whether fields are present and complete — not whether a text is well written.
The possible outcomes
Not every check always produces a result. Rather than guess, we state which state a check is in.
- Checked
- The check ran and its result is in the report.
- Unavailable
- The file or page could not be retrieved. We report that as “could not check” and derive no result from it.
- Not permitted
- Your robots.txt disallows our own crawler. We respect that and stop the check.
- Failed
- The retrieval failed technically. That is reported too, and never counted as a finding.
How we behave as a crawler
- We respect your robots.txt for our own fetches too. If you exclude us, we do not check.
- We identify ourselves clearly: AIProCraftScanner/1.0 (+https://www.aiprocraft.de/scan; visibility check on behalf of the site owner)
- The number of checks per connection is limited so your shop is not burdened.
- Only domain, timestamp and a result summary are stored — no personal data.
- If you later connect Shopify, we request read access only (read_products, read_orders, read_all_orders). There is no write access.
See also: a complete sample report
