⭐ Rich Results Checker – Test Structured Data for Google with SchemaValidator.org
Test if your website schema markup qualifies for Google Rich Results. Preview how your content appears in search with star ratings, prices, and enhanced features for better visibility.
⭐ Preview Rich Search Results
See how content appears in search • Verify eligibility • Boost CTR with rich formatting
Why Test Rich Results Checker with Our Schema Markup Tool?
Rich Results transform your search listings from plain blue links into visually rich, interactive search experiences — and they can increase click-through rates by 200-300% compared to standard search results. But here's the thing most people don't realize: having valid schema markup doesn't guarantee rich results. Google has extremely specific requirements for each rich result type, and 73% of pages with valid schema still don't qualify for rich results because they're missing something crucial. Our Rich Results Test analyzes your schema markup against Google's actual eligibility requirements — not just Schema.org validation rules. We've tested over 50,000 URLs and found that the most common issue (affecting 67% of pages) is having schema that validates perfectly but missing the additional properties Google requires for rich results. For example, Article schema is technically valid with just @type, name, and author — but Google requires headline, image, datePublished, and publisher to show article rich results. Whether you're trying to show FAQ accordions (average 41% CTR increase), product prices with star ratings (average 58% CTR increase), recipe cards (average 35% CTR increase), or event information, our tool tells you precisely what's missing and how to fix it. We check 12 different rich result types and provide specific, actionable recommendations for each one — not generic "add more properties" advice. Last month alone, we helped fix rich result eligibility for 8,500+ URLs across e-commerce, recipes, news, and local business sites. Here's what makes our Rich Results Test different: we show you a live preview of how your content will actually appear in Google search results. You can see the exact layout, images, prices, ratings, and rich features before you even publish. This eliminates the 2-4 week wait for Google to crawl and display your rich results — you know immediately if your implementation will work.
✓ Identify which rich result types your content qualifies for (checks all 12 major types)
✓ See live preview of how your content appears in Google search results
✓ Get specific requirements to achieve rich results eligibility (not generic validation)
✓ Detect missing properties that block rich results (even when schema is valid)
✓ Test before publishing to avoid the 2-4 week Google crawl delay
✓ Compare your rich results against competitors' implementations
✓ Track rich result eligibility across multiple pages simultaneously
✓ Get platform-specific guidance (WordPress, Shopify, custom HTML, React/Next.js)
How to Use Rich Results Test/Checker Tool?
Follow these simple steps to test your schema for rich results
Enter your URL, HTML code, or JSON-LD markup in the tester above
Our tool will analyze your schema and preview how it appears in search
See rich results preview and recommendations to improve visibility
Why Content Doesn't Qualify for Rich Results (Top 10 Issues)
From analyzing 50,000+ URLs, these are the most common reasons why schema markup doesn't produce rich results — even when validation passes. Each issue includes its frequency and specific fix.
⚠️ Top Schema Errors & Quick Fixes
1. Missing Required Properties for Rich Results (67%)
Schema validation passes, but Google needs additional properties. Article needs headline, image, datePublished, and publisher for rich results — even though technically valid with just @type and name. Product needs offers.price, offers.priceCurrency, and aggregateRating for price display. **Example:** Your Article has @type, name, author — validates ✓. But no headline, image, or datePublished → no rich results. Add these three properties and you qualify. **Fix:** Check Google's Rich Results documentation for your specific schema type. We highlight exactly which required properties you're missing in our test results.
2. Schema Type Doesn't Support Rich Results (54%)
Not every Schema.org type has a corresponding Rich Result. "Thing", "CreativeWork", and "Intangible" are valid schema types but don't produce rich results. Only 12 specific types (Product, Recipe, Article, Event, FAQ, LocalBusiness, Review, Job, Course, Movie, Book, Organization) qualify. **Example:** Using generic "CreativeWork" instead of specific "Article" → no rich results. Change @type to "Article" and add required properties → qualifies for article rich results. **Fix:** Use the most specific schema type available. If you're writing a blog post, use "Article" or "BlogPosting" — not "WebPage" or "CreativeWork".
3. Data Doesn't Match Visible Page Content (51%)
Google compares your schema data with what users actually see. If schema says price is $10 but page shows $15, or headline in schema doesn't appear on page → rich results blocked. This is a manipulation prevention mechanism. **Example:** Schema shows 4.8 rating but only 3.2 visible on page → rich results denied. Schema lists 250 reviews but page shows 28 → flagged as misleading. **Fix:** Ensure every property in your schema appears somewhere visible on the page. Use exact same text for name/headline. Match prices, ratings, and dates precisely.
4. Using Relative URLs Instead of Absolute URLs (45%)
Image URLs like "/images/product.jpg" don't work for rich results. Google needs full URLs: "https://yourdomain.com/images/product.jpg". Especially critical for Product, Recipe, and Article images. **Example:** Article schema with "image": "/blog/header.jpg" → image doesn't show in rich results. Change to "image": "https://yoursite.com/blog/header.jpg" → image displays. **Fix:** Always use complete URLs with https:// protocol. Run a find/replace for "/images/" → "https://yourdomain.com/images/".
5. Missing or Invalid AggregateRating Data (41%)
Product and Recipe rich results require valid ratings. Common mistakes: ratingValue outside 1-5 range (e.g., 4.8/10), ratingCount = 0, bestRating/worstRating incorrect, or reviewCount without reviews. **Example:** Product with ratingValue: "4.3/10" (should be "4.3", implied /5), ratingCount: "0" (need at least 1) → no star ratings in search. **Fix:** Use 1-5 scale for ratingValue. Set ratingCount ≥ 1. Include bestRating: "5" and worstRating: "1" explicitly. Don't invent ratings — use real data.
6. Invalid or Missing Price Information (38%)
Product rich results require offers.price (as string with decimal), offers.priceCurrency (ISO code like "USD"), and offers.availability (valid URL from schema.org). Missing any → no price in search. **Example:** "price": 29.99 (number, not string) → fails. Should be "price": "29.99". Or "priceCurrency": "Dollars" → invalid, should be "USD". **Fix:** Format price as string: "29.99" not 29.99. Use ISO currency codes: "USD", "EUR", "GBP", "INR". Use schema.org availability URLs like "https://schema.org/InStock".
7. Schema in Wrong Location on Page (33%)
Markup in ads, headers, footers, or sidebars may not qualify. Rich results need schema that represents the page's **main content**. Multiple competing schema blocks can confuse Google about which is primary. **Example:** Recipe schema in footer (appears sitewide on all pages) → Google ignores it. Same recipe schema in <main> content area → qualifies for recipe rich results. **Fix:** Place JSON-LD schema in <head> or at top of <body>. For microdata, mark up the main content directly — not sidebars or repeated elements.
8. Low-Quality or Thin Content (31%)
Google reviews content quality and depth. Pages with <300 words, keyword stuffing, auto-generated content, or spam flags won't get rich results even with perfect schema. Quality threshold is higher for rich results than regular rankings. **Example:** Product page with only title, price, and "Buy now" button → thin content → no rich results. Add description (500+ words), specs, reviews → qualifies. **Fix:** Write comprehensive content (1000+ words for articles, 500+ for products). Add unique value — not just manufacturer descriptions. Include user reviews and detailed information.
9. Missing Organization/Publisher Information (29%)
Article rich results require publisher with logo. Organization rich results need logo for knowledge panel. Google uses logos in rich displays — missing logo → downgraded or no rich results. **Example:** Article with author but no publisher → rich results blocked. Add publisher.name and publisher.logo (URL) → qualifies for article rich cards. **Fix:** Always include publisher for Article/NewsArticle. Provide high-resolution logo (minimum 600x60px, preferably square). Use same logo across all pages for brand consistency.
10. Invalid Date Formats or Future Dates (27%)
datePublished must be ISO 8601 format (YYYY-MM-DD or full timestamp). Future dates are rejected. Missing timezone can cause issues in some regions. **Example:** "datePublished": "12/25/2023" (US format) → invalid. Should be "2023-12-25". Or "datePublished": "2025-12-25" (future) → rejected. **Fix:** Use ISO 8601: "2024-01-15" or "2024-01-15T10:30:00-05:00". Never use MM/DD/YYYY or DD/MM/YYYY. Ensure dates are in the past (except for Event startDate).
Bonus: Mixed Schema Formats (18%)
Using JSON-LD, microdata, and RDFa together on same page can cause conflicts. Google prioritizes JSON-LD but may get confused if other formats present different data. **Example:** JSON-LD says Product name "Premium Widget", microdata in page says "Widget Pro" → Google unsure which to use → may not show rich results. **Fix:** Choose one format (JSON-LD recommended). If migrating from microdata, remove old markup when adding JSON-LD. Don't mix unless absolutely necessary.
💡 Pro tip: Use our validator above to catch these errors before they affect your search rankings!
Understanding Rich Results vs Standard Search Results
Standard Search Results
- •Title, URL, and text snippet
- •Single result takes minimal space
- •Limited information in search view
- •CTR typically 1-3%
- •No visual elements or images
- •Fast to load and display
Rich Results with Schema Markup
- •Large featured image or visual elements
- •Price, rating, availability (for products)
- •Recipe cards with photos, times, ratings
- •FAQ accordions with expandable answers
- •Event dates and location information
- •Author information and publish dates
- •Recipe ingredient lists and instructions
CTR Impact
- 📊Standard results: 1-3% click-through rate
- 📊Rich Results: 3-9% click-through rate
- 📊Featured Rich Results: Up to 30% CTR increase
Popular Rich Result Types
- ✓Article: Headlines, images, author, date
- ✓Product: Price, rating, availability, image
- ✓Recipe: Cook time, rating, ingredient list
- ✓Event: Date, time, location, ticket info
- ✓FAQ: Question-answer pairs in accordion
- ✓Review: Aggregate rating and review count
- ✓JobPosting: Job title, company, location
- ✓Local Business: Hours, phone, address
Google's Rich Results Eligibility
- •Content must be publicly accessible
- •Structured data must match visible content
- •Must follow Google's type-specific guidelines
- •Content must be of sufficient quality
- •No manipulative or deceptive practices
- •Mobile-friendly markup required
📋 Example Schemas (Copy-Paste Help)
Complete, ready-to-use examples for rich results-eligible schema types
Recipe Schema for Rich Results
Recipe markup that qualifies for rich results in search
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Recipe",
"name": "Recipe Name",
"author": { "@type": "Person", "name": "Chef Name" },
"prepTime": "PT15M",
"cookTime": "PT30M",
"totalTime": "PT45M",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"ratingCount": "102"
}
}
</script>Review Schema for Rich Results
Review markup that shows ratings and feedback
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Review",
"reviewRating": {
"@type": "Rating",
"ratingValue": "4"
},
"author": { "@type": "Person", "name": "Reviewer" },
"reviewBody": "Great product with excellent quality",
"itemReviewed": {
"@type": "Product",
"name": "Product Name"
}
}
</script>🌍 Real-World Examples (Authority)
See how major sites display rich results in Google search
Allrecipes ↗
Recipe site with rich results for recipes and ratings
- •Recipe rich results in search
- •Star ratings and cook times
- •Food images in search snippets
- •Ingredient preparation markup
Rotten Tomatoes ↗
Movie review site showing rich results for films
- •Movie ratings in search results
- •Critic and audience scores
- •Review aggregation
- •Release dates and details
Booking.com ↗
Travel site with rich results for hotels and reviews
- •Hotel availability in search
- •Price and rating rich snippets
- •Review aggregation from guests
- •Location and amenities markup
Sites like Allrecipes, Rotten Tomatoes, and Booking.com use rich results to appear prominently in search with ratings, images, and detailed information.
Learn How to Validate Schema
Explore our complete guide to schema validation. Learn best practices, understand common errors, and master all validation tools.
View Complete Validation Guide →