Skip to content
A/MR

SEO · · 3 min read

Google Says Structured Data Must Match What Readers Can See, and Valid Markup Still Doesn’t Guarantee a Rich Result

Google's general structured data guidelines: mark up only visible content, don't block the page, and know that valid markup is no guarantee of a rich result.

A/MR graphic: Google supports three structured data formats, JSON-LD recommended, and says valid markup does not guarantee a rich result

hi, i’m amr. schema markup gets sold as a switch that turns on rich results. google’s general structured data guidelines page describes something smaller, and it lists the ways markup can work against you.

what google says, in its own words

  • pages can be marked up in JSON-LD (the recommended format), Microdata or RDFa
  • “Don’t block your structured data pages to Googlebot using robots.txt, noindex, or any other access control methods.”
  • “Don’t mark up content that is not visible to readers of the page.”
  • “Don’t mark up irrelevant or misleading content, such as fake reviews or content unrelated to the focus of a page.”
  • “Your structured data must be a true representation of the page content.”
  • put the structured data on the page it describes, unless the documentation for that type says otherwise
  • items missing required properties are not eligible for rich results, and google won’t show a rich result for time-sensitive content that is no longer relevant
  • image urls in structured data must be crawlable and indexable
  • the rich results test and the URL inspection tool “catch most technical errors”
  • “Google does not guarantee that your structured data will show up in search results”, even when it passes the rich results test
  • a structured data issue “can result in a manual action”. google says a manual action removes rich result eligibility but “doesn’t affect how the page ranks in Google web search”, and you can check for one in the Manual Actions report in search console

the page doesn’t say how long a manual action lasts, how to appeal it, or which properties each rich result type needs, because it sends you to other pages for that. it makes no claim that rich results improve rankings.

my reading, not google’s wording: markup that describes something the visitor can’t see on the page is the fastest way to turn a technical task into a policy problem. the test tool checks syntax. it can’t tell whether the claim is true.

what to check this week

  • list the pages that carry schema and the type on each: article, product, review, event, faq
  • for each one, read the markup next to the visible page. every price, rating, date and name in the markup should be on screen for the reader
  • check that no schema page is blocked by robots.txt or tagged noindex. google says not to
  • run the live url through the rich results test and the URL inspection tool, and fix the errors they report
  • remove review or rating markup that isn’t backed by real reviews shown on the page
  • check dates on time-sensitive markup such as events and offers, since google says expired content won’t get a rich result
  • open the Manual Actions report in search console and note whether anything is listed
  • i covered what happened to one rich result type in an earlier post

where this stops applying

this page is the general rulebook. each rich result type has its own page with required and recommended properties, and the page doesn’t repeat them. i haven’t audited any site for this post, so treat the list above as a starting point.


start scaling — if your schema was added by a plugin and nobody has compared it with the page since, a one-hour review will show what’s marked up and whether readers can see it. let’s connect.

Sources: Google Search Central, “General structured data guidelines” (developers.google.com/search/docs/appearance/structured-data/sd-policies). Figures are published product documentation, not verified results from Amr’s own client accounts.

Leave a reply