Yes. Google's structured data guidelines ask that markup describe the page's main content and that the marked-up information be visible to the person who lands there. Markup describing something the page does not show is an eligibility problem first, and occasionally a manual action.
What does Google actually say about hidden or mismatched markup?
Its general structured data guidelines are explicit on two points: the markup has to represent the main content of the page, and it should not describe content that is hidden from the user. The review snippet documentation is stricter still, asking that the review content being marked up actually appear on the page carrying the markup.
Read together, those rules describe a single test. A reader who lands on the page should be able to find, without hunting, the thing your markup claims is there. That is a lower bar than it sounds, and it is the bar most broken implementations fail — not the syntax, which the validators already catch.
What counts as a mismatch?
Anything a reader could contradict by looking at the page.
| What the markup claims | What the page shows | Why it fails the test |
|---|---|---|
| A price | A different price after a feed update | The snippet in search results misstates the offer; the click arrives already annoyed |
| A star rating and review count | No reviews anywhere on the page | Nothing on the page substantiates the claim, which is the case review schema guidance addresses directly |
| In stock | An out-of-stock badge | Stale product schema, usually a caching gap rather than a decision |
| An author | No byline on the page | Describes an entity the page does not present |
| A product name | A different name in the heading | Reads as markup written for the search result rather than the page |
The question is not whether the markup validates. It is whether a skeptical reader could find every marked-up value on the rendered page. Valid markup describing invisible content is the common way sites lose rich results without losing rankings.
What happens when the markup and the page disagree?
Three outcomes, in rising order of cost. Most often nothing visible happens at all: the rich result simply never appears, and because nothing broke, nobody investigates. Next, rich results that used to show stop showing, which looks like an algorithm update and is really a template change from two releases ago. At the far end, Search Console's manual actions report names a structured data problem, and rich results come off the affected pages until it is fixed and a review is requested.
None of these three touches your ordinary rankings, which is exactly why the drift lasts so long. Organic search positions hold, clicks sag, and the obvious suspects get blamed.
Why does the mismatch usually happen by accident?
Because the markup and the visible page are built by different code paths at different times. Four mechanisms account for most of it:
- Plugin defaults. A tool bolts an aggregate rating or an organization block onto every page in the site, including pages where it describes nothing.
- Template drift. A field is dropped from the design and the schema markup block is left marking it up, because the block lives in a different file nobody touched.
- Cache and feed lag. Markup renders from a feed on one schedule and the visible price or availability on another, so the two agree most of the time and disagree exactly when it matters.
- Script-injected markup. Markup written after load against values the visible page has since replaced, which also makes the mismatch invisible in the page source.
Letting a plugin attach a rating to every page on the site. It is the single fastest way to turn a legitimate markup setup into something that reads as deliberate, because the pattern — ratings on pages with no reviews — is trivial to detect at scale.
How do you check it without reading every page?
Check templates, not URLs. Pick one representative page per template and run it through Google's Rich Results Test, which shows you what Google parsed rather than what you wrote. Then open the same page as a reader and find each marked-up value on it. If a value takes you more than a few seconds to locate, treat it as missing.
For scale, Search Console's enhancement reports tell you which markup types Google recognized across the site and where it found errors, which is enough to spot a template that stopped producing valid output. It will not tell you that valid markup is describing the wrong thing — no automated check will, because only your page knows what it was supposed to say. That comparison, run once per template after any release that touches markup or layout, is the whole discipline.
Where to start this week
Take the template that carries your most commercially important pages and audit exactly one of them against this test, field by field. Either every claim survives the reader check, in which case you have earned the right to trust the rest of that template, or one of them does not, in which case you now know how many pages share the same problem. Pick the template before you pick the tool.