Content Moved? Use Search to Locate
Close-up of the Google homepage on a screen showing search options.

Google’s Merchant Listings Update: A WooCommerce Audit Checklist

BySplinternet Marketing

Google updated its Merchant listing structured data documentation on July 7, 2026. The update is not evidence of a new ranking factor. It is a useful implementation prompt for WooCommerce teams managing prices, sales, shipping, returns, and product markup across several systems.

The main risk is data drift. A sale price can be correct in WooCommerce but stale in JSON-LD. Shipping terms can be accurate at checkout but incomplete in markup. A product page can also publish conflicting Product or Offer entities through WooCommerce, an SEO plugin, a theme, a feed integration, or custom code.

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

Audit pricing and offer data first

Google currently distinguishes three pricing states:

  • Active price: the price currently offered to shoppers.
  • Strikethrough price: the higher regular price shown alongside a sale price.
  • Member price: a price available to a defined loyalty or membership tier.

Review a representative set of products and compare the visible page, source HTML, JSON-LD, cart, and checkout. Confirm the active price, regular price, currency, availability, SKU or other identifiers, and any variation-specific offer data.

Do not mark the active price as a strikethrough price. Google also says that a price specification containing both priceType and validForMemberTier is ignored. If your store supports member pricing, confirm that the public price and member price are represented as separate, understandable price specifications.

Scheduled sales deserve a separate check. WooCommerce lets administrators set sale start and end dates, while Google recommends ISO 8601 dates with time and timezone information where practical. Review validFrom, validThrough, and priceValidUntil for expired dates, incorrect timezones, and values that do not match the storefront.

Check shipping, returns, and rendering

Compare shipping markup with the actual customer experience. Check destination coverage, shipping cost, handling time, and transit time. Variable products can have different shipping settings, prices, stock states, and SKUs, so testing only the parent product may miss a variation-level problem.

For a standard policy that applies to most products, Google recommends placing shipping and return policy information under Organization markup. Use offer-level shipping or return properties when a product needs an override or when there is no standard business-wide policy. In either case, the markup should reflect the published policy and the process your team can actually fulfill.

Also check how the markup is delivered. Google recommends putting Product structured data in the initial HTML for merchants optimizing for shopping results. Google warns that JavaScript-generated Product markup can make shopping crawls less frequent or reliable, which matters when prices or availability change quickly.

What to do next

  1. Trace every system that emits Product and Offer markup before editing individual templates.
  2. Test one simple product, one scheduled-sale product, one variable product, one member-price product if applicable, and one product with special shipping or return rules.
  3. Compare the visible offer, JSON-LD, cart, checkout, and any Merchant Center feed values.
  4. Run the Rich Results Test and inspect deployed examples with Search Console’s URL Inspection tool.
  5. Review the Merchant listings and Product snippets reports under Shopping. Search Console explains that these reports show samples of detected structured-data items, not a complete inventory of every URL.
  6. After deployment, monitor representative URLs through the next crawl and indexing cycle. If valid items fall or invalid items rise, inspect the shared template, plugin, feed, or extension that generated the change.

Start with expired sale dates, mismatched currencies, incorrect active-versus-strikethrough pricing, variation-level differences, incomplete shipping details, and stale return policies. Fixing the data source is usually more durable than adding another schema plugin or patching product pages one at a time.

Sources

Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.

This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.

Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.

Related Posts

Splinternet Marketing