Main area
Agency
technisches-seo

Testing and Debugging Structured Data — Tools, Errors and a Clean Workflow

Redaktion ·

Testing and Debugging Structured Data — Tools, Errors and a Clean Workflow

Structured data is only worth something if Google reads it correctly. A typo in a property name, a wrong data type or a missing required field — and the rich result you were hoping for never appears. The tricky part: such errors are invisible in the source, the HTML looks the same as always. That is why you need tools that show you what Google actually makes of your markup. This article sorts the three most important tools, explains the difference between an error and a warning, and gives you a debug workflow that works reproducibly.

The three tools — and what each one shows

There is no single tool but three, each answering a different question. Confusing them means despairing over the wrong picture.

Rich Results Test (Google). Shows which Google rich results your markup can generate on a specific page, and provides a preview of how the rich result might look in Search (source: Google Search Central, accessed 2026-06-06). This is the Google lens: it does not check every schema detail, only the types Google actually supports for rich results. You can feed it a live URL or a code snippet.

Schema Markup Validator (schema.org). Validates all schema.org-based markup on a page — without Google feature-specific warnings. This is the generic lens: broader, because it also knows types Google does not use for rich results, but more neutral, because it does not care whether Google builds a pretty search result from it. Google retired its old Structured Data Testing Tool and handed pure schema validation to this validator.

Search Console reports (rich result status reports). Show the aggregate across your real index — which structured data Google found on your whole site and whether it is valid, including the trend over time (source: Search Console Help, accessed 2026-06-06). The report has a summary page with a chart of errors, warnings and valid items, plus a details page per issue type. This is the reality lens: here you do not see one test page but what Google registers in live operation across all your URLs.

In short: the Rich Results Test and the validator check one page now; the GSC reports show the whole site over time.

Error vs. warning — the decisive difference

Both the Rich Results Test and the GSC reports separate two severity levels sharply, and you have to understand this split or you will chase the wrong problems.

Error (red). An item with at least one critical issue — typically a missing required field (required property). An item missing required properties is not eligible for rich results (source: Search Console Help, accessed 2026-06-06). Errors therefore block the rich result entirely. This is what you fix first.

Warning (yellow). The markup is valid but could be better — usually a recommended property is missing. The page can still appear as a rich result. The more recommended properties you provide, the higher quality the result is for users. Warnings are optimisation potential, not a blocker.

Common mistakes — and why they happen

Three classes of error show up again and again:

Missing required properties. The most common error. Every rich result type has a list of required properties in Google’s docs. If one is missing, the item is red and disqualified. Example: a Product markup without name, or a Recipe without recipeIngredient.

Markup for content not visible to users. Google explicitly forbids it: Don’t mark up content that is not visible to readers of the page (source: Google Search Central, accessed 2026-06-06). Structured data must represent the visible page content. Writing a 4.9-star rating into the markup that appears nowhere on the page violates the guidelines — and risks a manual action that removes rich result eligibility (it does not affect normal web ranking).

Wrong data types. A date as free text instead of ISO format, a price as a string with a currency symbol instead of a clean numeric value, a URL without a protocol. You do not notice such type errors in the HTML, but the validator does.

A clean debug workflow

So debugging does not turn into guesswork, a fixed order helps:

  1. Isolate the code with the schema validator. First feed the markup snippet into the schema.org validator. It tells you neutrally whether the schema is syntactically correct and type-correct — without Google logic in between.
  2. Check the Google view with the Rich Results Test. Only then check whether Google can build a rich result from it. Here you see missing required fields for the specific type and the preview.
  3. Cross-check visibility. Make sure every value in the markup actually appears on the page. This is the guideline check no tool does for you.
  4. Watch the real index with GSC. After deployment, monitor the rich result status report over days and weeks — it tells you whether Google accepts the markup across all affected URLs and whether new errors appear.

The first three steps are pre-validation on one page; the fourth is ongoing monitoring of the whole site. Together they prevent a silent error from costing rich results for months.

FAQ

What is the difference between the Rich Results Test and the Schema Markup Validator?

The Rich Results Test is Google’s lens: it shows only the types Google supports for rich results and provides a search preview. The schema.org validator is generic: it checks any schema.org markup for syntactic correctness, without Google-specific warnings, and also knows types unrelated to rich results. For debugging, use both in sequence.

Why doesn’t my rich result appear even though the test is green?

A green test only means the markup is valid and makes you eligible for a rich result. It is not a guarantee. Google decides itself whether and when a rich result is served — based on quality, content visibility and algorithmic judgement. Google also needs time to re-crawl the page before anything shows in Search.

Do I have to fix all warnings?

No. Warnings concern recommended, not required, properties — the page can appear as a rich result even with warnings. But they are quality potential: the more complete your markup, the richer and more useful the result. Always prioritise the red errors first; the warnings are worth it afterwards.

What happens if I mark up content that is not visible?

That is a guideline violation. Structured data must represent the page content visible to users. If you mark up something invisible — fabricated ratings or hidden text — Google can issue a manual action. The consequence: the page loses eligibility for rich results. Normal web ranking is unaffected, but the rich result is gone.

Is the Rich Results Test enough for monitoring on its own?

No. The Rich Results Test only ever checks one URL at a point in time. For ongoing control across the whole site you need the Search Console rich result status reports — they aggregate across the real index and show trends, so you spot newly appearing errors early after a deployment.

Themenuebersicht

Technisches SEOStructured Data