Check and correct structured data for a simple WooCommerce product

Check a simple WooCommerce product's public product data, correct only inaccurate source fields, and retest the page's structured data.

• Outcome: Technical SEO
• Tools: Woocommerce, Google Rich Results Test
• Responsible: WooCommerce store owners or editors who can update a product and check its public search data
• Estimated time: 15 minutes

Scope

This SOP covers:

• Inspect one public WooCommerce Simple product and its currently recognized Product structured data
• Compare the product name, main image, current offer price and currency, availability, and URLs with the real product information
• Correct source fields WooCommerce controls, retest after a change, or hand an output conflict to the site maintainer

This does not cover:

• Variable products with selectable options, grouped products, external products, subscriptions, or other extension-specific product types
• Writing custom schema code, installing or switching schema plugins, or changing theme/plugin output
• Google Merchant Center feeds, full shipping or return-policy setup, and any promise that Google will show a special result

Requirements

• The complete public URL of one product page with no selectable product variations
• Permission to open and update the selected product in WooCommerce
• A trusted source for the product's true name, main image, current price and currency, and actual availability

Related SOPs

• SOP 066: Test a page's structured data with Google's Rich Results Test

01. Inspect the public product output

Structured data is product information written for search tools to read. WooCommerce can create it automatically. First see what the public page reports; keep an accurate existing result instead of adding another.

1. In WordPress, open Products > All Products and edit the product for the URL you will test. Confirm its product type is Simple product and that customers do not choose a size, color, or other variation before buying. Keep the full public product URL for the test.

   • Warning: A product with selectable sizes, colors, or other options is a Variable product. Its price and identifier output needs a different method, so record the URL and ask the site maintainer for that route.
   • Resource: WooCommerce product types and editor settings (Confirm what WooCommerce calls Simple and Variable products and where their source fields live.)

2. Create a short note titled Structured data check in the product's work record. If there is no work record, use the plain-text place where your team tracks website changes. Add the complete public product URL and today's date so you can compare the same page after saving.

3. In the Structured data check note, open Google's Rich Results Test, choose URL testing if prompted, enter this public product URL, and start the test. Record each Product feature section, its status and issues, and the name, image, price and currency, availability, and URL shown there. Keep the test result beside the visitor-visible product page.

   • Warning: WooCommerce creates product data automatically, but an SEO plugin, theme, or another extension can also add or change Product data. The result shows the page's current output; it does not identify its source by itself.

4. Use the detected Product item and the page contents to choose the next path for your note:

   1. If the test reports one matching Product in each Product feature section shown, and its important values match the real offer, keep the output. Google may show Product snippets and Merchant listings as two sections for this same product; those two sections alone are not duplicate Product data. Write No correction needed now unless a specific required issue remains.

   2. If a value is missing or differs from the real product, copy the exact value and issue into the note, then compare the WooCommerce source fields in the next milestone.

   3. No Product data. If the test loads the page but finds no Product data, record it and continue to Check the WooCommerce product fields below. Compare every listed field with trusted product details even though Google supplied no values; correct any confirmed blank or wrong source field, then save and test the same URL. If the fields are already complete and accurate, or the retest still has no Product item, ask the site maintainer which component should create it.

      Repeated Product data. If one feature section repeats the same Product, record it and ask the site maintainer to trace that source, even if other sections also show Product data. Product snippets and Merchant listings can each show one matching Product for the same product; that alone is not a repeat. Do not install, switch off, or replace a plugin.

02. Check the WooCommerce product fields

Correct a field only when the product owner or store record confirms the current source value is wrong. The public page and its test data should describe the same offer.

1. In the product editor, compare the Product name, Product image, Product data, and public permalink with Structured data check and your trusted product details. If the test found no Product item, still check these source fields against the trusted details even though Google supplied no values. Use the trusted details when the existing page or editor may be wrong.

   • Warning: If you cannot confirm the correct business value, keep the current field and ask the product owner instead of guessing.
   • Resource: WooCommerce Product Editor settings (Find the product name, General pricing, Inventory, and saved product controls.)
   • Resource: WooCommerce product images and galleries (Identify the main Product image separately from extra gallery images.)

   1. Compare the test's Product name with the WooCommerce Product name and the page's main product heading. If the store record confirms the title is wrong, correct the Product name so it identifies the item accurately.

   2. Compare the test's main Product image with the WooCommerce Product image and the picture visitors see first. If it is missing or shows another item, select the accurate main product image. Gallery images are additional views; changing their order does not by itself change the main Product image.

   3. In Product data > General, compare the Regular price and any active Sale price with the real current offer. If a price is wrong, update that source field only. WooCommerce's currency comes from the store's currency setting; check WooCommerce > Settings > General > Currency options if the symbol or currency is unexpected.

      • Warning: If tax, location, or a currency extension makes the public price vary by visitor, do not change shared currency or tax settings to force a match. Record the test value and ask the store owner which offer should be represented.
      • Resource: WooCommerce shop currency (Confirm where the store's base currency is selected and how it affects product prices.)

   4. In Product data > Inventory, compare the Stock status with the real stock record. If Manage stock is enabled, check its Quantity too. Correct availability only to reflect whether customers can buy the item now, including a real backorder policy.

   5. Compare the Product URL and Offer URL in the test with the public product page after it finishes loading. If they point to another product, or the page redirects somewhere unexpected, record both addresses and ask the site maintainer to trace the permalink or output source. Do not change an established product URL just to silence a test result.

2. Read review, rating, and product-identifier messages against the guide for the detected Google product feature. Add a value only when the store has a real source for it.

   • Resource: Google product snippet requirements (Check current product name, offer, review, rating, and recommendation requirements.)
   • Resource: Google merchant listing requirements (Check which product information applies to pages where customers can buy the product.)

   1. If the product has no real customer reviews, do not create a review or rating to remove a message. For product snippets, Google allows an offer as an alternative to review or aggregate-rating data, though the test may still show a review recommendation. Record that the store has no reviews and leave the absent data out.

      • Resource: Google product snippet requirements (Confirm the documented offer alternative and review-data guidance.)

   2. If an identifier warning appears and the manufacturer supplied a GTIN or barcode for this exact product, enter that verified value in Product data > Inventory > Global Unique ID if the field is available. A store's SKU is a different code; do not copy it into the GTIN field. If no true identifier is available, leave the field empty and note why.

      • Resource: WooCommerce GTIN field documentation (Locate WooCommerce's built-in Global Unique ID field used for GTIN data.)

   3. If accurate reviews are visible but missing from the test, or a message asks for a value WooCommerce does not provide in this product editor, record it and ask the site maintainer which active product-schema source handles it. Do not add custom fields or a second schema generator as a workaround.

03. Save and check the final product page

After changing verified product data, confirm it saved and check the same public URL again. Keep a correct page unchanged.

1. If you corrected any product fields, select Update and wait for the save to finish. Reopen the product and confirm that each corrected name, image, price, currency, inventory state, or Global Unique ID was saved. If no source field needed correction, leave the product unchanged.

2. If you changed a source field, open Google's Rich Results Test, choose URL testing if prompted, and test the same public product URL again. In Structured data check, compare the new Product item and issue messages with the saved source fields and current public page. If a corrected value is still missing or an item remains repeated, hand the exact URLs, field, and test message to the site maintainer.

   • Warning: A passing test means the page may qualify for a supported Google feature. Google decides whether to show an enhanced result.