Why does Google say 'Missing field brand' for my WooCommerce products?

It means your Product structured data doesn't include a brand property. WooCommerce doesn't always output brand by default. Add a brand object to your Product JSON-LD, sourced from your product's brand attribute or taxonomy. It's a recommended field, so it's a warning rather than a hard error, but filling it improves eligibility.

Are Product schema warnings a problem?

Warnings (like missing gtin, brand, or review) won't disqualify a valid item, but they limit how rich your result can be and how confidently AI engines cite you. Errors (like missing name or a malformed offer) can disqualify the rich result entirely and should be fixed first.

Why do I have two Product blocks on one page?

Usually because your theme and an SEO or schema plugin both output Product structured data. Duplicate or conflicting blocks confuse parsers. Disable one source so exactly one Product block is emitted per product page.

Guides / Fix schema errors

How to Fix Common WooCommerce Product Schema Errors

Opened Search Console or the Rich Results Test and found a wall of Product warnings? Here are the errors WooCommerce stores hit most, what each one means, and exactly how to resolve it.

First: errors vs. warnings

Google separates errors (which can disqualify the rich result) from warnings (which limit how rich it can be). Fix errors first, then clear warnings to unlock the full result and stronger AI citation.

“Missing field 'name' / 'offers' / 'image'” (errors)

These are required. A missing name usually means the schema is malformed; a missing offers means price data didn’t render (common on variable products before a variation is selected); a missing image means no product image URL was emitted. Ensure every product has an image and that the offer block always renders with price, priceCurrency, and availability.

“Missing field 'brand'” (warning)

WooCommerce doesn’t always output brand. Add it from your brand attribute or taxonomy:

"brand": { "@type": "Brand", "name": "TrailMaster" }

“Missing field 'gtin' / 'mpn'” (warning)

Add a product identifier. Use the GTIN property matching the barcode length (gtin12 for UPC, gtin13 for EAN), or mpn plus brand when there’s no barcode. Never invent a GTIN. See the identifiers guide.

“Missing field 'aggregateRating' / 'review'” (warning)

Only add these if you genuinely have reviews — never fake them, which violates Google’s policies. If you collect reviews, map them into aggregateRating with a real ratingValue and reviewCount.

Duplicate Product blocks

If two Product blocks appear on one page, your theme and a plugin are both emitting schema. Pick one source and disable the other. Conflicting blocks can cause Google to read the wrong data or ignore both.

Price or availability mismatch

If your schema says InStock at one price but the page or feed says otherwise, Google flags it and may disapprove Merchant listings. The fix is structural: drive page, schema, and feed from one source of truth so they can’t disagree.

Invalid currency or price format

Use a plain decimal for price (89.00, not $89) and an ISO 4217 code for priceCurrency (USD). Currency symbols or thousands separators inside the value trigger validation errors.

How to validate after each fix

Run the URL through Google’s Rich Results Test.
Cross-check with the Schema.org validator.
In Search Console, use the Products enhancement report and click Validate fix after deploying.

Most of these errors come from incomplete or conflicting schema sources. Easy Woo API emits one complete, validated Product block per product — with identifiers, brand, and consistent pricing — so the warnings clear at the source. See the Product schema guide to start.