Google Search Central: Let's Talk Shopping Markup

Google Search Central takes on shopping markup in this episode, exploring how product structured data affects how your products appear across Google's various search and shopping surfaces. The Search Off the Record team discusses what markup Google actually uses, common implementation issues, and the evolving relationship between organic search and shopping experiences.

Watch the full video: Let's talk shopping markup

What the Episode Covers

The episode starts by distinguishing between product structured data for organic search and Google Merchant Center feeds for Shopping ads and free listings. While they serve different purposes, they increasingly overlap. Product markup on your pages can surface rich results in organic search — including price, availability, review ratings, and shipping information — without requiring a Merchant Center account.

The core product schema properties discussed include name, description, image, price, currency, availability, brand, SKU, and aggregate ratings. Google uses these to generate product rich results, which appear as enhanced listings with visual elements that stand out from standard blue links.

The team emphasizes that accuracy is non-negotiable. If your markup says a product is in stock but the page shows it as out of stock, Google may stop showing rich results for your site entirely. The structured data must match the visible page content exactly. This is not just a technical requirement — Google actively validates markup against page content.

They also cover the merchant listing experience, which is a newer search feature that lets users browse multiple products from a retailer directly in search results. This requires both correct product markup and enrollment in Google Merchant Center's free listings program. The combination of structured data and Merchant Center provides the broadest possible visibility across Google's shopping surfaces.

Key Takeaways

1. Price and availability must be current. Stale pricing data is the fastest way to lose product rich results. If your prices change frequently, your structured data needs to update in sync. Dynamic rendering of structured data based on real inventory and pricing APIs is the reliable approach.

2. Use the Product schema, not just Offer. The full Product schema includes properties for brand, SKU, GTIN, and other identifiers that help Google match your product to its broader product knowledge graph. More complete markup gives Google more confidence in displaying rich results.

3. Review markup requires real reviews. The AggregateRating property should reflect genuine customer reviews on your site. Using fabricated or misleading review counts is a structured data abuse violation that can result in manual actions.

4. Test with the Rich Results Test tool. Before deploying product markup to production, validate it using Google's Rich Results Test. This tool shows exactly what Google can extract from your markup and flags any errors or warnings. The Search Console enhancement reports then monitor ongoing compliance.

5. Shipping and return information enhances listings. Newer product markup properties for shipping cost, shipping time, and return policies can appear in rich results. Adding these properties makes your listings more informative and competitive against other results.

Beyond the Basics

The episode raises an important architectural question: where should product structured data live? For static product pages, embedding JSON-LD in the page template is straightforward. For dynamic catalog sites with thousands of products, generating accurate structured data at scale requires integration with product information management systems or e-commerce platform APIs.

The team also discusses the role of structured data in the broader product search ecosystem. Google Shopping, Google Images, Google Lens, and organic search all consume product markup differently. A well-implemented product page with comprehensive structured data can surface across multiple Google properties simultaneously, multiplying visibility without additional effort.

One practical consideration they highlight is variant handling. Products that come in multiple sizes, colors, or configurations need careful markup. Each variant should have its own Offer with accurate pricing and availability, nested within the parent Product. Incorrect variant markup is one of the more common issues found in structured data audits.

The conversation also touches on competitive dynamics. As more retailers implement product markup, the bar for visibility rises. Sites without structured data lose ground in search results because they cannot display the enhanced listing formats that users have come to expect. What was once a nice-to-have has become a baseline requirement for e-commerce visibility.

What This Means for Your Business

If you sell products online — or even display product information for lead generation — shopping markup directly affects how your offerings appear in search. Rich product results with pricing, ratings, and availability get significantly more attention than plain text listings.

For service businesses that offer packaged solutions or software products, product markup may still apply. Anything with a defined offering, price point, and description can potentially benefit from product schema implementation.

At Demand Signals, our WordPress Development and React / Next.js teams implement product structured data as part of the site build process. Combined with our LLM Optimization strategies, we ensure your products are visible not just in traditional search but across the expanding landscape of AI-powered shopping and discovery surfaces.