# Any store engine. Including the one you built.

> Aiscovery tests your storefront from the outside, so it works on any e-commerce platform, headless stack or custom store. Nothing to install.

- Canonical URL: https://aiscovery.io/platforms
- Markdown version: https://aiscovery.io/platforms.md
- Last updated: 2026-10-21

AI agents only see the pages your store serves. So do we: no app, no plugin, nothing to install.

- [Request a demo](https://aiscovery.io/demo)
- [See what breaks](https://aiscovery.io/platforms#engines)

Shopify, WooCommerce, BigCommerce, Magento, Shopware, PrestaShop, Wix, Squarespace, Your own code.

## One test, from the outside

The same four moves on every engine. Nothing runs inside your store.

1. **Add.** Your store's address, and your OK to test it.
2. **Check.** AI crawler rules, page basics and structured data, in about a minute.
3. **Try.** Named AI agents look for a product, its price, stock, delivery and returns.
4. **Verify.** Each fix names the change. Check again and we re-run the same test.

> Interactive demo on the HTML page: a guided tour that plays the 4 steps one after another on an example store. Its content is written out below.

> Example store: northwind-outdoor.com.

### Add

- northwind-outdoor.com
- I run this store and I'm OK with the test
- Check my store

### Check

| Check | Example result |
| --- | --- |
| AI crawler rules | Allowed |
| Page basics | In the page text |
| Product structured data | Found |

### Try

Google Gemini: "Find a waterproof jacket under $150. What does delivery cost?"

- Product: found
- Price: found
- Stock: found
- Delivery cost: not found
- Returns: found

Delivery cost is only shown at checkout.

### Verify

- Show delivery cost on product pages
- Delivery cost not found → Delivery cost found
- Same test, run again: 5 of 5 facts found

**That's it. Four steps.** No install, no meeting. You get what agents could and couldn't do, and the fix for each.

[Request a demo](https://aiscovery.io/demo)

## What usually breaks, engine by engine

The patterns we see most. Your own result shows only what is really on your store.

> Interactive demo on the HTML page: a store engine picker. Each engine shows an illustrative storefront scene with numbered spots that match its common problems.

### Shopify

Common problems:

1. Delivery cost appears only at checkout, so agents can't quote a total.
2. Variant prices depend on a script, so agents read the default variant.
3. Pop-ups for discounts or cookies cover the product facts.

What we check: robots.txt (including edits in robots.txt.liquid), product structured data, variant links and your delivery pages.

### WooCommerce

Common problems:

1. robots.txt blocks /wp-content/ files, so pages render without their styles and scripts.
2. Variable products show a price range until an option is picked.
3. Security or caching plugins block automated visitors outright.

What we check: Which page files robots.txt blocks, firewall responses, price and stock in structured data, and your returns page.

### BigCommerce

Common problems:

1. Shipping estimates live in the cart, not on product or policy pages.
2. Faceted category URLs multiply, and agents lose the canonical product.
3. Option pickers need a script before the price updates.

What we check: Canonical links, product structured data, links from your home page to key pages, and delivery terms in text.

### Magento

Common problems:

1. Configurable products show the final price only after an option is chosen.
2. Layered navigation creates thousands of near-duplicate pages.
3. Heavy pages time out before an agent finishes reading.

What we check: Page load for automated visitors, canonical links, structured data and whether key facts are in the page text.

### Shopware and PrestaShop

Common problems:

1. Cookie consent walls cover the whole page until someone clicks.
2. Prices change by country or customer group, so agents see a different total.
3. Delivery and returns sit in footer pages that aren't linked from products.

What we check: What the page shows before any click, prices in structured data, links to your policy pages, and robots.txt.

### Wix and Squarespace

Common problems:

1. Product details load with scripts, so the first page read is nearly empty.
2. Product structured data is thin or missing variant prices.
3. Policies live in pop-ups instead of their own pages.

What we check: Page text before scripts run, structured data, policy pages and whether AI crawlers are allowed.

### Headless

Common problems:

1. Content renders in the browser only, so agents that don't run scripts see an empty page.
2. Structured data is missing because the old theme used to add it.
3. Client-side routing hides links agents need to move between pages.

What we check: What the page text contains before scripts run, links between pages, structured data and your AI-facing files.

### Custom-built

Common problems:

1. Prices or stock come from an API call after the page loads.
2. Firewall rules written for scrapers also block AI agents.
3. Policies sit in PDFs that agents don't open.

What we check: Everything a shopper's agent needs from your public pages: reachability, page text, links, structured data and policies.

## Headless stores

If your front end renders in the browser, an agent that doesn't run scripts may see an empty page. We show you what it really gets.

- Next.js
- Nuxt
- Remix
- Astro
- Medusa

## Built it yourself?

If it serves pages to a browser, we can test it. No integration, no access to your code or admin.

## Also works with

- VTEX
- Webflow
- Square

## See what agents see on your store.

Whatever it runs on, your first result takes about a minute.

[Request a demo](https://aiscovery.io/demo)

Platform names and logos belong to their owners. Aiscovery is not affiliated with them; we test any store from the outside.

---

This is the Markdown version of the page for AI agents. The HTML page at the canonical URL is authoritative. Site index: https://aiscovery.io/llms.txt