Rich Results Test Guide for Schema Validation | Semantec SEO
MIRENAby Semantec SEO
Menu

Governance and validation

Use the Rich Results Test for Google features, not for every Schema.org type

The Rich Results Test reports which Google supported rich result features a code sample or URL may qualify for and identifies critical and recommended property issues.

Follow the implementation model Return to the schema hub
Tool guide 5 decisions 6 checks Reviewed 2026-07-27

Current platform reality

Separate Schema.org meaning from Google feature eligibility.

Reviewed 2026-07-27

The tool is not a universal Schema.org validator. Use the Schema Markup Validator for generic vocabulary checks and URL Inspection for the rendered live page.

Use and avoid

Apply the type only when the visible role and evidence support it.

Use when
  • A Google supported structured data feature is being implemented.
  • A code sample needs prelaunch testing.
  • A live URL must be checked after deployment.
  • The team needs to distinguish errors from warnings.
Avoid
  • Testing Service, WebPage, or another generic type and assuming no result means invalid schema.
  • Treating a preview as a display guarantee.
  • Ignoring hidden, stale, or irrelevant marked content.
  • Skipping the live URL after a code only test.

Implementation model

Make the page role, identity, fields, and validation decisions in order.

01

Choose code or URL mode

Use code for isolated prelaunch checks and URL for the rendered page.

02

Read detected items

Confirm the tool found the intended Google feature.

03

Fix critical errors

Required property failures need resolution before eligibility.

04

Review warnings

Recommended fields can improve completeness but are not always mandatory.

05

Inspect the live URL

Use URL Inspection and Search Console after deployment.

Acceptance checks

Do not approve the markup because the JSON parses.

The content, entity ownership, canonical URLs, policy state, and maintenance source must also pass.

Check

Correct target

The tested type is a current Google supported feature.

Check

Complete code

The sample includes the real page values.

Check

Visible match

Every field corresponds to visible content.

Check

Rendered output

The URL mode sees the final DOM.

Check

No guarantee wording

The result is described as eligibility only.

Check

Generic validation

Schema.org types outside Google support use the correct validator.

Primary sources

Use current Google and Schema.org documentation as the source of truth.

Questions

Rich Results Test Guide for Schema Validation questions.

What does a valid result mean?

It means the markup passes the tested Google feature requirements. It does not guarantee display.

Why is a generic type missing from the tool?

The tool focuses on Google supported rich result features, not the entire Schema.org vocabulary.

Should code and URL mode both be used?

Use code mode before release and URL mode after the final page is live and renderable.

What follows testing?

Inspect the live URL, monitor Search Console, and recheck after template or content changes.

Next route

Prepare schema cues after visible copy, entity ownership, and URLs are approved.

MIRENA can audit the page role, identity, fields, current feature support, and validation route. Production markup still needs human review and live testing.

Founder access is €20 every 30 days excluding VAT for one seat and one active MIRENA instance. OpenAI account rules and usage limits remain separate.

Open MIRENA Open the schema hub