Product Schema Missing Field Errors: How to Fix Them

This guide explains every common product schema missing field message in Search Console, which ones actually stop your products appearing as rich results, and how to fix them on any platform.

Are missing field warnings in Search Console a problem?

Missing field warnings are usually not a serious problem, because Search Console separates critical issues, which make an item invalid, from non-critical issues, which only limit how it can appear. The rich result report help page says a valid item has no critical issues and can appear on Google as a rich result, and that non-critical issues are listed separately under “Improve item appearance”.

So the first step is always the same: open the report and check whether the item is listed as invalid or valid with warnings. A store with hundreds of “missing field” warnings and zero invalid items does not have an emergency. A store with even a few invalid items does.

It also helps to know where the messages come from. Google reads whatever Product markup your theme, plugin or app outputs. Most platforms output a basic set of fields by default, and the warnings simply list the recommended fields that basic set leaves out. That is why two stores on the same theme often see exactly the same list of warnings.

In my client audits, many store owners panic over warnings their theme or plugin will never fill, while a genuine critical error, such as a missing price on variant products, sits unnoticed in another report.

Which Product fields are required and which are optional?

Google has two Product rich result types with different requirements: merchant listings for pages where people can buy from you, and product snippets for pages such as reviews and comparison sites. Google’s merchant listing documentation lists name, image and offers as required Product properties, and price plus priceCurrency as required inside the offer.

The product snippet documentation requires name plus at least one of review, aggregateRating or offers. It also notes that the Merchant listings report already covers product snippets that include offer markup, so the Product snippets report mainly matters for non-merchant pages.

This table covers the fields that most often appear in missing field messages.

How do I fix missing field priceValidUntil?

Fix a missing priceValidUntil warning by adding the date a price ends only when the price really has an end date, such as a sale; for a normal ongoing price you can leave the warning, because the field is recommended rather than required. Both Google documents list priceValidUntil as a recommended Offer property.

The bigger risk is the opposite mistake. Google warns that a listing may not display if priceValidUntil shows a date in the past. Some themes and plugins once filled this field with a fixed date one year ahead, which later expired and quietly made products ineligible. If your markup contains an old hard coded date, either update it dynamically or remove the field.

1. Run a product URL through the Rich Results Test and find the priceValidUntil value.
2. If the date is in the past, fix the template or plugin setting that writes it.
3. If it is a regular price with no end date, consider leaving the field out.
4. For sales, output the real sale end date in ISO 8601 format, for example 2026-12-31.

What does missing field shippingDetails mean?

Missing field shippingDetails means your Offer markup does not say how much shipping costs or how long delivery takes, which Google uses to show shipping information in merchant listings. It is a recommended field, so the product remains valid without it.

Google’s merchant listing documentation recommends defining your standard shipping and return policies once under Organization markup and using the Offer level shippingDetails and hasMerchantReturnPolicy properties only to override them for specific products, or when you have no standard policy. For most stores, that is far easier than repeating the same shipping block on thousands of product pages.

If your platform cannot output Organization level policies, a shipping app or SEO plugin that adds shippingDetails per offer is the alternative. In that case, test a product in every shipping zone you serve, because a single default rate applied to all countries is a common source of wrong delivery prices in markup.

Whichever method you use, the values must match what customers see at checkout. Markup that claims free delivery when the cart adds a fee is inaccurate, and inaccurate structured data is worse than none.

What does a real fix look like on a store?

How do I validate the fix in Search Console?

Validate a structured data fix by testing a few URLs in the Rich Results Test, deploying the change, then clicking Validate fix in the relevant Search Console report. Google rechecks the affected items over the following days or weeks.

• Test a simple product, a variable product and a sale product, since they often use different template paths.
• Use URL Inspection to see whether Google’s indexed version already includes the new markup.
• Remember that fixes must be made in your site’s source code, theme or plugin; the report only reflects what your pages output.
• Check that the markup matches the visible page: price, currency, availability and reviews.

If several plugins output Product markup at the same time, you can end up with two conflicting Product entities on one page, one complete and one missing fields. Disable duplicate schema output so only one source writes it. Structured data and template fixes like this are part of my technical SEO service, and product markup is reviewed in every e-commerce SEO project. For general structured data practice, the FAQ schema generator shows how clean JSON-LD is laid out, and the content and media SEO page covers rich results more broadly.

Frequently asked questions