Rich Results Testing Workflow Before Site Release
Key takeawayRich result testing tools flag syntax and missing required properties, but testing the wrong way produces misleading conclusions. This sheet fixes the workflow: choose the type, test one page, read warnings, batch verify, then check the regression.
Industries and use cases
- Validating product, breadcrumb, FAQ and video markup before launch
- Confirming markup survived a template change
- Locating the cause of errors reported in Search Console
- Handing markup maintenance to a new team member
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Confirm the result type | Decide which rich result the page should produce before testing; a page declares only types that match its content | High | Test Product on product pages, Article on posts and FAQPage on Q&A blocks without stacking unrelated types. |
| Use a public URL | The tested URL returns 200 without login and matches what users see | High | Pages behind access restrictions cannot be fetched; open access or switch to code snippet mode. |
| Required properties | All required fields pass in the tool with no missing-property message | High | Add name, image, price, currency and validity as prompted; one gap invalidates the whole item. |
| Optional properties | Recommended fields are added where they carry business value rather than to chase a perfect score | Medium | Prioritise ratings, brand and availability, which buyers actually look for. |
| Values match the page | Price, rating, availability and dates in the markup are identical to the visible text | High | Render markup from page data so hand-written values cannot drift. |
| Date and currency format | Dates use ISO 8601 and prices use three-letter currency codes such as USD or EUR | Medium | Format at template level and never mix 2026/11/21 with 11-21-2026. |
| Mobile retest | The same URL returns identical results in the mobile test | Medium | Responsive templates often hide fields; markup should not declare fields hidden on mobile. |
| Warning handling | Each warning is assessed, mismatched markup removed and format issues fixed | Medium | Warnings do not block display but weaken confidence; record each decision. |
| Batch validation | Three URLs per core template are validated with consistent results | Medium | Batch testing exposes edge cases that appear only on part of the data. |
| Search Console regression | Within 3 to 7 days after release, valid items increase and errors fall to zero in the rich results report | High | Reports lag, so do not rewrite code just because nothing appears on day one. |
| Snippet archive | Passing snippets are archived with page type and date | Low | Archives let you compare later changes and find which release broke what. |
| Retired types | Markup for discontinued rich result types is removed | Low | Check the supported types list periodically and delete deprecated markup to cut dead code. |
Common misjudgements
- A clean tool report is taken as the end of the job: valid syntax does not mean true content, and price or rating must still match the page.
- Debugging repeatedly on a staging environment, where restricted pages cannot be fetched and the conclusion is unusable.
- Applying one markup type to every page, so an article declares product data and the markup loses credibility.
How to use this checklist
- Pair with the structured data sheet: this one covers tool workflow, that one covers field conventions.
- Run after every template release and do a full quarterly regression.
- Archive test screenshots with release records to trace where a problem started.
FAQ
Does passing the test guarantee a rich result?
No. The tool only validates syntax and required fields; display depends on content quality and context.
Can one page carry several rich result types?
Yes, provided each type has real matching content and they do not conflict.
Why do the test tool and Search Console disagree?
They fetch at different times and scopes: the tool tests a single page while the report aggregates the whole site with a delay.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
Full Launch Checklist for a New B2B WebsiteBrand Entity Review for AI Overviews and Answer EnginesDomain, DNS and HTTPS Verification for a New SiteFinal Pre-Publish Review for Content Used as an AI Sourcehreflang Configuration Review for Multilingual SitesNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.