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.

1. Go to your Project Settings
2. Navigate to Step 3: Extensions
3. Enable Rich Results Validation
4. Choose whether to include warnings (optional)
5. 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 13 structured data types: Article, Breadcrumb, Event, FAQ, Image Metadata, Merchant Listing, Organization, Product, Profile Page, 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:

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.

Merchant listing and Product snippet are both built on Product markup. Merchant listing is for pages where the shopper can buy: it needs a single Offer with a price and currency, and carries shipping and returns details. Product snippet is for reviews, aggregators and pages that link out to sellers: it accepts Offer or AggregateOffer, and surfaces ratings and reviews.

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.

What Lumar checks for each type

Condensed from the CS one-pager (October 2026). Link the full PDF at the end of the section for the complete property tables.

Intro: Lumar checks each type against Google's own property table. A missing required property means the rich result does not show. A missing recommended property means it shows with less in it. Google revises these requirements without much notice; this reflects October 2026.

Article (Article, NewsArticle, BlogPosting). Google publishes no required properties; add the ones that apply. Recommended: author, headline, image, datePublished, dateModified. Watch out: author.name should carry the name only, no job titles or "posted by", and one author per author field.

Breadcrumb (BreadcrumbList, ListItem). Required: itemListElement, and on each item: item, name, position. Watch out: position starts at 1, you need at least two items, and the last crumb may omit item.

Events (Event, Place, PostalAddress, Offer). Required: name, startDate, location, location.address. Watch out: location.address should be a street address; virtual-only events are not supported; each event needs its own URL.

FAQ (FAQPage, Question, Answer). Google stopped showing FAQ rich results on 7 May 2026 and removed the documentation in June. The markup is still valid schema.org, but earns no Google rich result. Lumar still reads and reports it.

Image Metadata (ImageObject). Required: contentUrl plus at least one of license, creator, creditText, copyrightNotice. Watch out: the Licensable badge needs license specifically.

Merchant listing (Product, Offer). Required: name, image, offers, and offers.price (or priceSpecification.price) with priceCurrency. Watch out: price must be above zero, merchant listings need an Offer not an AggregateOffer, and the markup has to come from the seller.

Organization (Organization, OnlineStore, LocalBusiness). No required properties; built from the recommended set (name, url, logo, sameAs, contactPoint, address and so on). Watch out: Google asks for this on one page, the home or About page. Lumar does not check placement.

Product snippet (Product, Review, Offer, AggregateOffer). Required: name plus at least one of review, aggregateRating, offers. With offers, a price; with AggregateOffer, lowPrice and priceCurrency. Watch out: a past priceValidUntil date may stop the snippet; mark up product pages, not category listings.

Profile page (ProfilePage, Person, Organization). Required: mainEntity and mainEntity.name, where mainEntity is a Person or Organization. Watch out: interactionStatistic should count activity on the hosting platform only.

Q&A (QAPage, Question, Answer, Comment). Required: mainEntity, mainEntity.name, answerCount, plus acceptedAnswer or suggestedAnswer with text. Watch out: one question per page, and users must be able to submit answers. A page with no way to add answers is ineligible.

Recipes (Recipe, HowToStep, HowToSection, ItemList). Required: name, image; sectioned recipes need HowToSection.name and itemListElement. Watch out: prepTime and cookTime only count as a pair, otherwise use totalTime; calories needs recipeYield.

Review snippet (Review, AggregateRating, Rating). Required: author, reviewRating, reviewRating.ratingValue; on AggregateRating, ratingValue plus ratingCount or reviewCount. A standalone review also needs itemReviewed with a valid Google type. Watch out: self-serving reviews on LocalBusiness or Organization markup are ineligible for stars; review content must be visible on the page. A review snippet can only sit inside Book, Course list, Event, Local business, Movie, Product, Recipe, Software App, or the schema.org types CreativeWorkSeason, CreativeWorkSeries, Episode, Game, MediaObject, MusicPlaylist, MusicRecording, Organization.

Videos (VideoObject, Clip, BroadcastEvent). Required: name, thumbnailUrl, uploadDate. Watch out: contentUrl points at the video file and embedUrl at the player, neither at the page. A timezone on uploadDate is recommended.

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.

Optional metrics

Alongside validation, Lumar extracts a small set of values from Product and Article markup. These are available as columns on All Pages and in the Rich Results reports, and can be filtered, segmented and exported. Use them to check the content of your markup, not just whether it validates.

Product properties

These let you find products with missing or unexpected values, for example pages with Product markup but no price, or products marked OutOfStock that are still linked from category pages.

Article properties

Google asks that the author field carries the name only, with no job titles or “posted by” text, and one author per author field. Filter on this column to find pages where the author value is empty or formatted inconsistently.

Structured data metrics on All Pages

our metrics bring validation results into the All Pages report, so you can see structured data problems alongside Search Console data, indexability and custom metrics.

Add them from the column picker on All Pages. All four can be filtered and used in segments. The two counts can also be used in Monitor alerts.

To prioritise fixes by traffic: filter Schema Types Present to the type you care about, add Search Console Impressions as a column, and sort. Open the matching Rich Results report for the detail on which block and which property.

Filtering by type and severity: You can filter to pages where a type has any issue: set Schema Issues Count By Type, type, contains "Product snippet". You cannot filter to pages where that type specifically has an error, because the type and the count are matched separately. A page with a Product snippet warning and an Article error would match both "type contains Product snippet" and "errors greater than 0". The Schema Issues Count By Type column shows which type carries which, so you can read it per page. To filter by type and severity together, use the Errors or Warnings report for that type.

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.

Where do I find product price and availability?

They are not columns on the structured data reports. To see price across a group of pages, open Data Explorer, find the URL path group you want, then select View URLs to reach a filtered All Pages report where you can add the Product Price column. Price is most reliable on pages with a single product.

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:

• Structured Data Validation in Lumar
• Google Rich Results documentation