How to Use the Rich Results Test Alongside Search Console
Master the Rich Results Test + GSC combo for full schema validation. Step-by-step guide to validate structured data, fix errors, and earn rich results fast.
The Problem: You're Flying Blind on Schema
You've shipped. Your site has content. But Google isn't showing your pages with rich results—those fancy snippets with ratings, prices, or event details that grab clicks.
The brutal truth: most founders never validate their structured data. They add schema markup, hope Google picks it up, and wonder why their CTR stays flat.
The fix is simple. The Rich Results Test and Google Search Console work together. One tells you if your schema is valid. The other shows you if Google actually cares.
This guide walks you through both, step by step.
Prerequisites: What You Need Before Starting
Before you test anything, get your foundation in place.
You'll need:
- A live website with at least one page of content
- Access to Google Search Console (if you haven't set it up yet, do that first—it takes 10 minutes)
- A page with structured data markup already in place (JSON-LD, microdata, or RDFa)
- A modern browser (Chrome, Firefox, Safari, or Edge)
- 15 minutes of uninterrupted time
Optional but recommended:
- Linking GA4 with Google Search Console to track rich results performance
- Access to your domain's coverage report in Search Console
- A text editor or IDE to edit your schema markup if needed
If you don't have schema markup yet, that's fine. We'll show you how to validate it once you do.
Understanding the Two Tools: Rich Results Test vs. Search Console
These tools do different jobs. Confusing them wastes time.
The Rich Results Test is a validator. It reads your code and tells you:
- Is your schema markup syntactically correct?
- Does it match Google's requirements for rich results?
- What errors or warnings exist?
- What rich result types are eligible on this page?
Google Search Console is a monitoring tool. It tells you:
- Is Google actually indexing your pages?
- Are rich results appearing in search results?
- How many impressions and clicks are you getting from rich results?
- What rich result types does Google recognize on your site?
Think of it this way: the Rich Results Test is your quality control. Search Console is your performance dashboard.
You need both. One validates the code. The other validates the results.
Step 1: Access the Rich Results Test
Start here. This is where you validate your schema markup.
Open the Rich Results Test:
Go to Google's Rich Results Test. No login required.
You'll see a clean interface with two input options:
- A URL field (top)
- A code field (bottom)
Choose your input method:
If your page is already live and publicly accessible, paste the full URL into the URL field. Example: https://yoursite.com/product-page
If your page isn't live yet, or if you're testing code locally, paste your HTML directly into the code field. Copy the entire HTML from your page source, including the <head> and <body> tags.
Why this matters: The Rich Results Test reads your actual page code. If your schema markup is embedded in JavaScript and doesn't render on the server, the test might not see it. If you're using a framework like Next.js or Vue, make sure your schema is server-rendered or included in the static HTML.
Click the test button and wait 10-30 seconds. The tool crawls your page and parses the schema.
Step 2: Read Your Rich Results Test Report
The report breaks down into three sections. Read them in order.
The Status Bar (Top)
You'll see one of three outcomes:
- Green checkmark + "Rich results eligible": Your schema is valid and matches Google's requirements. Rich results can appear in search.
- Yellow warning icon + "Warnings found": Your schema is valid, but it's missing optional properties or has non-critical issues. Rich results can still appear, but you're leaving value on the table.
- Red X + "Errors found": Your schema has critical errors. Rich results won't appear until you fix them.
If you see errors, don't panic. Most are fixable in 5 minutes.
The Rich Results Section (Middle)
This shows what rich result types Google detected on your page. Examples:
- Product (with price, rating, availability)
- Article (with headline, image, publish date)
- Event (with date, location, ticket URL)
- Recipe (with ingredients, cook time, rating)
- FAQ (with question-answer pairs)
If you added schema markup for a product but Google only detects an article, you have a syntax error or missing required fields.
The Errors and Warnings Section (Bottom)
This is where the actionable feedback lives.
Each error or warning includes:
- The property name (e.g., "image", "price", "description")
- What's wrong (e.g., "Missing recommended property", "Invalid value")
- Where it appears in your code
For example: "Missing recommended property 'image'. Add an image URL to your schema."
Click on any error to see the exact line of code causing the issue.
Step 3: Fix Schema Errors Before Moving Forward
If you have errors (red X), fix them now. Warnings can wait.
Common errors and 2-minute fixes:
Missing required properties
Each rich result type requires certain fields. For a product, you need:
name(product name)description(what it does)offers(withpriceandpriceCurrency)
Add the missing property to your schema markup. If you're using JSON-LD, it looks like this:
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Wireless Headphones",
"description": "Noise-cancelling Bluetooth headphones",
"offers": {
"@type": "Offer",
"price": "99.99",
"priceCurrency": "USD"
}
}
Invalid data types
If you put text where a number is expected (e.g., "price": "ninety-nine" instead of "price": "99"), the test will flag it. Fix the value to match the expected type.
Malformed JSON
Missing commas, extra quotes, or unmatched brackets break the entire schema. Use a JSON validator to find syntax errors. Copy your schema into the validator, and it'll highlight exactly where the problem is.
After fixing, re-test:
Update your code, save it, and run the Rich Results Test again. Paste the URL or code again. The test should now show fewer (or zero) errors.
Pro Tip: Keep the Rich Results Test open in one tab while you edit your code in another. Test-edit-test cycles are fast. You'll catch and fix errors in minutes, not hours.
Step 4: Set Up Google Search Console (If Not Already Done)
Now that your schema is valid, you need to monitor it in production.
Google Search Console is where you see if your rich results are actually appearing in search results.
If you haven't set up Search Console yet:
Follow our 10-minute setup guide. You'll verify your domain and submit your sitemap. This tells Google to crawl and index your pages.
If you already have Search Console:
Move to Step 5. You're ready to monitor rich results.
Step 5: Submit Your Sitemap in Search Console
Search Console needs to know about your pages. A sitemap speeds up indexing.
To submit your sitemap:
- Sign in to Google Search Console
- Select your property (your domain)
- Click Sitemaps in the left menu
- Paste your sitemap URL (usually
yoursite.com/sitemap.xml) - Click Submit
Google will crawl your sitemap and index your pages. This usually takes 24-48 hours, but can be faster.
Why this matters: Without a sitemap, Google crawls your site slowly. With one, Google discovers new pages faster and sees your schema markup sooner. Learn more about submitting sitemaps here.
Step 6: Use the URL Inspection Tool to Validate Individual Pages
Once your sitemap is submitted, Google crawls your pages. The URL Inspection tool shows you what Google sees.
To inspect a page:
- In Search Console, go to URL Inspection (search bar at the top)
- Paste the full URL of a page with schema markup
- Click Inspect
Google will crawl that page on-demand and show you:
- Is the page indexed?
- What rich result types does Google detect?
- Are there any crawl errors?
- When was it last crawled?
The key section: "Enhancements"
Scroll down and look for "Enhancements." This shows which rich result types Google found on your page.
If your schema is valid but Google shows "No enhancements detected," it usually means:
- Google hasn't crawled the page yet (wait 24 hours and re-inspect)
- Your schema is server-side rendered incorrectly
- Your schema is in a JavaScript file that isn't being rendered
Learn more about the URL Inspection tool and how to diagnose indexing problems.
Step 7: Monitor Rich Results Performance in Search Console
Once Google indexes your pages, you can see if rich results are actually showing in search results.
To view rich results performance:
- In Search Console, click Enhancements in the left menu
- Select the rich result type you want to monitor (e.g., "Product", "Article", "FAQ")
- You'll see a table with:
- Valid: Pages with valid schema
- Warning: Pages with schema issues
- Error: Pages with broken schema
- Excluded: Pages Google detected but won't show rich results for
The performance graph shows:
- How many impressions your rich results are getting
- How many clicks they're driving
- Your click-through rate (CTR)
Rich results typically boost CTR by 20-50%. If you're not seeing clicks, it usually means:
- Your pages aren't ranking high enough to show rich results (they're below position 10)
- Your rich results aren't compelling (e.g., missing images or ratings)
- Google is still crawling your pages (wait 48 hours)
Read our guide to understanding Search Console's Performance report for more details.
Step 8: Compare Rich Results Test Results with Search Console Data
Here's where the two tools work together.
The Rich Results Test tells you: "Your schema is valid."
Search Console tells you: "Google sees your schema and is showing rich results."
They should match. If they don't, you have a problem.
Scenario 1: Rich Results Test shows valid, Search Console shows valid
Perfect. Your schema is working. Monitor performance over time and watch for CTR improvements.
Scenario 2: Rich Results Test shows valid, Search Console shows warnings
This usually means:
- You're missing optional properties (the test shows warnings, but rich results still appear)
- Your schema is inconsistent across pages
- Google is interpreting your schema differently than the test tool
Fix the warnings in your schema markup and re-test. Most warnings are about missing optional fields like image, rating, or review.
Scenario 3: Rich Results Test shows errors, Search Console shows errors
Your schema is broken. Fix the errors in the Rich Results Test, re-test, and wait 24 hours for Google to re-crawl.
Scenario 4: Rich Results Test shows valid, Search Console shows no enhancements
Google hasn't crawled your page yet, or your schema isn't being rendered properly.
Wait 48 hours and re-inspect the URL. If it still shows no enhancements, your schema might be in JavaScript that isn't being server-rendered. Move your schema to the static HTML or use a framework that renders it on the server.
Pro Tip: Run the Rich Results Test once when you publish a page. Then check Search Console weekly to see if Google has indexed it and detected rich results. If Search Console shows errors after 48 hours, the issue is usually rendering, not validation.
Step 9: Set Up Search Console Alerts for Rich Results Issues
Search Console can notify you when problems arise.
To enable alerts:
- In Search Console, click the bell icon (top right)
- Click Manage notifications
- Look for "Enhancements" section
- Enable alerts for the rich result types you care about
You'll get an email if:
- A large percentage of your pages have schema errors
- Google detects a new issue affecting your rich results
- A previously valid page now has errors
Learn which Search Console alerts actually matter and which you can ignore.
Step 10: Link GA4 to See Rich Results Impact on Traffic
You can see if rich results are actually driving traffic to your site.
To link GA4 to Search Console:
- In Google Analytics 4, go to Admin > Data streams
- Click your web data stream
- Scroll down and click Enhancements
- Toggle on Google Search Console
- Click Connect and select your Search Console property
Once linked, you can see in GA4:
- Which search queries are driving traffic
- Which pages are getting impressions
- Your CTR by search query
- How many clicks are coming from rich results specifically
Follow our detailed GA4 + Search Console setup guide for step-by-step instructions.
Advanced: Testing Multiple Pages at Scale
If you have 100+ pages with schema markup, testing them one at a time is slow.
Use Search Console's Enhancements report instead:
- Go to Enhancements in Search Console
- Select the rich result type
- Click the Errors tab
- You'll see all pages with schema errors, sorted by error type
This is faster than testing individual pages. Fix the most common errors first (they usually affect the most pages).
To validate new schema before publishing:
If you're adding schema to 50 new pages, test one page in the Rich Results Test first. Once that page is valid and live, the rest should work the same way.
Advanced: Schema Markup Beyond the Rich Results Test
The Rich Results Test only validates schema that Google uses for rich results. But schema.org has hundreds of types.
For broader schema validation, use Schema.org's Live Tester:
This tool validates all schema.org types, not just those that produce rich results. It catches errors that the Rich Results Test misses.
For example, if you're using schema for internal site linking or knowledge graph optimization, Schema.org's Live Tester will catch issues the Rich Results Test won't.
Common Mistakes to Avoid
Mistake 1: Testing localhost or staging URLs
The Rich Results Test can't crawl pages that aren't publicly accessible. Always test live, published URLs.
Mistake 2: Forgetting to republish after fixing schema
You fix your schema in the code, but don't deploy it. The test still sees the old, broken version. Always deploy before re-testing.
Mistake 3: Ignoring warnings
Warnings don't block rich results, but they reduce their quality. A product without an image is less likely to get clicks than one with an image. Fix warnings too.
Mistake 4: Expecting instant results
Google doesn't index pages instantly. After you publish schema markup, wait 24-48 hours before checking Search Console. If you re-test too early, you'll see outdated data.
Mistake 5: Using the Rich Results Test as your only validation tool
The Rich Results Test only tells you if your schema is valid. It doesn't tell you if Google is actually using it. Always pair it with Search Console.
Troubleshooting: When Things Go Wrong
Problem: Rich Results Test shows valid, but Search Console shows nothing
Cause: Google hasn't crawled your page yet.
Fix: Wait 48 hours. Then use the URL Inspection tool to request crawling. Google will re-crawl the page immediately.
Problem: Rich Results Test shows errors, but you can't figure out what's wrong
Cause: Your JSON is malformed or your schema is using incorrect property names.
Fix: Copy your schema into a JSON validator. Fix any syntax errors. Then check the official schema.org documentation for your rich result type. Make sure you're using the correct property names and data types.
Problem: Search Console shows warnings but not errors
Cause: You're missing optional properties or using deprecated schema versions.
Fix: Review the warnings in Search Console. Add missing properties (like image or rating). Update your schema to the latest version.
Problem: Your schema works in the Rich Results Test but not on your live site
Cause: Your site uses JavaScript to render schema. The Rich Results Test sees the server-rendered HTML, but Google's crawler doesn't.
Fix: Move your schema to the static HTML in your page's <head> tag, or use a framework that server-renders it. Avoid putting schema in JavaScript that runs in the browser.
The Workflow: Rich Results Test + Search Console
Here's the repeatable process:
Before publishing:
- Write your schema markup
- Test it in the Rich Results Test
- Fix any errors
- Fix any warnings (optional but recommended)
After publishing:
- Wait 24 hours
- Use URL Inspection to check if Google crawled it
- Wait another 24 hours
- Check the Enhancements report in Search Console
- Monitor CTR and impressions over the next week
Weekly:
- Check Search Console for new errors
- Fix any issues
- Track CTR improvements
Monthly:
- Review your Enhancements report
- Identify which rich result types drive the most clicks
- Prioritize adding schema to more pages of those types
Key Takeaways
The Rich Results Test validates your code. Search Console validates your results.
You need both. One without the other leaves you flying blind.
Rich results boost CTR by 20-50%. But only if your schema is valid and Google knows about it.
The workflow is simple:
- Write schema markup
- Test it in the Rich Results Test
- Fix errors
- Publish
- Monitor in Search Console
- Iterate
Don't skip steps. Founders often skip the testing phase and wonder why their rich results don't show up. The Rich Results Test takes 30 seconds and saves you 48 hours of debugging.
Pair the Rich Results Test with Search Console for full validation. The test tells you if your schema is syntactically correct. Search Console tells you if Google actually cares.
Monitor performance. Rich results are worthless if they don't drive clicks. Check your CTR weekly. If it's not improving, either your pages aren't ranking high enough, or your rich results aren't compelling.
Next Steps: Beyond Rich Results
Once your rich results are working, expand your schema strategy.
Consider adding schema for:
- Internal site linking (helps Google understand your site structure)
- Breadcrumbs (improves navigation in search results)
- Author information (builds credibility)
- Organization details (shows up in knowledge panels)
Track your progress.
Use our free SEO tool stack to set up monitoring across all your tools. Rich results are one piece of SEO. You also need to track rankings, organic traffic, and crawl health.
Do a quarterly review.
Run a quarterly SEO review to validate your schema strategy. Check which rich result types are driving the most traffic. Double down on what works.
The Bottom Line
Ship fast. But don't ship blind.
The Rich Results Test takes 30 seconds. Search Console takes 2 minutes to set up. Together, they give you full visibility into your schema markup and its impact on search traffic.
You've already built something worth showing. Make sure Google shows it to the right people.
Test your schema. Monitor it in Search Console. Iterate. That's it.
No agency. No guessing. Just data.
Get the next one on Sunday.
One short email a week. What is working in SEO right now. Unsubscribe in one click.
Subscribe on Substack →