How to check your schema is working with Google’s Rich Results Test

How can you tell whether your schema is working?

Use Google’s Rich Results Test to see whether Google can read eligible structured data on a live page or draft code. Structured data is code that labels page content for search systems. A pass confirms readable markup for supported rich result types, while search display still depends on Google’s own checks.

seo consultant reviewing website data with colleague in office

The Rich Results Test confirms readability, not search display

Google’s Rich Results Test checks whether Google can detect structured data that qualifies for supported rich result types. It can test a live page address or URL, and it can also test a code snippet before that code goes live.

Readable by Google and visible in Search are separate outcomes. A valid result means the tool found supported markup and no blocking technical error for the item it tested. Google still decides whether to show a rich result.

Schema.org is the wider vocabulary for schema markup, and the test does not check every possible Schema.org use. It focuses on rich result eligibility for Google-supported types. For a service website, useful markup normally describes real page content, such as Organisation, LocalBusiness, Breadcrumb, Article or Video information.

Google’s tool supports JSON-LD, short for JavaScript Object Notation for Linked Data; RDFa, short for Resource Description Framework in attributes; and Microdata. In practice, we care less about the format label and more about the business question: can Google read the right meaning from the page?

A reliable schema test starts with the version Google can fetch

Schema testing works best when you test the same page Google can reach and render. Draft code has value, but the live page shows whether the markup survives the website template, scripts and access controls.

• Choose URL or Code mode. Use URL mode when the page is published. Use Code mode when you want to test schema before publishing, or when a developer is adjusting the markup.
• Test the live page where possible. The live URL check gives the closest view of what Google can inspect on the actual website.
• Use Code mode for draft markup. Choose Code, paste the structured data or page code, run the test, then rerun it after edits.
• Check the user agent. The tool can run with a smartphone or desktop user agent, which means the crawler identity used for the test. The default is smartphone, so mobile rendering matters.
• Confirm access. Pages and resources need to be available to an anonymous internet user. A firewall, password protection, robots.txt file that blocks crawlers, or a noindex directive that tells search engines not to index the page can stop a proper URL test.
• Rerun after changes. A single pass on draft code does not prove the published page is fixed.

At First Place SEO, we treat this as a visibility diagnostic, not a code hunt. The useful test asks whether Google can access the page, render it, find the structured data and connect that markup to what a user can read on the page.

Test results become useful only after interpretation

A Rich Results Test result is evidence, not a performance score. The result tells you what Google found, what blocked eligibility and which details deserve review before you decide whether the issue belongs with content, development or wider search engine optimisation work.

A green result usually means valid items were detected. A crawl failure means the page could not be fetched. A syntax error means the markup cannot be read correctly. “No items detected” means Google found no supported rich result structured data in the rendered page, although other Schema.org markup may still exist.

The item view matters. You can expand detected items to see the rich result type, the fields found and the errors or suggestions attached to them. The code explorer uses rendered source code, which helps reveal whether the markup appears after the page has fully loaded.

Errors block eligibility for the affected item

Errors need attention because they stop the affected structured data item from qualifying for its rich result type. Missing required properties are a common cause. A required property is a field Google needs for that rich result, such as a mandatory name, image or other page-specific detail listed for that feature type.

One page can also expose a wider template problem. If every service page uses the same markup block and one required field is missing, the test result on a single URL may be pointing at a site-wide issue.

Warnings point to missing recommended detail

Warnings do not always block eligibility in the same way as errors, but they still deserve judgement. A warning often means Google found the basic item but wanted extra recommended information that could make the markup more complete.

We do not treat warnings as automatic failures. We look at the page type, the business value of that rich result and whether the missing detail is genuinely present on the visible page. Adding markup for information users cannot see creates a different problem, because structured data needs to match the page content.

First Place SEO Website Strategy Meeting - illustrative Image

Valid schema can still stay out of Google’s search display

A valid schema test confirms that Google can read the markup. Rich result display remains a separate choice made by Google, based on its systems, feature support and quality checks.

Several factors sit outside a simple pass result. Google can decide not to show a rich result, the page can fail quality guidelines, or the markup can describe content that is misleading, irrelevant or hidden from users. Automated testing catches technical problems, but it does not judge every quality issue.

Older advice can also send service businesses in the wrong direction. Google Search Central’s documentation updates record that the frequently asked question, or FAQ, rich result feature stopped appearing in Google Search from 7 May 2026, and the documentation was removed in June 2026. Adding FAQPage markup for old-style Google FAQ dropdowns is no longer a sensible visibility plan for an ordinary service website.

Artificial intelligence, or AI, search adds another reason to be precise. Clear structured data can help machines interpret page meaning, but passing the Rich Results Test does not guarantee inclusion in AI Overviews, ChatGPT, Gemini or Grok. The safer target is machine-readable consistency: the markup, headings and visible content should point to the same business information.

Live verification is the end point after a schema fix

When the fix is deployed, the test needs to move from draft validation to live verification. Retest the affected URL in Google’s Rich Results Test, then use Google Search Console and the URL Inspection tool to see what Google can inspect after the page is live.

Reporting can lag behind the fix. Search Console rich result status reports may still show an error until Googlebot, Google’s crawler, has revisited or reprocessed the page. If the same issue appears across many URLs, the likely fault sits in the content management system template rather than one page’s copy.

Manual actions deserve a quick check when rich result eligibility looks wrong despite valid markup. A structured data manual action can remove eligibility for rich result appearance, although it does not change how the page ranks in Google web search. The Manual Actions report in Search Console is the right place to verify that point.

At First Place SEO, we connect schema checks to wider search clarity. A technically valid markup block has limited value if the visible page, business details and page intent are sending mixed signals.

The common misconception is that valid schema means the job is done. It does not. A green test result is a checkpoint. The work is complete only when the live page, its visible content and its structured data tell the same story to Google.

seo consultant discussing technical website audit with colleague

Questions we get asked about schema testing

Can you test schema before a page is published?

Yes. Google’s Rich Results Test has a Code mode where you can paste draft markup or page code, then rerun the test after edits. A live URL test is still needed after publishing.

Why does Search Console still show a schema error after the fix?

Search Console can keep showing an old error until Google has crawled or reprocessed the live page again. Retest the live URL first, then use URL Inspection to check what Google sees.

Which schema types matter most for a service website?

Service websites usually benefit from accurate Organisation, LocalBusiness, Breadcrumb, Article or Video markup where those types match the visible page. Review snippet markup needs particular care because it must reflect real, visible review content.

Should you add FAQ schema for Google FAQ dropdowns?

No. Google deprecated the FAQ rich result feature in 2026, so ordinary service businesses should not add FAQPage markup expecting those dropdowns in Google Search.

Can structured data help AI systems read your site?

Structured data can make page meaning clearer to machines when it matches the visible content. It does not secure inclusion in AI answers, so it should sit alongside clear page copy and consistent business information.