Avatar Website Design

Google Rich Results Test: How To Validate Schema Markup

Google Rich Results Test: How To Validate Schema Markup

You’ve added schema markup to your website, but how do you know it’s actually working? That’s where the Google Rich Results Test comes in. This free tool from Google lets you validate your structured data and see exactly how your pages might appear in search results with enhanced features like star ratings, FAQ dropdowns, or product pricing.

For small business owners, rich results can make the difference between getting noticed or getting buried on page one. A properly marked-up page stands out with eye-catching elements that boost click-through rates without spending an extra dollar on ads. But if your schema contains errors, you’re missing out on these benefits entirely, and you might not even realize it.

At Avatar Website Design, we build SEO-optimized websites that help small businesses compete online. Part of that process includes implementing clean, validated structured data. Whether you’re working with us or managing your own site, understanding how to test your schema markup is essential knowledge.

This guide walks you through using the Google Rich Results Test step by step, from accessing the tool to interpreting results and fixing common errors.

What the Google Rich Results Test checks

The Google Rich Results Test analyzes your structured data markup to verify whether it meets Google’s requirements for enhanced search results. When you run a test, the tool scans your page or code snippet and identifies any schema.org vocabulary that could trigger rich results. It specifically looks for markup types that Google currently supports, such as recipes, products, articles, events, and local business information.

The tool checks both technical accuracy and eligibility for rich results, but passing the test doesn’t guarantee your page will display enhanced features in actual search results.

Types of structured data it validates

The google rich results test recognizes several markup formats including JSON-LD, Microdata, and RDFa. Your structured data must follow proper syntax rules and include all required fields for the type you’re implementing. Here are the main schema types it validates:

  • Article (Article, NewsArticle, BlogPosting)
  • Breadcrumb (BreadcrumbList)
  • Carousel (ItemList with specific item types)
  • Course (Course with provider details)
  • Dataset (Dataset)
  • Event (Event)
  • FAQ (FAQPage)
  • How-to (HowTo)
  • Job Posting (JobPosting)
  • Local Business (LocalBusiness and subtypes)
  • Product (Product with offers, reviews, aggregateRating)
  • Recipe (Recipe)
  • Review (Review with aggregateRating)
  • Video (VideoObject)

Each type has required and recommended properties that the tool checks against. Missing a required property triggers an error, while missing recommended properties generates warnings.

What it doesn’t check

This tool focuses exclusively on structured data validation and doesn’t evaluate your overall SEO health. It won’t catch issues like broken images, slow page speed, or mobile usability problems. You also won’t get insights about your content quality or keyword optimization through this test. Think of it as a specialized tool that handles one job well rather than a complete site audit solution.

Before you run the test

You need to prepare a few things before using the google rich results test. First, make sure your structured data is actually live on your page. If you’re testing with a URL, the markup must be published and accessible to Google’s servers. Testing a draft version sitting in your local development environment won’t work. You also want to clear your browser cache if you’ve recently made changes to avoid testing an outdated version of your page.

Check your markup format

Verify that your structured data follows proper JSON-LD format if you’re using that method. JSON-LD should appear within a <script type="application/ld+json"> tag in your HTML. You can view your page source (right-click and select "View Page Source" in most browsers) to confirm the markup exists where you expect it. Look for the opening and closing script tags to ensure nothing got cut off during implementation.

Make sure your JSON-LD doesn’t contain syntax errors like missing commas or brackets before running the test, as these will cause immediate failures.

Gather your testing materials

Have either your complete page URL or your code snippet ready to paste into the tool. If you’re testing code directly, copy the entire JSON-LD block including the opening and closing script tags. Testing partial code snippets often leads to confusing results because the tool can’t properly validate incomplete markup.

Run a test using a URL

Testing with a live URL is the simplest way to validate your structured data. This method checks your actual published page exactly as Google sees it, including any dynamically generated content or changes you might have missed in your code editor. You’ll get real results that reflect what search engines will encounter when they crawl your site.

Access the tool

Navigate to the Google Rich Results Test at https://search.google.com/test/rich-results. The interface loads with two tabs at the top: one for URL testing and one for code testing. Make sure the URL tab is selected before you proceed.

Enter your URL and test

Copy your full page URL including the https:// prefix and paste it into the text field. The tool won’t accept partial URLs or relative paths. Click the "Test URL" button and wait while Google fetches your page.

Enter your URL and test

Testing usually takes 10 to 30 seconds depending on your page size and server response time.

Google displays detected structured data types on the right side once the test completes. You’ll see green checkmarks for valid markup, yellow warnings for recommended improvements, and red errors for problems that prevent rich results eligibility. Click any item to expand details about specific issues.

Run a test using code

Testing with code snippets works best when you’re developing structured data before publishing it live or when you want to validate markup from pages behind login walls. This method lets you paste JSON-LD directly into the tool without needing a public URL. You can test experimental changes without affecting your live site or validate markup from development environments that Google can’t access.

Enter your code snippet

Click the "CODE" tab at the top of the google rich results test interface. Paste your complete JSON-LD markup including the script tags into the text field. The tool accepts your entire schema block or just the JSON object itself.

Enter your code snippet

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Avatar Website Design",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Your City",
    "addressRegion": "State"
  },
  "telephone": "+1-555-555-5555"
}
</script>

Click "TEST CODE" and wait for results. The tool processes your markup the same way it handles URL tests, showing detected types with validation status. This approach helps you catch syntax errors before deployment and verify that your schema structure matches Google’s requirements.

Testing code snippets gives you immediate feedback without making changes to your live website.

Fix errors and recheck eligibility

When the google rich results test identifies problems with your structured data, you need to address them before your pages qualify for enhanced search results. Red error messages block rich results entirely, while yellow warnings indicate missing recommended properties that could improve your display. Start with critical errors first, then tackle warnings to maximize your chances of appearing with rich features.

Common errors and their fixes

Missing required properties trigger the most frequent errors. Check that your schema type includes all mandatory fields like name, image, and datePublished for articles, or offers and aggregateRating for products. Syntax errors from missing commas, unclosed brackets, or incorrect quote marks also cause failures.

Fix structural problems by validating your JSON through a JSON validator before retesting to catch basic syntax issues.

Property type mismatches happen when you use text where Google expects a URL or number. Review the Schema.org documentation to confirm each property accepts your value format. Here are the most common fixes:

  • Missing required properties: Add all mandatory fields for your schema type
  • Invalid property values: Match the expected data type for each field
  • Syntax errors: Check for missing commas, brackets, or quotes
  • Incorrect nesting: Ensure child objects appear within their parent structure

Retest after making changes

Save your corrected markup and republish your page if you tested with a URL. Wait 60 seconds for your server to update before running another test. Paste your updated URL or code back into the tool and click the test button again to verify your fixes worked.

google rich results test infographic

Wrap up and keep improving

Validating your structured data with the google rich results test gives you direct insight into how Google sees your markup. Testing regularly catches errors before they hurt your search visibility and confirms that your pages stay eligible for enhanced results. Make validation a routine part of your workflow whenever you add or modify schema markup on your site.

Continue checking your structured data after making site updates or adding new content types. Google updates its rich results requirements periodically, so what worked last month might need adjustments today. Your ongoing testing habit ensures your markup stays current with Google’s standards and your pages maintain their eligibility for eye-catching search features.

Need a website that’s built with proper structured data from day one? Avatar Website Design creates SEO-optimized sites for small businesses with clean, validated schema markup already in place.

Scroll to Top