🎧 Prefer to listen?
You’ve written a great blog post. You’ve done the keyword research, optimized your headings, added internal links. But when you Google your topic, your result looks like every other bland blue link on the page. Meanwhile, your competitor’s result shows star ratings, an FAQ dropdown, and a thumbnail image. They’re getting the clicks. You’re not.
The difference isn’t content quality — it’s structured data. And Google gives you a free tool to check exactly what yours looks like: the Rich Results Test.
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” — those enhanced search listings with images, ratings, dropdowns, and other visual elements that make people click.
If you’re running a blog built with Hugo, WordPress, or any modern CMS, you probably already have some structured data. 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 what rich results your page is eligible for.
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. For example, if your Article schema is missing image or author, Google will flag it. These are worth fixing.
3. Errors — These mean your structured data is invalid and Google can’t process it. Common causes: missing required fields, incorrect data types, or malformed JSON-LD. Fix these immediately — they prevent rich results entirely.
4. Detected items that aren’t eligible — Sometimes Google finds structured data that doesn’t qualify for rich results. This usually means the schema type exists but Google doesn’t currently enhance it in search.
The schemas every blog needs
If you’re a solo builder running a blog, these are the structured data types you should have:
Article / BlogPosting — Every blog post should have this. It tells Google the title, author, publish date, modified date, and featured image. Most Hugo themes (like PaperMod) generate this automatically from your frontmatter. Check that your date, title, and cover.image fields are correct — the Rich Results Test will flag if they’re missing.
FAQPage — If your post has a Q&A section, add FAQ schema. This produces dropdown rich results in search, which can double your click-through rate. We covered this in our start here guide — it’s one of the easiest SEO wins for beginners.
BreadcrumbList — Shows your site’s navigation structure in search results (e.g., Home > Tools > SEO). This helps Google understand your site hierarchy and makes your results look more professional.
Organization / Person — Your site-wide schema that identifies who you are. This feeds into Google’s Knowledge Panel and helps establish authority.
Common mistakes the test catches
I’ve run the Rich Results Test on dozens of sites, and these errors come up constantly:
Missing image in Article schema — Your post has a cover image, but your structured data doesn’t reference it. Google can’t show a thumbnail in search without this. Fix: make sure your frontmatter cover.image points to a real, accessible image URL.
Incorrect date format — Schema requires ISO 8601 dates (2026-07-04T08:00:00Z). If your CMS outputs dates in a different format, Google flags it. Most modern CMSs handle this, but check if you’re using custom templates.
Duplicate schema types — Some themes generate both Article and BlogPosting for the same page. This confuses Google. Pick one and remove the other.
Missing author information — Google increasingly wants to know who wrote your content. If your Article schema doesn’t include an author with a name and URL, you’re missing a trust signal. This matters even more since Google’s E-E-A-T updates.
FAQ schema without matching content — Don’t add FAQ schema for questions that don’t actually appear on the page. Google checks for this and may penalize your site.
Beyond the test: what to do with the results
The Rich Results Test shows you what’s wrong. Here’s how to fix it:
If you’re on Hugo — Your theme likely handles most schema generation. Check your layouts/partials/schema.html or similar template. We use custom schema templates that include Article, FAQPage, and BreadcrumbList on every post. If your theme doesn’t have these, you can add them to your layouts/_default/single.html.
If you’re on WordPress — Install a schema plugin like Rank Math or Yoast. Both generate the essential schemas automatically. The free tiers handle Article and FAQ schema; the paid versions add more types.
If you’re on any platform — You can add JSON-LD structured data manually. This is a script tag you put in your page’s <head> section. The Schema.org documentation lists every available type and property. For beginners, start with Article and FAQPage — they have the highest impact for the least effort.
The bigger picture: structured data in 2026
Structured data isn’t just about rich results anymore. With AI search engines like Perplexity, Google’s AI Overviews, and ChatGPT Search increasingly pulling from web content, structured data helps these systems understand and cite your content correctly.
If you’ve been following the rise of AI agents and how they interact with web pages, structured data is how those agents identify what your content is about. A well-structured page with proper schema is more likely to be cited, summarized, and referenced by AI systems.
We’ve been building this into our site from the start — our AI Tool Advisor uses structured data to help AI systems understand tool comparisons. It’s not just SEO anymore; it’s making your content machine-readable.
What to do right now
- Go to search.google.com/test/rich-results
- Test your homepage and your top 5 blog posts
- Fix any errors (red) immediately
- Address warnings (yellow) within a week
- Re-test after fixes to confirm everything is green
- Check Google Search Console’s “Enhancements” section weekly to monitor rich result performance
This takes 30 minutes and costs nothing. The payoff — better click-through rates, more visibility in AI search, and a more professional presence in search results — is immediate and compounding.
If you’re already using tools like Make.com to automate your workflow, you can even set up a monthly automation that tests your top pages and alerts you when structured data breaks. That’s the kind of AI automation that actually saves time.
And if you’re still figuring out which AI tools to use for your content workflow, our guide on AI productivity tools that actually work breaks down the stack worth paying for.