Google Rich Results Test: Free SEO Tool for Your Blog, No Code

You’ve written a great blog post. You did the keyword research, fixed your headings, added internal links. Then you Google your topic and find your result sitting there as a plain blue link — while your competitor’s listing shows star ratings, an FAQ dropdown, and a thumbnail image. They get the click. You get scrolled past.

That difference usually isn’t content quality. It’s structured data, and most blogs either have broken schema or none at all. Google gives you a free tool to check yours: the Rich Results Test. In this post I’ll walk through how to run it, how to read what it tells you, and how to fix the problems it finds — in about fifteen minutes, for free.

What structured data actually does

Structured data is code you add to your website that tells Google what your content is, not just what it says. A recipe isn’t just text about cooking — it’s a recipe with ingredients, cook time, and nutritional info. A blog post isn’t just words — it’s an article with an author, publish date, and FAQ section.

When Google understands this, it can display your content as rich results: enhanced listings with images, ratings, dropdowns, and other elements that earn clicks. The payoff isn’t theoretical. In one of the most-cited case studies, Rotten Tomatoes saw an 82% higher click-through rate on pages with structured data compared to pages without it. Your mileage will vary, but the direction is consistent — listings with extra visual elements get more attention on a crowded results page.

If your blog runs on Hugo, WordPress, or most modern CMSs, you probably already have some structured data, usually from your SEO plugin or theme. The question is whether it’s correct, complete, and actually producing rich results. That’s what the Rich Results Test tells you.

How to use the Rich Results Test

Go to search.google.com/test/rich-results and paste your URL. Google will crawl the page and show you exactly what structured data it finds, whether it’s valid, and which rich results your page qualifies for. You can also paste a code snippet directly if you want to test markup before publishing it — handy when you’re editing a template.

Here’s what to look for:

1. Valid items detected — These are the structured data types Google found and can process. Common ones for blogs include Article, BlogPosting, FAQPage, and BreadcrumbList. If you see these in green, you’re good.

2. Warnings — These aren’t errors, but they mean you’re missing optional fields that could improve your rich results. If your Article schema is missing image or author, Google will flag it. Fix these; they’re cheap wins.

3. Errors — Your structured data is invalid and Google can’t process it. Common causes: missing required fields, wrong data types, or malformed JSON-LD. Fix these immediately, because they block rich results entirely.

4. Detected items that aren’t eligible — Sometimes Google finds valid markup for a feature your page can’t actually show, like Review schema on a page with no review content. Google tightened these rules in 2019 and again in 2023, restricting review stars to specific content types, so an ineligible item often means your theme is adding schema you don’t need. Remove it rather than ignore it.

Rich Results Test vs. Schema Markup Validator

Here’s the part most posts skip, and it trips people up constantly. Google deprecated most of the old Structured Data Testing Tool in 2021, and if you go looking for a replacement you’ll find two different tools that do two different jobs.

The Rich Results Test only checks markup that qualifies for Google’s rich result features — roughly 17 types, including Article, FAQ, HowTo, Product, and Breadcrumb. If your schema is valid but doesn’t map to a rich result Google displays, the tool will show it as “not eligible” and tell you little else.

The Schema Markup Validator checks your markup against the full schema.org vocabulary instead. Use it when you’re working with schema types the Rich Results Test ignores, like Person, Organization, or WebSite. My workflow: validate against schema.org first to catch structural mistakes, then run the Rich Results Test to confirm Google will actually do something with it.

One more quirk worth knowing: the Rich Results Test renders your page with Googlebot smartphone, so it sees your mobile version. If your mobile theme outputs different structured data than desktop — some WordPress themes do — you’re testing the mobile markup whether you realize it or not. Check your site on a phone if the results surprise you.

Fixing the issues it finds

Most fixes fall into a few buckets, and none require a developer if you’re on WordPress.

Missing fields are the easiest. Yoast SEO and Rank Math both let you fill in author, image, and date information from the post editor. If your theme outputs broken JSON-LD — malformed brackets, wrong data types — you can usually disable the theme’s schema and let your SEO plugin handle everything, which avoids running two conflicting sets of markup.

For FAQ schema, I add it manually with a small JSON-LD block in the post, then paste the code into the Rich Results Test’s code tab before publishing. It takes two minutes and catches typos before Google does.

After every fix, re-run the test. Changes to schema don’t show up in search results immediately; Google has to recrawl the page, which can take days. Don’t panic if the live URL still shows old results an hour after you fixed them. Use the “Test live URL” option rather than the cached code view to confirm what Google sees right now.

Run the test monthly on your top ten posts. Schema breaks quietly — a plugin update, a theme change, a migration — and you won’t notice until your FAQ dropdowns vanish from search. Fifteen minutes a month keeps that from happening.