Schema Markup Guide: How to Get Rich Results in Google

Schema Markup Guide: How to Get Rich Results in Google

Schema markup (also called structured data) is code you add to your website that helps search engines understand your content in a structured, machine-readable format. When Google understands what your page contains — a recipe, a product, an FAQ, a how-to guide — it can display enhanced results called "rich results" that stand out in search with extra visual elements like star ratings, images, FAQ dropdowns, and more.

Rich results get higher click-through rates than standard blue links. Pages with FAQ rich results, for example, take up more visual space in search results and can double or triple their CTR. This guide covers the schema types that matter most, how to implement them, and how to test your markup.

What Is Schema Markup?

Schema markup is based on Schema.org, a collaborative vocabulary created by Google, Microsoft, Yahoo, and Yandex. It defines hundreds of content types and properties that describe what a page is about in terms a machine can parse. When you add schema markup to a recipe page, for instance, you are telling Google: "This is a recipe. The name is X, the cooking time is Y, the ingredients are Z."

Without schema markup, Google has to guess this information by analyzing your page content. With schema markup, you provide it explicitly and accurately.

JSON-LD: The Recommended Format

Google recommends JSON-LD (JavaScript Object Notation for Linked Data) as the preferred format for structured data. JSON-LD is a script tag that contains a JSON object describing your content. It is separate from your HTML, easy to read and maintain, and can be injected dynamically with JavaScript.

The alternative formats are Microdata (HTML attributes) and RDFa (HTML attributes). These mix structured data with your HTML content, making pages harder to maintain. Google accepts all three formats but recommends JSON-LD for new implementations.

A basic JSON-LD script tag looks like this: <script type="application/ld+json">{ "@context": "https://schema.org", "@type": "Article", "name": "Your Article Title" }</script>. Place this in your page's head or body — Google finds it either way.

Major Schema Types for Websites

FAQPage Schema

FAQPage schema displays your frequently asked questions directly in search results as expandable dropdowns. This takes up significantly more space than a standard result, pushing competitors further down the page and increasing your CTR.

Use FAQPage when your page contains a list of questions with answers. Each question becomes a potential rich result entry. Ensure your FAQ content is visible on the page — Google may not display rich results for hidden or collapsible content that is not accessible without user interaction.

HowTo Schema

HowTo schema marks up step-by-step instructions. Google can display these as rich results with step images, total time, and estimated cost. This is ideal for tutorials, recipes, DIY guides, and any content that walks users through a process.

Each step should have a clear name, descriptive text, and optionally an image. The more complete your markup, the richer the potential result.

Article Schema

Article schema (including NewsArticle and BlogPosting) tells Google that your page is an article. It can include the author, date published, date modified, publisher, and headline. This helps Google display articles properly in search results, Google News, and Discover.

WebApplication Schema

WebApplication schema describes a web-based tool or application. This is particularly relevant for tool pages — it tells Google the page is a functional application rather than just informational content. Include the application name, description, operating system (Web), and application category.

Organization Schema

Organization schema identifies your business or website as an entity. Include your name, URL, logo, social media profiles, and contact information. This helps Google display your brand correctly in knowledge panels and other enhanced results.

BreadcrumbList Schema

BreadcrumbList schema provides Google with your page's navigation hierarchy. Instead of showing the raw URL in search results, Google displays a breadcrumb trail like "Home > Tools > SEO Tools > Meta Title Generator" — which is more readable and clickable.

Product Schema

Product schema is essential for e-commerce pages. It enables rich results with product images, prices, availability, and star ratings. If you sell products, this schema type has the most direct impact on CTR from search results.

How to Implement Schema Markup

Manual Implementation

Write JSON-LD directly in your page templates. For Next.js sites, create a reusable component that accepts schema data as props and renders the script tag. This approach gives you full control and works well for consistent page types.

Using a CMS or Framework Plugin

Many CMS platforms and frameworks have plugins or built-in support for schema markup. WordPress plugins like Yoast SEO automatically generate basic schema. Next.js apps can generate schema dynamically in server components based on page data.

Google Tag Manager

For sites where modifying code is difficult, Google Tag Manager can inject JSON-LD script tags into pages. This is less ideal for performance but provides a no-code implementation path.

Testing Your Schema Markup

Rich Results Test

Google's Rich Results Test (search.google.com/test/rich-results) is the primary tool for validating structured data. Enter a URL or paste code to see which rich results your markup qualifies for and identify any errors or warnings.

Schema Markup Validator

The Schema Markup Validator (validator.schema.org) checks your markup against the full Schema.org vocabulary. It is more comprehensive than the Rich Results Test and catches issues that Google's tool might not flag.

Google Search Console

The Enhancements section in Google Search Console shows schema-related errors, warnings, and valid items across your entire site. Check this regularly to catch issues that arise from template changes or content updates.

Common Schema Mistakes

• Markup that does not match visible content: Google requires that the information in your schema matches what users see on the page. Do not add Organization schema to every page — only the homepage or about page.
• Duplicate schema: Having both JSON-LD and Microdata for the same content can confuse parsers. Pick one format and use it consistently.
• Invalid property values: Using incorrect types or formats for properties (e.g., a string where a number is expected) causes errors.
• Over-marking: Not every page needs every schema type. Use schema that is relevant to the actual content on the page.
• Missing required properties: Each schema type has required properties. Omitting them causes Google to ignore the markup entirely.

Explore Schema Types

Use our free schema markup type guide to discover the right schema types for your pages. Browse by content type, see example JSON-LD code for each, and get implementation guidance tailored to your platform. No signup required.