Category : CRO & UX

Tools

Rich Results Test

FREE · OFFICIAL GOOGLE

The official view of what Google extracts from your pages.

Why I use it

Pasting code into a validator is not the same as testing the public URL : theme, apps, and injections matter.

Catches syntax errors and ineligible rich-result types.

How I use it : mini guide

After every schema change (Product, FAQ, Breadcrumb), I test the live PDP or target page.

  1. 1. Live URL

    What Googlebot can see, not a staging site behind auth.

  2. 2. Before / after

    Screenshots of recognised fields for the client.

  3. 3. Duplicates

    If multiple JSON-LD blocks describe the same product, I consolidate or remove redundant sources.

  4. 4. Search Console alignment

    I then watch enrichments in GSC for that page type.

Concrete Shopify example

Duplicate FAQ between theme and SEO app: live test showed two FAQPage blocks ; removed redundant injection.

Limits I've identified

  • Not a content or internal linking audit.
  • Some valid markup types never show as rich results.
  • Lag between deploy and SERP display.