E-commerce Stores

Browse online stores by AI visibility score. Read scan findings on bot access, then check product details, prices and delivery terms at the store.

How websites are scored

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD1Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation0Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields0Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states1Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL1Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links0Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

Filters · 1 active

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD1Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation0Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields0Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states1Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL1Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links0Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

1 site

Websites in the directory, with their Good for Bots score. Column headers sort the list.
Site	Category	Score
Dropshipping desde cero dropshippingdesdecero.com Shopify themes, conversion audits, and tools for dropshippers by Alejandro Atienza	E-commerce Stores	View report for Dropshipping desde cero:

Promarks a Pro listing, in gold. Pro never changes a score or a place in the order.What Pro includes

Through a bot’s eyes

About E-commerce Stores

A store can show a beautiful product page while leaving a text reader unsure which price belongs to which variant. Size, colour, stock and delivery conditions often change together. If those relationships disappear from the readable page, an assistant comparing products has an incomplete picture.

Useful product information keeps the offer and its conditions together: what is being sold, in which currency, with which options, and under which delivery and return terms. Structured data can add another description of the product, but the page itself should explain the offer in language a customer can understand.

The scanner reads public pages without placing orders or checking stock. A report built from the homepage and a few sampled pages cannot establish access to every product page. Check the store for the current offer and delivery terms.

What to look for

Use these questions when reading the sites themselves. They are guidance for this category, not additional scoring checks.

Price with its conditions: A price should identify its currency and the item or variant it applies to. Readers also need a clear route to shipping, tax and subscription conditions.
Variants that remain understandable: Size, quantity and configuration should retain their relationship to the product. An isolated list of options can be misleading without the selected offer.
Delivery and return information: Public policy pages let a reader understand the purchase beyond the product description. Check the store's current conditions directly.
Readable product descriptions: Specifications and materials should be text, with labels and units. A photograph of a specification sheet gives a text crawler much less to use.

Frequently asked questions

Does the score mean an agent can buy from this store?

No. The score measures web readability, not checkout automation. We do not place orders or certify purchasing integrations.

Do you verify prices and stock?

No. A report is an observation from a scan, not a live inventory or pricing feed. Confirm the current offer on the store's own website.

Does product structured data guarantee a citation?

No. Machine-readable descriptions can make an offer easier to interpret, but they do not guarantee that an assistant will select or cite the page.

Questions about scores, scans and listings in general are answered in the FAQ.