How it works

It doesn't read your code. It shops.

An agent opens your store in a real browser, adds a product, reaches checkout, and judges what it saw against 115 rules. About three minutes. Nothing installed.

See a sample report first

Audit running nowleatherman.com

Checks AEO

Checks GEO

Visits

Buys

Judges

Ranks by money

Explains the fix

northline.com

NNorthline SupplyCart · 0

New in · heavyweight cotton tees

Heavy cotton tee$38

Merino crew tee$64

Boxy pocket tee$29

northline.com/products/heavy-cotton-tee

Home › Men › Tees

Heavy cotton tee · charcoal★ 4.8 · 212 reviews$38MLXLAdd to cartShipping calculated at checkout

northline.com/cart

Your cart (1)

Heavy cotton teeM · Qty 1$38

Subtotal$38

ShippingCalculated later

Total$38

Checkout

northline.com/checkout

1Information2Shipping3Payment

Full namePhone number

CityContinue to payment

PDP-001Price hidden until you scroll on mobileCRT-001No shipping estimate in the cartCHK-001Guest checkout is not the first option

Sorted by revenue at risk26 findings · top 5

CriticalPDP-001Price visible without scrolling or interaction on desktop and mobile

2 – 5.2% of purchases

MediumPDP-003Add to cart stays reachable on long product pages

0.2 – 0.7% of purchases

MediumPDP-021Q&A or full specifications for considered purchases

0.2 – 0.7% of purchases

MediumPDP-031Touch targets at least 44×44 px on every interactive element

0.2 – 0.7% of purchases

LowPDP-011Product title carries brand and descriptive attributes, not just an SKU

0.1 – 0.4% of purchases

CriticalPDP-001Price visible without scrolling or interaction on desktop and mobile

What we sawOn mobile the price sits below the gallery, a full scroll down. On desktop it is above the fold.

Why it mattersPrice is the first thing a shopper looks for. When it is missing from the first screen, they treat the page as incomplete and leave.

The fixShow the price next to the product name above the gallery on mobile, and pin it with the add-to-cart button.

2 – 5.2% of purchasesEstimate · method published

AEOCan answer engines find your store?Before the visit · 1 of 2

A shopper asks an answer engine“Best heavyweight cotton t-shirt with fast shipping?”

✓Product schema present and validAEO-01

~FAQs readable as text, but no FAQ schemaAEO-04

✕Shipping and returns policy not quotable on the product pageAEO-07

GEOCan an AI agent buy from you?Before the visit · 2 of 2

What the agent sees on the page<span class="price">$38</span> · "availability": "InStock"

✓Price and availability are readable text in the DOM, not an imagePDP-A02

✓Add and buy buttons are real elements with clear namesPDP-A05

✕CAPTCHA gate before checkout with no agent pathCHK-A02

Rules judged115of 115

Score65/ 100

✓52~17✕24

The walk

Four pages, one agent, one score

H01

Opens your homepage

Checks it is a real store, finds a product the way a shopper would.

2reads: scripts off, then a real browser

P02

Reads the product page

Price, shipping, reviews, variants, schema. Adds to cart.

40rules

C03

Opens the cart

Totals, shipping estimate, express wallets, edit and remove.

25rules

K04

Reaches checkout

Walks to the payment step. Card never entered. Nothing ordered.

50rules

Then it judges

103 rules for humans, 12 for AI agents

Every rule is pass, partial, fail, not applicable or not assessable. Rules it could not judge, and rules your store has nothing for, are dropped and never guessed. Each failing rule gets a revenue-at-risk band and a fix.

Browse the rules Methodology

Product page40

Cart25

Checkout50

AI search & agents12

✓ pass~ partial✕ fail · dollars at riskDemo store · illustrative

The proof loop

Find the leak. Fix it. Prove it.

A finding is worth nothing until the score moves. Re-audit the same store and we show which rules flipped from failing to passing.

Watch plans ›

✓9 rules flipped to pass+$1,900–4,200/mo recovered

Illustrative example of a re-audit.

Could not judge, so not scored

If bot protection stops the walk at checkout, its rules are dropped from the score. Never guessed.

Coverage next to every score

You always see how many of the rules actually ran on your store.

Ranges, not point estimates

Revenue at risk is a band, estimated as a percentage of revenue, with the source named.

It doesn't read your code. It shops.

Four pages, one agent, one score

Opens your homepage

Reads the product page

Opens the cart

Reaches checkout

103 rules for humans, 12 for AI agents

Find the leak. Fix it. Prove it.

Could not judge, so not scored

Coverage next to every score

Ranges, not point estimates

Audit my store, free.