How to Get Rich Snippets in Google with Schema.org

Rich snippets are search results with additional elements, such as rating stars, product prices, recipe information, or breadcrumbs. Google supports some Schema.org types, and display depends on its rules and the page content. This article covers implementation and validation, as well as the discontinued FAQ and HowTo formats.

What are rich snippets

A rich snippet is a regular search result enhanced with structured data. Google extracts this data from Schema.org markup and displays it as:

• Rating stars — for products, recipes, and locations.
• Product information — price, availability, and other supported attributes.
• Recipes — preparation information, an image, and other supported fields.
• Breadcrumbs — a navigation path below the title.
• Images — for articles, products, and recipes.
• Publication date — for news and articles.

Benefits of rich snippets

Important: Google does not guarantee that rich snippets will appear. Correct markup for a supported type makes a page eligible, but the search engine makes the decision. Check the type in Google's current gallery, rather than checking only whether it exists in Schema.org.

Types of rich snippets

FAQPage: a Schema.org type without Google FAQ rich results

Google stopped showing FAQ rich results in May 7 2026 year, and removed the format's documentation in June 15. This is noted in the official update log. FAQPage remains a Schema.org type for a page with questions and answers, but it does not create an FAQ block in Google search results.

If you need FAQPage as a structured description:

• Use FAQPage markup.
• Questions and answers are visible on the page.
• The content is relevant to the search query.
• There is no spam or manipulation (the questions should be real).

Markup example:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Как оформить заказ?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Добавьте товар в корзину, перейдите к оформлению, заполните данные и выберите способ оплаты."
      }
    }
  ]
}

Check the structure with Schema Validator on reChecker and compare it with the page text. SERP Preview helps assess the title and description; it does not confirm that an FAQ will appear in Google.

HowTo: discontinued rich result format

Google stopped showing HowTo rich results in September 2023 year. The official announcement includes an update about ending desktop display after the mobile format was discontinued. HowTo still describes instructions in Schema.org, but adding it does not create a step-by-step Google snippet. Recipes use the separate supported Recipe type.

Requirements:

• Use HowTo markup.
• Steps are visible on the page in the same order.
• The content is a real step-by-step instruction.
• totalTime and estimatedCost describe the duration and cost of the process; they do not bring back the discontinued Google format.

Markup example:

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "Как настроить роутер",
  "totalTime": "PT15M",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Подключите кабель",
      "text": "Подключите Ethernet-кабель от провайдера в порт WAN.",
      "position": 1
    },
    {
      "@type": "HowToStep",
      "name": "Войдите в панель",
      "text": "Откройте браузер и перейдите по адресу 192.168.1.1.",
      "position": 2
    }
  ]
}

Product with a rating

A Product snippet with stars can appear for products with reviews and ratings.

Requirements:

• Use Product markup.
• Include aggregateRating with ratingValue, reviewCount, and bestRating.
• The rating on the page must match the markup.
• Include at least several genuine reviews.

Markup example:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Ноутбук ProBook 15",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "89",
    "bestRating": "5",
    "worstRating": "1"
  },
  "offers": {
    "@type": "Offer",
    "price": "64990",
    "priceCurrency": "RUB",
    "availability": "https://schema.org/InStock"
  }
}

BreadcrumbList

Breadcrumbs appear below the title as a path: Home > Category > Subcategory > Page.

Requirements:

• Use BreadcrumbList markup.
• Match the breadcrumbs visible on the page.
• Use a correct hierarchy and URLs.

Markup example:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Главная", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Каталог", "item": "https://example.com/catalog" },
    { "@type": "ListItem", "position": 3, "name": "Текущая страница" }
  ]
}

Article and NewsArticle

For articles and news, Google may show the publication date, an image, and the publisher's name.

Requirements:

• Use Article or NewsArticle.
• Include datePublished and dateModified.
• Include author and publisher with a logo.
• Include an image.

Markup example:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Заголовок статьи",
  "datePublished": "2026-03-07",
  "dateModified": "2026-03-07",
  "author": { "@type": "Person", "name": "Автор" },
  "publisher": {
    "@type": "Organization",
    "name": "Сайт",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  },
  "image": "https://example.com/article.jpg"
}

Step-by-step implementation plan

Step 1: Choose a markup type

Determine which type is appropriate for the page:

Step 2: Create the markup

Use JSON-LD examples. Make sure all required fields are filled in and the data matches the page content.

Step 3: Add it to the page

Place the JSON-LD in <head> or at the beginning of <body>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [...]
}
</script>

Step 4: Validate it

Check the markup with Schema Validator on reChecker. Fix all errors and critical warnings.

Step 5: Check how it appears in search

Use SERP Preview on reChecker to review the title and description wording. Check markup supported by Google with Rich Results Test. FAQPage and HowTo no longer produce the corresponding Google rich results; you can validate their structure with the Schema.org validator.

Step 6: Wait for indexing

Reindexing takes from several days to several weeks. Request reindexing in Google Search Console.

Common errors that prevent rich snippets from appearing

1. Content does not match the markup

The rating on the page must match the markup. Questions and answers must be visible. Do not add markup for content that is not on the page.

2. JSON syntax errors

Extra commas, unescaped quotation marks, or invalid JSON cause the markup to be ignored. Check it with a validator.

3. Manipulative markup

Fabricated reviews, ratings for nonexistent products, or FAQs made up of keywords carry a risk of penalties. Use only genuine data.

4. Duplicated types

Multiple conflicting FAQ or Product blocks on one page. Combine them into one or keep one relevant block.

5. Outdated formats

Google periodically updates its requirements. Follow Google's documentation and update your markup.

Google's content quality requirements for rich snippets

Even valid markup does not guarantee that rich snippets will appear. Google evaluates content quality.

Relevance

The page should fully answer the user's query, and the markup should describe its content. One question is acceptable for FAQPage if it belongs to the visible FAQ; the number of questions does not bring back FAQ rich results. HowTo should describe a real step-by-step instruction.

Uniqueness

Duplicate or copied content with markup rarely gets rich snippets. Original, useful content is prioritized.

Timeliness

For articles and news, use current dates. Outdated content with a date from two years ago may not appear with a date in the snippet.

Compliance with the rules

Google does not show rich snippets for content that violates its policies (adult content, dangerous advice, deception, etc.). Manipulative markup carries a risk of penalties.

Competition

The number of rich snippets shown in search results is limited. If competitors are stronger in relevance and authority, your markup may not appear. Work on improving your content and backlink profile.

Combining types

You can use multiple Schema.org types on one page. This describes the content, while the availability of Google rich results is checked separately for each type:

• Article: Article + BreadcrumbList.
• Product page: Product + BreadcrumbList + FAQ (if there is an FAQ).
• Instructions: HowTo + BreadcrumbList.
• Service page: Service + FAQ + BreadcrumbList.

Place each type in a separate <script type="application/ld+json"> block. Avoid conflicts (for example, two different Product types for the same product).

Monitoring rich snippets

Google Search Console

The “Enhancements” → “Structured data” section shows:

• The number of pages with markup.
• Errors and warnings.
• The types of data detected.

Fix errors first. Address warnings where possible.

Manual checks

Periodically enter key queries in Google and check whether rich snippets appear for your pages. Keep in mind that Google may show different versions to different users.

Tools

Frequently asked questions

Does markup guarantee that rich snippets will appear?

No. Markup makes a page eligible. Google decides whether to show a rich snippet based on relevance, content quality, and other factors.

How long does it take for rich snippets to appear?

After implementation and reindexing, it takes from several days to several weeks. It takes longer for new pages.

Can I use multiple types on one page?

Yes. Article + BreadcrumbList and Product + FAQPage are possible Schema.org combinations if they match the page. Each Google-supported format is checked separately: having FAQPage does not add an FAQ rich result.

What should I do if rich snippets disappear?

Check whether Google currently supports the format, then check for markup errors and whether the markup matches the page content. FAQ and HowTo rich results have been discontinued; fixing the JSON-LD will not bring them back. For current formats, use the latest documentation and Search Console reports.

Do rich snippets work in Yandex?

Yandex supports some types (breadcrumbs, organizations, products). Check them in the Structured Data Validator.

Do I need to update markup when the content changes?

Yes. If the rating, price, publication date, or FAQ answers change, update the corresponding markup. For Google-supported formats, a mismatch with the page content may prevent rich results from appearing. Updating FAQPage keeps the data accurate but does not bring back FAQ rich results.

Can I use markup for hidden content?

No. Content referenced by the markup (questions, answers, ratings, steps) must be visible to users on the page. Hidden content with markup is manipulative.

Additional types of rich snippets

Besides the types described above, Google supports other types. Here is a brief overview:

Recipe

For recipes with ingredients, cooking time, and calorie information. Requires Recipe markup with the fields recipeIngredient, recipeInstructions, prepTime, and cookTime.

VideoObject

For video content. Can show a preview and duration in search results. Requires VideoObject markup with embedUrl, uploadDate, and duration.

Event

For events such as concerts, webinars, and exhibitions. Fields: name, startDate, location, offers.

LocalBusiness

For local businesses. Address, opening hours, rating, and reviews. May appear in local search results and on maps.

Course

For educational courses. Name, description, provider, and rating.

Check the latest requirements in Google's documentation. Types and requirements are updated periodically.

Conclusion

Start with Google-supported types that match the page content: Product, Recipe, Article, or BreadcrumbList. Create markup based on real data, check it with Rich Results Test, and assess actual display and clicks. FAQPage and HowTo can be used as Schema.org types, but the corresponding Google rich results have been discontinued.

Additional resources:

• JSON-LD examples: Article, Product, FAQ, HowTo, BreadcrumbList
• Schema.org markup: complete guide to structured data