Structured data: policies, supported features and entity types
Scope came first: the priority pages don't carry every markup type, so this cluster used a seeded, stratified sample of about 200 URLs across every sitemap class. Re-running the same sample after a fix moved no verdict, and that was the finding: the measurements were stable. Google's own tools, which had been blocked by a user-agent gap, could then confirm them.
Across about 200 sampled pages, marked-up text values were compared with visible text. Re-rendering pages with absent values cut the count from 92 to 32, so two thirds of the apparent problem was rendering timing, not invisible markup. A second run on the same sample gave the same 32. Of those, 26 are description fields from two generated templates, and the other 6 are probably fine (spelling variants and unrendered breadcrumb names). Scored Partial because the text is not visible, though no rich result depends on it. The realistic cost is a wasted field: real content was available and a template sentence was emitted instead.
Google's Search Gallery listed 32 features on the day of capture. The site emits 23 distinct @type values, of which 9 map to a gallery feature. The rest are legitimate schema.org types that Google will not render as rich results, and Rich Results Test on 8 pages reported only gallery features, as the claim predicts.
Of 167 non-logo ImageObjects in the sample, none carries both properties, and the two fall on different templates. Google's own tools corroborate the measurement, reporting Image Metadata warnings on 77 pages. The verdict stands because the claim's test is unmet. Before recommending a fix we checked the image rights position, because adding license markup should follow from the rights a publisher actually holds. A failed check doesn't always mean the fix is to add the markup.
All 10 sampled Article nodes use a correct type and carry headline, image and an author. The author is written as a JSON-LD @id reference, which is valid. Our tool first misread it as a nameless author, a defect caught in piloting that would have produced a false Gap on every article. Rich Results Test later validated the same markup.
176 BreadcrumbList objects with no faults: every ListItem typed, positions strictly increasing from 1, every name present, every item an absolute URL. Search Console's indexed view holds 159 stored Breadcrumbs items with no issues. 22 sampled pages carry no trail, which is recorded as an opportunity, not a failure of this claim.
Rendered pages keep their JSON-LD, and the type set is identical between crawl and rendered views. The claim's second sentence, validate with Rich Results Test, could not be followed at first: Google's testing tools fetch under a separate user agent that the site's prerender did not recognise, so they received an empty app shell. That was reported and fixed, and on re-measuring, all 8 pages tested returned valid items.
Both halves hold: the most specific applicable type is used, and Rich Results Test confirms it yields no rich result. As an observation only, most nodes carry none of the type's domain-specific properties, even though that information is on the page as text. Recorded as an enrichment opportunity.
Want this run on your site?
We test your site against the same claims, record a verdict and the evidence for each one, and tell you what to fix first.
Start a conversation