Learning Center

Practice store: broken and fixed

Harbor & Ridge is the demo store we test AI agents against. Here are its product and checkout pages built two ways: one with 4 problems we often find on real stores, and one with each fixed. Every problem still works for a person with a mouse, which is why they reach production unnoticed.

Open both versions

Both look much the same in a browser. Try each with a keyboard only, or with a screen reader, and the differences show at once. That's close to how an AI agent experiences them.

1. The price only appears after JavaScript runs

What an agent sees: An agent that reads the page without running scripts finds an empty price box, and there's no product data in the page to fall back on. It can't tell what the jacket costs.

The fix: Put the price in the HTML the server sends, and add Product structured data with the price, currency and stock for each option.

Broken
<div class="price" id="price">
</div>
<script>setTimeout(function(){document.getElementById("price").textContent="$89.00"},150)</script>
Fixed
<div class="price" data-price>$89.00</div>

AgentScore flags this as "Product pages give price and stock in a form agents can read" and "Content loads without JavaScript". Read the guide to fixing it.

2. Size and colour are clickable boxes, not form controls

What an agent sees: The swatches are plain boxes with a click handler. An agent doesn't see a choice to make, and the colour swatches have no text at all, so it can't tell blue from black.

The fix: Use real form controls: a select or radio buttons, each with a visible label and the option's name as text.

Broken
<div class="option">
<div class="option-name">Size</div>
<div class="swatches">
<div class="swatch" data-option="Size" data-value="XS">XS</div>
<div class="swatch" data-option="Size" data-value="S">S</div>
<div class="swatch" data-option="Size" data-value="M">M</div>
<div class="swatch" data-option="Size" data-value="L">L</div>
<div class="swatch" data-option="Size" data-value="XL">XL</div>
</div>
Fixed
<fieldset>
<legend>Size</legend>
<label>
<input type="radio" name="Size" value="XS" required> XS</label>
<label>
<input type="radio" name="Size" value="S" required> S</label>
<label>
<input type="radio" name="Size" value="M" required> M</label>
<label>
<input type="radio" name="Size" value="L" required> L</label>
<label>
<input type="radio" name="Size" value="XL" required> XL</label>
</fieldset>

AgentScore flags this as "Clickable things are real buttons and links". Read the guide to fixing it.

3. Add to cart is an icon with no name

What an agent sees: The button is a box with a cart picture and a click handler. An agent finds nothing called "Add to cart" on the page, so it can't buy.

The fix: Use a real button with the words "Add to cart" on it, or at least an accessible name.

Broken
<div class="atc" onclick="document.getElementById('add-form').requestSubmit()">
<svg>…</svg>
</div>
Fixed
<button type="submit">Add to cart</button>

AgentScore flags this as "Buttons and links have names" and "Agents can find and press your add-to-cart or sign-up button". Read the guide to fixing it.

4. Checkout fields have no labels

What an agent sees: The words next to each box aren't tied to it, and the fields are named f1, f2, f3. An agent filling in the form has to guess which box takes the email and which takes the postcode.

The fix: Give every field a label tied to it, a meaningful name and an autocomplete hint, such as autocomplete="email".

Broken
<div class="field">
<div>Email</div>
<input name="f1">
</div>
Fixed
<label for="email">Email</label>
<input id="email" name="email" type="email" autocomplete="email" required>

AgentScore flags this as "Cart and checkout fields are labelled for agents" and "Form fields are labelled". Read the guide to fixing it.

Check your own site

The same problems are among the most common we find. See the statistics for how often, or run a free AgentScore scan to find out whether your store has them.