What enhancement reports measure
Enhancement reports are a set of separate reports in Search Console, one for each type of structured data Google has detected on your site. Breadcrumbs, frequently asked questions, products, videos, job postings and the rest each get their own entry, and none of them appear until Google finds that type on at least one of your pages.
Inside a report, your pages are sorted into valid items, items valid with warnings, and invalid items, then grouped by the specific issue causing each state. An error means a required property is missing or malformed, and that item cannot qualify for the corresponding search feature. A warning means a recommended property is absent: the item still qualifies, but with less to show.
Each issue group carries a validation option. Once you have fixed the underlying pages, you ask Google to re-check, it recrawls a sample, and the group either clears or comes back with the same fault.
Why enhancement reports matter
Structured data is written for machines, so nothing about it is visible when it breaks. A theme update, a plugin change or an edited template can invalidate markup across an entire site, and the only way you find out is through these reports or a sudden change in how your listings look.
They are also the practical way to check work at scale. Testing one URL proves that page is fine; these reports tell you whether the template behind a few thousand pages is fine, which is the question that actually matters.
Common mistakes with enhancement reports
The largest is believing that valid markup buys a rich result. Validity only makes a page eligible. Google decides separately whether to display an enhanced listing, based on the query, the device and its own judgement about the page, and it withdraws features from whole categories of site from time to time.
The second is treating warnings as urgent. They are optional properties, worth adding when the data genuinely exists and not worth inventing when it does not.
The third is more serious. Marking up content that visitors cannot see on the page — questions and answers that are not published, ratings nobody left — is against Google’s guidelines and can attract a manual action. The markup must describe what is actually there.
How to act on it
Work errors before warnings, and work by issue group rather than by URL, because one template fix usually clears a whole group. Open a sample page, test it, correct the template, then use validation and expect the result to take time while pages are recrawled.
If a report appears for a type you never deliberately added, find out what added it. Duplicated or conflicting markup from a theme and a plugin at once is common and produces contradictory data. Keeping one source of truth for markup, and reviewing it after any platform change, is the least glamorous but most reliable part of schema markup work.