Skip to content
Proofline

AI visibility for US online stores

Can AI assistants see your products?

Shoppers now ask ChatGPT, Perplexity and Google's AI answers which store to buy from. Proofline checks whether those assistants can actually read your products and prices, and shows you the stored evidence behind every claim.

Get your free audit See a sample Proof Page

For owners and e-commerce leads of US stores with 10 to 250 employees. Public pages only. Nothing to install.

Scan complete · 6 findings · 3 checks could not run 2 Oct 2026 · 09:13–09:16 UTC

AI visibility

Accessibility

Proof Page ready · every finding links to its evidence Open the Proof Page
Example Findings anonymized and combined from audits of US home-furnishings stores, October 2026. Store name, paths and times are placeholders.

01 · The audit

How it works

Three pages, a set of checks, and a page you can forward. Every claim on it carries the evidence it came from.

  1. Step 1

    You send a store URL

    We pick three pages: home, a category and a product. We fetch them the way an assistant's crawler does: a plain request first, then a real browser. We respect robots.txt, never log in and never place an order.

  2. Step 2

    Every check keeps its evidence

    Each check stores what it saw: the response, the rendered page, the date and time. A finding without evidence is marked unverified and is never shown to you as fact.

  3. Step 3

    You get a Proof Page

    One private link with every finding, the evidence behind it, and what the fix takes. No PDF, no slide deck, nothing to install.

A Proof Page, as you would see it

Example
Prepared for store.example

What I found on store.example

On 2 October 2026 I checked store.example. The pages I looked at: the home page, a category page and a product page. Here's what I found.

At a glance

  • The category page shows 0 of 36 products without JavaScript.
  • The product page has no machine-readable price.
  • A plain automated fetch got a bot-challenge page, so three checks could not run: robots.txt, sitemap and llms.txt. I list them rather than guess.
  • Automated accessibility checks fail on the home and category pages.

AI visibility

high Exhibit 1 Products visible without JavaScript

Category page shows 0 of 36 products without JavaScript

An assistant that reads the plain response gets an empty category. I counted 0 products in the HTML response and 36 after rendering, which is what a shopper's browser shows.

Technical details
https://store.example/collections/sofas 2 Oct 2026
high Exhibit 2 Product data for assistants

No machine-readable price on the product page

The page carries one block of structured data, and it describes the company, not the product. An assistant that relies on it has no price and no availability to quote.

Technical details
https://store.example/products/linen-sofa 2 Oct 2026
high Exhibit 3 Automated requests blocked

A plain automated fetch got a bot-challenge page, so checks could not run

The first request, made without a browser, was answered with a challenge page instead of the store. Checks that read plain responses could not run. The rendered checks did.

Technical details
https://store.example/ 2 Oct 2026

Accessibility

high Exhibit 4 Automated accessibility scan

Automated accessibility checks fail on the home and category pages

WCAG 2.1 A and AA rules, run with axe-core. The product page could not be confirmed as a product page, so I did not check it rather than guess.

Technical details
https://store.example/ https://store.example/collections/sofas

color-contrast × 14, image-alt × 9

2 Oct 2026
medium Exhibit 5 Accessibility overlay widgets

Two accessibility overlay widgets load on every page checked

An overlay does not change the HTML that an assistant or a screen reader reads. I flag it so you know what it does and does not do. I do not sell one.

Technical details
https://store.example/ 2 Oct 2026
Checked and fine
  • A skip-to-content link is present on every page checked

Automated scan of the pages checked, 2 October 2026, with axe-core 4.10 and HTTP-level checks. Automated checks find a part of the issues, not all of them. Three checks could not run and are listed as such, not guessed.

This is an example. The findings are anonymized and combined from real audits. The store name, paths and times are placeholders.

02 · Why both

An AI assistant reads your store the way a screen reader does.

Neither of them looks at the page. Both read what is underneath: the HTML your server sends, the labels on controls, the product data in the markup. When a category is empty until JavaScript runs, a shopping assistant sees nothing, and so does a customer using a screen reader. When a price exists only as pixels, neither can read it. The fixes overlap, so one round of work moves both.

One fix, two readers
What your store needs For an AI assistant For a screen reader
Products listed in the HTML Reads the catalog Hears the catalog
Price and availability in the markup Can quote a price Has a price to announce
Labeled buttons and form fields Tells “Add to cart” from “Save” Announces what each control does
Text alternatives on product images Knows what the image shows Hears what the image shows

An accessibility scan comes with it

Alongside the AI checks we run an automated accessibility scan (WCAG 2.1 A and AA, with axe-core) on the same pages. In the US, store accessibility is discussed in the context of the ADA. We report what the scan found and what it could not check. It finds a part of the issues, never all of them, and it is not legal advice.

Overlays are something we flag

If an accessibility overlay widget loads on your pages, it shows up on your Proof Page. An overlay does not change the HTML that an assistant or a screen reader reads. We do not sell one, and we do not recommend one.

03 · Free audit

Get your free audit

Send your store URL. You get a private Proof Page with every finding, the evidence behind it and what a fix takes. No account, nothing to install, no obligation.

By sending this you agree that Proofline may use your e-mail address to send you this one audit and to reply to this request. No newsletter, no marketing e-mail. Privacy

Or write to andrew@asytnyk.com

We check public pages only, respect robots.txt, never log in and never place orders. What our crawler fetches, and how to opt out, is public.

Get your free audit

Send your store URL and work e-mail. You get a private Proof Page with every finding and the evidence behind it.

By sending this you agree that Proofline may use your e-mail address to send you this one audit and to reply to this request. No newsletter, no marketing e-mail. Privacy