GSC Enhancements Report: Monitor Structured Data
Structured data markup — schema.org JSON-LD that tells Google what your content is about — is only as valuable as Google's ability to read and validate it. The Enhancements section in Google Search Console is where Google reports back on what it found: which schema types it detected, which URLs have valid markup, and which have errors that prevent rich results from appearing in search. Monitoring these reports is essential for protecting and improving your rich result eligibility.
What the Enhancements Reports Show
The Enhancements section in the GSC left navigation lists one report for each structured data type Google has detected across your site. Each report shows a trend chart of Valid, Warning, and Error URL counts over time, and a table of specific issues with the number of affected URLs. You can click into any issue to see the list of affected pages, and click any URL to open URL Inspection for that page. The reports only appear after Google has crawled and detected structured data on your site — a brand new schema implementation may take 1–2 weeks to appear after Googlebot recrawls the relevant pages.
Schema Types GSC Monitors
GSC Enhancements reports cover the schema types that are eligible for rich results in Google Search. These include: Product (price, availability, ratings), Review Snippet (aggregate ratings, individual reviews), FAQ (question-answer pairs), How-To (step-by-step instructions with images), Recipe (ingredients, cook time, nutrition), Article (news articles, blog posts), Event (event dates, locations, tickets), Job Posting, Course, Dataset, and Book. Not all schema types have Enhancements reports — BreadcrumbList and SiteLinksSearchBox appear but may be reported under different sections. Only markup that follows Google's rich result guidelines generates Enhancements data.
Error vs Warning vs Valid
GSC uses three severity levels for structured data issues. Error means a required property is missing or has an invalid value — URLs with errors are ineligible for rich results and will not show enhanced SERP features regardless of how well the page ranks. Warning means an optional or recommended property is absent or has a potential issue — the page may still qualify for rich results but might display a reduced or incomplete enhancement. Valid means Google parsed the schema successfully and the page is eligible to show rich results, though eligibility doesn't guarantee they'll appear (Google uses additional quality signals). Always resolve Errors first.
Common Structured Data Errors
The most frequent structured data errors across schema types: missing required field (e.g., Product schema missing "name" or "offers"), invalid value format (a date formatted as "March 2026" instead of ISO 8601 "2026-03-15"), empty field (a property present in the markup but with no value), and logo or image missing required dimensions. For Review schema, the most common error is providing a rating without an "author" property — Google requires every review to have a named author. For FAQ schema, having fewer than two question-answer pairs or placing the markup on pages where the FAQ doesn't actually appear on the page will generate errors.
Using the URL Inspection Tool for Schema
For any URL showing in an Enhancements error list, use the URL Inspection tool to get detailed schema diagnostics. After inspecting a URL, scroll to the "Enhancements" section of the inspection result — it lists every schema type detected on that page, the properties found, and any specific property-level errors. This is the most granular view of what Google actually parsed from your markup. It also shows whether Google is seeing the live version of your page or a cached version from weeks ago, which matters if you've recently updated your schema. Use "Test Live URL" to force a fresh fetch and validate your current markup.
Fixing Missing Required Properties
Required properties for each schema type are documented on developers.google.com/search/docs/appearance/structured-data. For Product schema, the required properties are name and at minimum one of: offers, review, or aggregateRating. For FAQ, each Question must have a name (the question text) and acceptedAnswer with text. For Recipe, required fields include name, image, author, description, and recipeIngredient. When fixing missing properties, use Google's Rich Results Test tool to validate your markup before deploying — it catches errors instantly and shows you exactly what a rich result would look like for that page. Fix and test before pushing to production to avoid creating new GSC errors.
After Fixing: Validate and Request Indexing
After deploying structured data fixes, the workflow is: validate with the Rich Results Test (live URL test), then use URL Inspection in GSC to request indexing for the affected pages. Don't wait for Googlebot to recrawl on its own schedule — requesting indexing typically results in recrawling within hours to days. Once the page has been recrawled, check the URL Inspection result again to confirm the error is resolved. Return to the Enhancements report after 3–5 days — if the fix was applied correctly across all affected URLs, you should see the Error count drop and the Valid count rise correspondingly. If errors persist, some pages may not have deployed the fix correctly.
Monitoring New Schema Deployments
When you add structured data to a new section of your site — new schema type, new page template, or a new CMS component — build a monitoring workflow into the deployment process. After deploying, add a 2-week calendar reminder to check the relevant Enhancements report for that schema type. New implementations often have template-level errors that affect hundreds or thousands of pages simultaneously — catching these early prevents a large backlog of errors accumulating before anyone notices. For large sites, the error count chart is the fastest way to detect a problem: a sudden spike in errors after a deployment date is a clear signal of a schema regression introduced by the change.
Structured Data Errors That Kill Rich Results
Some structured data errors are more consequential than others. Errors that definitively prevent rich results include: missing required properties (Google will not show a Product rich result without a price), schema markup that describes content not present on the page (this also violates Google's spam policy and can trigger a manual action), and rating values outside the valid range. Errors that don't always block rich results but reduce eligibility include: missing recommended image properties, aggregate rating with fewer than the recommended number of reviews, and markup on paginated pages where the content is not fully present. Resolve errors in order of their business impact — fix schema on your highest-traffic pages first, especially product and review pages where rich results directly improve conversion rates.