How to Fix "Option1: BL" and Other Variants AI Can't Read

When an AI agent reads your product data, it sees your variants as a list of option names, option values, SKUs, and prices. If those option names are "Option1" and "Option2," the agent has nothing to work with.

The signal StoreAudit actually scores here is your option names. An option named Color tells the agent exactly what dimension it's looking at; a generic name like Option2 tells it nothing. StoreAudit flags generic names (Option1, Option2, Option3) and the single-variant default name "Title" — those are the names you want to fix first.

What AI agents see in your variants

Your /products.json feed exposes every product's variants and options. For each product, the agent gets:

• Option names — the labels for each variant axis (e.g., "Size", "Color"). These live in the product's options[].name array.
• Option values — the specific choices (e.g., "Small", "Blue"). On each variant these appear in the option1, option2, and option3 fields — those are value slots, not the option's name.
• SKUs — unique identifiers for each variant
• Prices — per-variant pricing

The option names are the most important part — they're what StoreAudit scores. They tell the agent what dimension each variant represents. A literal name of "Option1" only shows up if a merchant typed it, which is rare; the default StoreAudit flags far more often is the name "Title," which Shopify assigns to products that have no real variants.

Fix your option names

Shopify defaults to "Title" as the option name for products with no real variants. This is fine for single-variant products. But when you have actual variants, use clear, human-readable names:

Instead of	Use
Option1	Size
Option2	Color
Option3	Material

Your option values are worth cleaning up too. StoreAudit doesn't read variant values, so this part isn't directly scored — but it improves how AI matches queries, so it's still good practice:

Instead of	Use
BL	Blue
S, M, L	Small, Medium, Large
01, 02, 03	Cotton, Linen, Silk

AI agents read these option values as plain text. The clearer they are, the better the agent can match them to customer queries — even though it's the option names, not these values, that move your StoreAudit score.

Add SKUs to every variant

SKUs (Stock Keeping Units) are unique identifiers for each specific variant of a product. Many stores leave these empty, but they matter for AI.

AI agents use SKUs to:

• Precisely identify a specific variant in recommendations
• Track inventory and availability accurately
• Match products across different systems and platforms

A good SKU is descriptive and consistent. For example: TSHIRT-BLU-M for a blue medium t-shirt. But even if your SKU system is internal codes, having any SKU is better than having none.

For scoring, StoreAudit looks for SKUs on at least 80% of a product's variants — so a stray blank or two won't sink you, but a product with mostly-empty SKUs will. Digital products are exempt: StoreAudit doesn't expect SKUs on downloads, services, or other non-physical items.

How to check your SKUs

1. Go to Products > Export in Shopify admin
2. Export all products as CSV
3. Open the CSV and check the Variant SKU column
4. Look for empty cells — those are variants without SKUs

How to update variants in Shopify

1. Go to Products in your Shopify admin
2. Click on a product with variants
3. Scroll to the Variants section
4. Click on the option name (e.g., "Option1") to rename it
5. Update each variant's SKU in the variant details
6. Save

For bulk updates, the CSV export/import method works well. Update the Option1 Name, Option1 Value, and Variant SKU columns across all products.

Collections as category signals

A note on scoring: collections aren't part of the Variant & Option Structure score — StoreAudit doesn't read your collection structure. The tips below are general best practice for AI readability, not a way to move this category's points.

Collections tell AI agents how your products relate to each other. A well-organized collection structure helps agents understand your product catalog.

Some tips:

• Use descriptive collection names. "Men's Cotton T-Shirts" is more useful than "Summer Picks."
• Create category-based collections. "T-Shirts", "Pants", "Accessories" — these help AI agents map products to standard categories.
• Use automated collections where possible. Conditions based on product type, tags, or vendor keep collections accurate as you add products.
• Don't rely only on manual collections. Manual collections can go stale as your catalog changes.

AI agents use collection titles and the products inside them to build a picture of what your store sells and how products are grouped. Clear collection names lead to better product recommendations.