Toronto: 905-626-3857 Calgary: 403-456-6224

WooCommerce Product Pages for AI Shopping: Fix Your Product Data Before the Holiday Rush

by Paradigmmedia | Oct 14, 2026 | eCommerce

A shopper types a question: "Will a 1 L insulated flask fit my car's cup holder, and can it arrive before December 23?"

Your product page says: "Perfect for any adventure. Keeps drinks hot or cold all day."

That copy answers neither half of the question. It gives no size, no material and no delivery facts. A person will leave and look elsewhere. A search tool or shopping assistant has nothing to quote, so it will favour a page that does.

Vague copy fails because shoppers ask for facts. This guide helps you choose five important products, find the missing facts, and hand your developer a ranked list of fixes. No markup, feed or description can guarantee that a product appears or sells. Accurate data gives every system something correct to work with. Shopping tools gather product information in different ways, so aim for accuracy everywhere your data lives.

This guide assumes you already run WooCommerce. If you are still choosing a platform, start with our post on choosing an eCommerce solution.

Four places your product data lives

  1. The visible product page. What shoppers read.
  2. WooCommerce product fields. The settings behind the page: price, stock status, SKU (your internal stock code), attributes, variations (versions of one product, such as size or colour), weight and dimensions.
  3. Structured data. Code, usually in a format called JSON-LD, that labels facts for machines. It says "this number is the price" and "this text is the brand."
  4. A merchant feed. A file or sync that sends product data to Google Merchant Center, the tool where you manage how your products appear across Google.

These four should agree. They drift apart easily. You set a sale price on Monday. A caching plugin keeps serving the old page. An SEO plugin prints the regular price in the markup. The feed refreshes on its own schedule. Now you have four versions of one price.

Google's Merchant Center product data specification says prices, availability and product details must match your landing page, checkout and structured data. Mismatches can cause disapprovals or display problems.

The facts every product needs

  • A clear name: product type, brand, model and the feature that sets it apart. One product, one page.
  • Brand, plus a GTIN (the barcode number, such as a UPC or EAN) where one exists. Take it from the supplier's packaging or paperwork. If the maker assigns a part number (MPN), use that. Never invent either. Google states that a product submitted with an incorrect GTIN will be disapproved. If a product has no GTIN, leave the field blank. WooCommerce's Google extension FAQ advises this too.
  • Attributes and variations. Size, colour, capacity, with a distinct SKU, image and stock count for each variation.
  • Dimensions, weight and material. Use units your customers use, and say the units.
  • What it fits, works with or replaces.
  • Price in CAD, and availability. Match your actual stock.
  • Shipping and returns. You supply these facts. Nobody can infer them for you. State your carrier, cost, handling time, delivery estimate and return window. Google's free listings requirements name Canada among the countries where shipping settings are required, and ask for return policy information on your website.

WooCommerce's own product description guidance points the same way: lead with product type and key specifications, and

Before and after: an illustrative example

Northern Hearth Goods is an invented Ontario retailer. The Trailhead Flask is an invented product. Every specification below is illustrative.

Before

Our best-selling flask keeps drinks hot or cold all day. Perfect for any adventure. Available in several colours.

After

Trailhead Insulated Flask, 750 mL and 1 L, double-wall stainless steel

  • Material: 18/8 stainless steel body, powder-coated exterior (illustrative)
  • Capacity: 750 mL or 1 L (illustrative)
  • Dimensions: 1 L model is 8.2 cm wide and 29 cm tall (illustrative)
  • Fits cup holders up to 8.5 cm wide (illustrative)
  • Lid: top-rack dishwasher safe. Body: hand wash only (illustrative)
  • Colours: Forest, Slate, Cream. Each colour has its own SKU and photo
  • Price: shown in CAD per variation
  • Shipping: [merchant supplies carrier, cost, handling time and delivery estimate]
  • Returns: [merchant supplies window, condition and who pays return shipping]
  • GTIN: ©

The second version answers the opening question. It also gives your developer exact fields to check.

Product, Offer markup, and Merchant Center

In structured data, a Product describes what the item is. An Offer describes how to buy it: price, currency and availability.

Google's merchant listing guidance requires a name, an image, and an offer with a price and currency. It recommends availability, shipping details, return policy, identifiers and brand. Only pages where a shopper can buy the product are eligible. Google's product structured data page adds that enhancements appear at the discretion of each experience and may change.

Eligibility is not guaranteed display. Google says the same about Merchant Center. Its free listings page states that approval to show products does not guarantee they will be shown. Free listings cover surfaces including Search, Shopping and Gemini, and surface availability can change.

Merchant Center's Diagnostics section lists problems by severity. Fix the ones that stop products from serving first.

One warning for WooCommerce stores. Your theme, an SEO plugin and WooCommerce itself may each print Product markup on the same page. Conflicting blocks send mixed signals. Check how many appear, choose one source of truth, and switch the others off. If you use Google's official WooCommerce extension, it syncs from your product fields, so fix the fields first.

A six-step audit

  1. Select five products. Pick top sellers, high-margin items, products with variations and products customers ask about most.
  2. Reconcile fields and feeds. Fill in the worksheet below for each product.
  3. Validate structured data. Run each product URL through Google's Rich Results Test. Count the Product blocks. Check price, currency and availability.
  4. Check diagnostics. Open Merchant Center Diagnostics and note issues on your five products.
  5. Test variants. Select every variation. Confirm that price, stock, image and SKU change on the page and in the markup.
  6. Review checkout. Confirm that price, shipping cost, taxes and return wording match what the product page promised.

A reusable catalogue-quality worksheet

Copy one table per product. Mark any row where the four sources disagree.

FieldVisible pageWooCommerce fieldStructured dataFeedMatch?
Product name
Price (CAD)
Sale price and dates
Availability
Variant options and SKUs
Brand
GTIN or MPN
Material
Dimensions and weight
Compatibility
Shipping cost and timing
Return terms

Prioritized correction

IssueCustomer impactWhere to fixHow to verify
Price or stock differs between page, markup and feedShopper sees one price and pays another. Listings may be disapproved.Product fields, caching, SEO plugin settings, feed syncWorksheet shows four matching values after the cache is cleared
Shipping and returns missing or vagueShopper cannot judge cost or deadline.WooCommerce shipping zones, Merchant Center shipping settings, returns pageTest checkout to two provinces. Wording matches the page.
Variants share one description or imageShopper cannot tell which size or colour they get.Variations tabSelect each variation and confirm the page and markup change
More than one Product markup blockMixed signals about the same item.Theme, SEO plugin, WooCommerce settingsPage source shows one Product block
Invalid or invented identifiersProduct disapproved.Product fields, feedValues match supplier packaging. Diagnostics clear.
Missing material, size or compatibilityCommon questions stay unanswered.Product description and attributesA stranger can answer your opening question from the page alone

A two-week plan

Week 1. Days one and two: choose five products and fill in the worksheets. Days three and four: gather shipping and returns facts from your own policies, then correct identifiers and fields. Day five: remove duplicate markup.

Week 2. Days six and seven: fix variations. Days eight and nine: validate markup and clear the Diagnostics issues you can. Day ten: run a full test purchase on each product. Then set a calendar reminder to recheck after your first holiday sales week.

BOOK A FREE CONSULTATION

Need help clarifying your shopping cart database to enhance your product pages and improve AI search?

Request a product catalogue and feed audit

Paradigmmedia builds and maintains WooCommerce stores for businesses in Toronto, Calgary and across Canada. No audit can promise placement or sales. A catalogue and feed audit gives you a ranked list of corrections your store can act on before the holidays. Our GEO guide for small businesses explains the wider search context.

Frequently asked questions

Does every AI shopping tool require structured data?

No source says so. Tools gather product information in different ways. Google lists Product and Offer markup to become eligible for its merchant listing experiences. Accurate markup helps machines read your page and gives no guarantee of display.

What should I do if my product has no GTIN?

Leave the field blank and provide the brand and, where the maker (is this marker) or maker)assigns one, the MPN. Never create a number. Google's specification says incorrect GTINs lead to disapproval.

How long should a product description be?

As long as it takes to answer a buyer's questions. WooCommerce's guidance says to aim for completeness and not worry about word count.