A Search Console schema warning means Google read your structured data but found it incomplete for one search feature. Open the affected report, inspect one example URL and find the exact type and property named in the message. Then add that property only if the page visibly shows the information.

Critical issues can stop an item from appearing as that rich result. Non-critical issues usually leave the item eligible, and Google says a warning is not a ranking penalty by itself. So, the first job is sorting your message into one of those two groups.

One rule applies to every fix: a property goes into the markup only when visitors can see that detail on the page.

Key takeaways

  1. Sort the message firstCritical issues can stop an item appearing as a rich result. Google says a non-critical warning is not a ranking penalty by itself.
  2. Work from one example URLOpen the report, inspect one example URL, add the value to the page or its template, test the live URL, then select Validate fix.
  3. Add only visible factsAdd a property only when visitors can see that detail on the page. Do not invent ratings, prices or identifiers to remove a message.
  4. Fix the templateIf a theme, plugin, app or custom template generates the markup, correct it there. Editing one page may not remove a warning rebuilt on every page.
  5. Know when a warning can stayA non-critical warning can stay when the property does not apply, the information is not visible, or adding it would require invented or misleading facts.
  6. Allow time for validationValidation can take about two weeks or longer, so a lingering message is normal. A passed validation is not a promise of a rich result.

What a missing field message tells you

A message such as Missing field "name" has three parts: a feature, a type and a property. The feature is the Google search appearance the markup is being checked for, such as Product snippets or Breadcrumbs. The type is the schema.org type in your markup. The property is the field Google expected to find and did not.

Google's current reports group items as valid or invalid. According to Google's rich result report overview, an invalid item has at least one critical issue that prevents it from appearing as the relevant rich result. A valid item can still carry non-critical issues, which Google lists as improvements to how the item appears. Google's issue categorization update describes the same split. Email alerts may still use the older words "error" and "warning", so read the report itself to see which group your message sits in.

It helps to keep four meanings of "correct" apart. The JSON can be syntactically valid. The properties can match the schema.org vocabulary. The markup can meet the requirements of one Google feature. And the page can be indexed and actually shown with an enhanced result. Passing one level does not promise the next, and Google's general structured data guidelines say eligible pages are not guaranteed a rich result.

A structured data manual action is a separate matter. Google says it can remove rich result eligibility, although the page may still appear in ordinary search results. A routine missing field warning is not a manual action.

Fix a warning in order

Work through the same sequence for any message. It keeps you from editing the wrong page or marking a fix as done before every URL is corrected.

  1. Open the affected report in Search Console and select the issue to see its example URLs.
  2. Inspect one example URL and read which type and property the message names.
  3. Decide whether the page shows that information to visitors.
  4. Add the accurate value to the page or, more often, to the template that generates it.
  5. Test the live URL with Google's Rich Results Test and URL Inspection.
  6. Select Validate fix once every affected page is updated.
A man in a ceramics shop back room reviews a product page on a laptop beside a glazed mug and a blank paper tag.
Figure 1. Compare the example page with the warning before changing any markup.

Step 4 is where most time goes. If a theme, plugin, app or custom template produced the markup, fix the source that generated it. Editing the page content alone may not remove a template-level warning, because the same incomplete markup is rebuilt on every page that uses the template.

A good habit is to fix one example page first and test it before changing the template for hundreds of pages. A single product page gives you a quick answer on whether your change produced the property you meant to add.

Product and Merchant listing fields

Product markup feeds two separate Google features with different requirements. Google's Product snippet documentation covers pages that describe a product, such as an editorial review or a comparison page. Google's Merchant listing documentation covers pages where visitors can buy the product. Check which report your warning came from before choosing a fix.

Here are the common Product messages and what each one asks for, as described in Google's rich result error messages:

  • Missing field "name": add the product's visible name.
  • Either "offers", "review", or "aggregateRating" should be specified: add one that genuinely exists on the page, or remove the Product markup if the page is not a product page.
  • Missing field "price" or priceCurrency: add the active price and a three-letter currency code for a product people can buy.
  • No global identifier provided: add a real gtin8, gtin12, gtin13, gtin14, mpn or isbn if one exists for the product.
  • Missing field "priceValidUntil": add it only when the price really expires on a known date.

Merchant listings also require an active price greater than zero. The example below is a purchasable product with the properties Google lists for that feature. Replace every value with details from your own product page, and delete any property that your page does not show.

json
{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://example.com/products/blue-lantern#product",
  "name": "Blue Lantern",
  "image": [
    "https://example.com/images/blue-lantern.jpg"
  ],
  "description": "A fictional rechargeable lantern for indoor use.",
  "brand": {
    "@type": "Brand",
    "name": "Example Brand"
  },
  "sku": "EX-LANTERN-001",
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/blue-lantern",
    "price": 39.99,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

Notice what this example leaves out. It has no aggregateRating and no review, because Google lists both as optional for Merchant listings. A product page with no visible reviews can carry complete, eligible markup without them. Adding invented ratings to clear a recommendation would break Google's guidelines on accurate, visible content.

Review fields

Review markup applies only in permitted contexts. Google's review snippet documentation lists supported types that include Product, Recipe, Movie, Book, Event, Course, SoftwareApplication and certain LocalBusiness uses. The review must be visible on the page, genuine and about a specific item. Google also says self-serving reviews of a local business or organization are not eligible for its star review feature.

These are the usual Review messages:

  • Missing field "author": name the real reviewer with a valid person or organization name.
  • Missing field "itemReviewed": add the reviewed item when the review is not nested inside that item.
  • Missing field "reviewRating" or ratingValue: provide the rating shown on the page.
  • Rating is missing required best and/or worst values: specify bestRating and worstRating when the scale is not the default 1 to 5.
  • Missing field "reviewCount" or ratingCount: provide the visible count for an aggregate rating.

The next example is a standalone review that points at a product. Change the product name, reviewer, date, text and rating to match a review that your page actually displays. If the page shows a score out of ten, set bestRating to 10 so the scale is explicit.

json
{
  "@context": "https://schema.org",
  "@type": "Review",
  "@id": "https://example.com/reviews/blue-lantern#review",
  "itemReviewed": {
    "@type": "Product",
    "@id": "https://example.com/products/blue-lantern#product",
    "name": "Blue Lantern"
  },
  "author": {
    "@type": "Person",
    "name": "Jordan Example"
  },
  "datePublished": "2026-10-10",
  "reviewBody": "The fictional lantern is easy to carry and simple to recharge.",
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": 4,
    "bestRating": 5,
    "worstRating": 1
  }
}

When a Product page carries an editorial review of its own, the review object can sit inside the Product instead. In that nested form, itemReviewed is not needed because the review already belongs to the product. Google lists author, reviewRating and ratingValue as required for the Product snippet feature in that case, and datePublished as recommended.

Breadcrumb messages usually mean the list is incomplete or numbered wrongly. According to Google's breadcrumb documentation, the feature needs an ordered itemListElement, and each ListItem needs a position and a name. Intermediate items should also carry an item URL. The final breadcrumb may leave item out.

Match each message to its fix:

  • Missing field "itemListElement": create the ordered list of breadcrumb entries.
  • Missing field "position": number each entry, starting at 1.
  • Missing field "name": add the breadcrumb label visitors see.
  • Missing field "item": add the URL for each intermediate entry.
  • Fewer than two ListItem objects: add a meaningful parent and the current page, if the page has that hierarchy.

Google recommends breadcrumbs that follow a typical path a visitor would take, not merely the URL folders. It also says breadcrumb results currently appear on desktop Search. In the example, replace the names and URLs with your own page path, and keep the labels identical to the breadcrumb trail shown on the page.

json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "@id": "https://example.com/guides/schema-warnings#breadcrumb",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Guides",
      "item": "https://example.com/guides"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Testing and fixing",
      "item": "https://example.com/guides/testing-and-fixing"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Fixing schema warnings"
    }
  ]
}
Two colleagues look at one laptop together at a shared table in a co-working space.
Figure 2. Testing the live page before requesting validation keeps a fix from being marked done too early.

Add only what the page shows

The safest way to clear a missing field is to ask one question: can a visitor see this information on the page today? If yes, add it. If no, the property does not belong in the markup, whatever the warning says.

Google's guidelines tell site owners to keep structured data accurate and to mark up content that visitors can see. Bing's webmaster guidelines say the same thing, adding that markup should reflect visible content and does not guarantee visibility. So, a made-up aggregateRating, a placeholder price or a guessed gtin13 may clear the message but puts the page at odds with both sets of guidelines.

When the information exists but is not on the page, you have two choices. Publish it where visitors can read it, then mark it up. Or leave the property out. A real identifier that sits in your product database but not on the page is a fine candidate for the first choice.

If a whole type does not fit, remove it. A Product block on an article, or review stars attached to your own business, describes something the page is not. Removing wrong markup is a valid fix and usually clears the related messages at once.

Fix the template when a platform generates the markup

Many warnings are produced by software, not typed by hand. A theme, an SEO plugin, a store app or a site builder may output the markup for every page of a kind. The first step is to inspect the rendered page and identify which one generated it, so you edit the right place. If two tools describe the same item, change one of them first and retest, so you know which output Search Console is reading.

Platform behavior differs. Wix says it supports manual JSON-LD, preset markup and AI-generated blog markup (Wix structured data documentation). Squarespace says it automatically generates structured data for several groups, including blog post, event, local business, organization, product and website (Squarespace SEO documentation). Webflow documents manual entry and its own AI generation (Webflow schema documentation).

On Shopify, HubSpot and Next.js sites, inspect the rendered product page or the live URL to see the JSON-LD the theme or component produces, then correct the template, field or component behind it. WordPress readers will find the install and plugin routes in the WordPress schema markup guide, which explains how to check existing theme and plugin output before editing anything.

If your markup is hand-written, paste it into the Schema Validator to catch syntax problems before you publish. JSON-LD needs valid JSON, with unique keys, quoted strings and no comments or trailing commas, according to the W3C JSON-LD 1.1 specification.

Test the live page and request validation

Test the live URL before you ask Google to validate. Google's Rich Results Test checks eligibility for Google features and reports errors and warnings. The Schema Markup Validator, run by schema.org, checks vocabulary without Google feature warnings, as Google's markup testing documentation also notes. Use the first to see whether the warning is gone and the second to confirm the vocabulary is sound. To inspect a page's markup without Search Console access, the Schema Checker reads a public URL.

Then check that Google can reach the page. Look at robots.txt, noindex tags, login requirements and server errors, since a blocked page cannot be rechecked. Run URL Inspection on the live URL to confirm the fetched page contains your new markup.

When every affected URL or the shared template is corrected, open the issue details page and select Validate fix. Google's validation details say it checks a sample first, then queues the known affected URLs for recrawling. The status moves through Started, Looking good, Passed, Failed or N/A. If validation fails, inspect the URLs that failed, correct them and start again after the current cycle ends.

Validation can take about two weeks or longer, so a lingering message in the days after your fix is normal. Google may also update issue counts during ordinary crawling without any validation request. A passed validation confirms Google's recrawl checks for known instances; it is not a promise of a rich result.

From warning to verified fix

  1. Open the reportSelect the issue in Search Console and read the type and property it names.
  2. Inspect an example URLCheck whether the page visibly shows the information the property describes.
  3. Update the sourceAdd the real value to the page or to the template that generates the markup.
  4. Test the live URLRun the Rich Results Test and URL Inspection on the corrected page.
  5. Check crawl accessConfirm robots.txt, noindex tags, logins and server errors do not block Google.
  6. Validate and monitorSelect Validate fix after all pages are corrected, then watch the status.

When a warning can stay

Not every warning needs a code change. A non-critical warning can usually stay when one of these is true:

  • The item is valid and the issue is non-critical.
  • The property does not apply to the page.
  • The information is not visible to visitors.
  • Adding the property would require invented, unavailable or misleading facts.
  • Adding it would create duplicate or conflicting markup.
  • The page is not meant to qualify for that Google feature.

A leftover warning for a property you cannot back with real facts is a better outcome than a clean report built on made-up data. If the warning appears on a Product page that has no reviews, leave review and aggregateRating out. If the page is valid but still shows no enhancement, the question moves from missing fields to eligibility and display, which has its own checks.

Bing reads schema.org in JSON-LD, Microdata and RDFa and validates annotations against the chosen data types (Bing structured data documentation). Its URL Inspection Markup card lists issues for the selected type, and Yandex offers a structured data validator.

For ChatGPT Search, allow OAI-SearchBot in robots.txt (OpenAI ChatGPT Search, crawler documentation); Perplexity documents its crawlers in its bot guide. Keep key facts in visible page text and use accurate markup. See whether AI systems use schema markup.

Questions people ask

What does "missing field" mean in Search Console?

It means the markup for a feature lacks a property Google looks for. The message names the type and the property, such as Missing field "name" in Product. Check whether the page shows that information before adding anything.

Do non-critical structured data warnings hurt rankings?

Google says a warning is not a ranking penalty by itself. Non-critical issues describe how complete an item's appearance can be, and the item usually stays eligible. Fix them when the property is real and visible, and leave them when it is not.

Should I add a rating if my product has no reviews?

No. Add review or rating properties only when genuine reviews are visible on the page. Without them, leave the properties out; a Product can still carry offers and qualify for its feature.

Why does the warning still show after I fixed the page?

Search Console updates after Google recrawls the affected URLs, and validation can take about two weeks or longer. Confirm the live URL in the Rich Results Test, check that Google can crawl it, and wait for the validation status to change.

Does structured data guarantee a rich result or an AI citation?

No. Google says eligible pages are not guaranteed an enhanced display, and Bing says annotations do not guarantee a visually rich result. Accurate markup describes the page; whether a provider shows or cites it is that provider's decision.

Quick check: fix it or leave it

Choose an answer to see feedback. Nothing is scored or saved.

Question 1 of 3

A Product page has no reviews and Search Console recommends aggregateRating. What is the right move?

Question 2 of 3

A non-critical warning appears on an otherwise valid item. What does Google say about it?

Question 3 of 3

Your theme generates the markup on every product page. Where should the fix go?

Terms in a Search Console warning

Select a term to see its definition.

Structured data. Code that describes a page's content in a standard vocabulary so software can read it.