Find these reports in Rankability > Structured Data.
Lumar validates structured data against Google's Rich Results requirements, helping you find issues that could prevent enhanced search listings. For background on what we validate and why, see Structured Data Validation in Lumar.
What you can do with these reports
- Audit Rich Results eligibility at scale. Check whether your product pages, articles, recipes, and other content qualify for enhanced Google search listings, without testing pages one at a time in Google's Rich Results Test.
- Find and fix validation errors. Identify missing required properties, invalid formats, and other issues that block your pages from appearing with enhanced features in search results.
- Export issues for development teams. Get detailed error information with extracted structured data blocks, giving developers everything they need to locate and fix issues.
Enabling structured data validation
Structured data reports require the Structured Data Reporting extension to be enabled in your project settings.
- Go to your Project Settings
- Navigate to Step 3: Extensions
- Enable Rich Results Validation
- Choose whether to include warnings (optional)
- Run a crawl
Reports will populate once the crawl completes.
When you enable Rich Results Validation in Crawl Settings, new reports replace the old schema reports. The new reports validate more structured data types, so you may notice an increase error counts.
Report Types
Lumar validates 12 structured data types: Article, Breadcrumb, Event, FAQ, Image Metadata, Merchant Listing, Organization, Product, Q&A, Recipe, Review, and Video.
Each type has specific required and recommended properties defined by Google. See Google's Rich Results documentation for detailed requirements per type.
Each structured data type has three associated reports:
| Report | Purpose | Affects Health Score |
| Pages with [Type] | All pages containing this structured data type | No |
| [Type] Errors | Pages with issues that block Rich Results eligibility | Yes |
| [Type] Warnings | Pages with missing recommended properties | No |
FAQ Errors do not contribute to your Health Score. Google now restricts FAQ Rich Results to government and health sites, so most pages won't qualify regardless of markup validity. The report remains useful for identifying issues if your site is eligible.
Errors indicate problems with required properties. Pages with errors won't qualify for Rich Results until fixed. These are the issues to prioritise.
Warnings indicate missing recommended properties. Pages may still qualify for Rich Results, but adding these properties could improve how your content appears. Warning reports only populate if you enabled warnings in crawl settings.
Optional metrics
You can add additional columns to customise your reports for Product and Article types. Use these to audit product data at scale, such as identifying pages with missing prices or inconsistent brand values.
Product properties
- Product Price
- Product Aggregate Rating
- Product Availability
- Product Brand
- Product SKU
Article properties
- Article Author
Working with the reports
Viewing validation details
Open any Errors or Warnings report to see pages with validation issues. The default view includes the Blocks column, which shows the extracted structured data (JSON-LD, Microdata, or RDFa) found on each page. This lets you see exactly what Lumar found in your markup.
The Issues column expands to show details for each validation issue, including the issue type, severity, description, affected property, and schema type.
Drilling down to page details
Click any URL to open page details. This shows all structured data blocks found on that page, not just the type you filtered by — useful when a page has multiple schema types.
Exporting for development teams
Export reports to create fix tickets for developers. Exports include the page URL, issue details, and affected properties.
API and Data Studio
All structured data metrics are available through the Lumar API and Data Studio connector. If you previously connected a data source, reconnect to access the new metrics.
Article properties: Author
Frequently asked questions
Why do I see more errors than before?
The new reports validate more structured data types and check against Google's current requirements. This surfaces issues that older reports didn't detect.
What if Lumar shows an error but Google's Rich Results Test doesn't?
Our validation continuously improves as we refine our understanding of Google's requirements. If you find pages that pass Google's test but show errors in Lumar, contact support@lumar.io with the page URL and a screenshot. This feedback helps us improve accuracy.
Why doesn't Lumar validate against Schema.org?
Google's requirements differ from Schema.org specifications. Google accepts some markup that Schema.org would reject, and requires specific properties beyond the Schema.org minimum. Validating against Schema.org would flag issues that don't actually affect your search appearance. Lumar validates against what Google actually requires.
Do I need JavaScript rendering enabled?
No. The enhanced structured data validation works without JavaScript rendering. Lumar extracts JSON-LD and other data types directly from your page source.
Can I see all structured data on a page, not just one type?
Yes, click the URL link in Summary column to drill down to Resource Details to see all extracted schema blocks for that page, regardless of which report you started from.
Related articles: