Sources checked 15 November 2026. All businesses, search phrases, messages and figures in the examples are fictional UK examples; illustrative only, not Craig’s client work or measured results.
Review basis: a check of official public documentation, not firsthand testing, a logged-in account review or a paid-plan comparison. No test scores or screenshots are presented as real results.
Google’s Rich Results Test checks structured data for supported Google search features. It helps diagnose markup, but a valid result is not a promise that Google will display the feature.
1. Check the intended feature first
- Read Google’s current guidance for the page type.
- Confirm the content genuinely qualifies.
- Make the markup match visible information.
- Do not add invented ratings, prices or reviews.
The test is not a universal validation of every Schema.org type. A type can be meaningful schema without being supported as a Google rich result.
2. Choose URL or code testing
- URL: tests a page the tool can fetch publicly.
- Code: checks a supplied snippet before publication.
- Device: the tool allows smartphone or desktop testing.
Protected resources are not available to a public fetch. Do not expose private pages just to make the test work, and do not paste customer data, credentials or unpublished sensitive material into a public tool.
3. Turn a warning into a decision
Harbour & Hide, Glasgow — fictional UK example; illustrative only
Assumed page: an individual walking-jacket product page with visible product information.
Assumed finding: the test recognises a supported product item but reports missing or invalid information.
Decision: check the exact requirement, correct the markup using verified product details and run the test again.
Do not do: invent a rating or apply individual-product claims to an entire category grid.
This is an invented workflow, not a captured test result. No eligibility, warning or search appearance was checked for the fictional shop.
4. Distinguish errors from recommendations
Expand individual findings and read the relevant feature guidance. Errors can prevent eligibility; warnings may identify recommended information rather than a complete failure.
- Check the rendered source associated with the finding.
- Confirm the information is accurate and visible where required.
- Investigate loading problems if repeat results differ.
- Recheck after publishing the correction.
A plugin reporting “schema added” does not prove Google fetched the expected markup. The schema-plugin article provides background, but current feature requirements still need checking.
5. Separate testing from search appearance
- A live test does not prove that Google indexed the page.
- Valid markup does not guarantee a rich result for every query.
- A preview is illustrative, not a promised appearance.
- Quality and spam policies apply beyond syntax.
Use Search Console for indexing and available enhancement evidence. Do not count a test pass as a traffic gain.
6. Know when another check is needed
The tool suits supported Google rich-result diagnosis. Broader vocabulary validation, full-site crawling and commercial measurement require different checks.
For shops, the category-page guide explains why the page’s purpose matters. Do not treat every listing as a single product.
Limitations and next step
This review checks public documentation only. No logged-in workflow, actual markup trial or rich-result uplift was tested.
Choose one eligible page type, verify the facts and check one page before changing an entire template.
Sources
Sources checked 15 November 2026. The workflow is editorial advice, not a ranking guarantee.

