---
title: "Rich Results in Vue"
description: "Google removed FAQ and HowTo snippets and cut more types in 2026. See which Schema.org types still earn rich results and how to add them in Vue."
canonical_url: "https://nuxtseo.com/learn-seo/vue/mastering-meta/rich-results"
last_updated: "2026-07-16"
---

<key-takeaways>

- Vue SPAs must server-render structured data for rich result eligibility; client-only rendering is unreliable
- Google removed FAQ and HowTo rich results for most sites in 2023, and cut several niche types further in January 2026
- Product, Recipe, Article, and Event types still show rich results and can lift click-through rate
- Test with Rich Results Test before deploying: valid markup doesn't guarantee a display

</key-takeaways>

Rich results are enhanced search listings that show more than a blue link: star ratings, prices, cook times, event dates. Google displays them when a page has valid [Schema.org structured data](https://schema.org/), but not every type survived. Google removed [FAQ and HowTo rich results](https://developers.google.com/search/blog/2023/08/howto-faq-changes) for most sites in 2023.

For Vue SPAs specifically, structured data must be server-side rendered to be eligible. Client-only rendered JSON-LD isn't reliably picked up by crawlers, which makes SSR or prerendering essential if you're targeting rich results.

## What Changed

**August 8, 2023**: FAQ rich results became limited to well-known government and health sites, and every other site lost them. HowTo rich results dropped from mobile search the same day.

**September 13, 2023**: HowTo rich results dropped from desktop too, ending the feature everywhere.

<warning>

FAQ rich results remain limited to authoritative government and health sites. Adding FAQ schema to a regular business or blog site has no visible effect in search results.

</warning>

Google said the changes give search "a cleaner and more consistent search experience." Sites that relied on FAQ or HowTo markup saw click-through rate drop, with no way to get those snippets back.

Google trimmed further in January 2026, deprecating [Practice Problems, Nutrition Facts, Nearby Offers, and Local Bikeshare Station Status](https://searchengineland.com/google-to-remove-more-search-features-including-practice-problems-nutrition-facts-nearby-offers-and-more-464255): niche structured data types that no longer trigger rich results, as part of an ongoing effort to simplify the results page.

## Rich Results That Still Work

<table>
<thead>
  <tr>
    <th>
      Type
    </th>
    
    <th>
      Shows
    </th>
    
    <th>
      Example
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/article" rel="nofollow">
        Article
      </a>
    </td>
    
    <td>
      Headline, image, date
    </td>
    
    <td>
      News, blog posts
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/breadcrumb" rel="nofollow">
        Breadcrumb
      </a>
    </td>
    
    <td>
      Navigation path
    </td>
    
    <td>
      Home > Category > Page
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/event" rel="nofollow">
        Event
      </a>
    </td>
    
    <td>
      Date, location, ticket info
    </td>
    
    <td>
      Concerts, conferences
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/local-business" rel="nofollow">
        LocalBusiness
      </a>
    </td>
    
    <td>
      Hours, location, reviews
    </td>
    
    <td>
      Stores, restaurants
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/product" rel="nofollow">
        Product
      </a>
    </td>
    
    <td>
      Price, availability, reviews
    </td>
    
    <td>
      E-commerce
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/recipe" rel="nofollow">
        Recipe
      </a>
    </td>
    
    <td>
      Cook time, calories, ratings
    </td>
    
    <td>
      Food sites
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/review-snippet" rel="nofollow">
        Review
      </a>
    </td>
    
    <td>
      Star rating
    </td>
    
    <td>
      Product/service reviews
    </td>
  </tr>
  
  <tr>
    <td>
      <a href="https://developers.google.com/search/docs/appearance/structured-data/video" rel="nofollow">
        Video
      </a>
    </td>
    
    <td>
      Thumbnail, duration, upload date
    </td>
    
    <td>
      <a href="https://youtube.com" rel="nofollow">
        YouTube
      </a>
      
      , Vimeo embeds
    </td>
  </tr>
</tbody>
</table>

[See the full list in Google's Search Gallery](https://developers.google.com/search/docs/appearance/structured-data/search-gallery).

Product, Recipe, and Event rich results drive measurable clicks. Rotten Tomatoes added structured data to 100,000 pages and measured a [25% higher click-through rate](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) versus pages without it.

## Testing Your Markup

![Rich Results Testing Workflow](/images/learn-seo/vue/rich-results-workflow.svg)

Use [Rich Results Test](https://search.google.com/test/rich-results) to validate structured data. Enter your URL or paste HTML directly. The tool shows which rich results are eligible and flags errors.

Two validation tools exist, and they do different jobs:

1. **Rich Results Test**: tests Google-specific eligibility. Use this to see if your markup qualifies for rich results in search.
2. **Schema Markup Validator**: tests schema.org syntax compliance. Use the [validator](https://validator.schema.org/) for types that don't qualify for rich results but you want on the page anyway, like Organization or WebSite.

## Monitoring in Search Console

[Google Search Console](/learn-seo/vue/launch-and-listen/search-console) shows a separate report for each rich result type found on your site:

1. Open Search Console
2. Go to **Enhancements** in the sidebar
3. Click the rich result type (Product, Recipe, Article, etc.)

Each report shows valid items that can display as rich results, and invalid items with errors blocking display. Fix errors immediately: they block rich results entirely. Address warnings when possible: they can reduce effectiveness even when the result still shows.

The reports only show a sample of detected items, not every instance, and Google drops reporting for types that no longer appear in search. [Search Console removed reporting](https://searchengineland.com/google-drops-reporting-on-several-structured-data-types-461744) for Course Info, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing, and Claim Review in September 2025.

## Should You Remove FAQ/HowTo Markup?

No, keep it. Google says structured data that's not used "does not cause problems for Search, but also has no visible effects." The visible rich result is gone for most sites, but the basic data still helps: LLMs read Schema.org markup as structured data rather than parsing raw text, which raises the odds of correct citation in AI answers.

If you're adding new markup, skip FAQ and HowTo unless you run a government or health site. Focus on Product, Recipe, Article, and Event types instead: they still work.

## Common Rich Result Mistakes

**Missing required fields**: each rich result type has required properties. Product needs `name`, `image`, `offers`. Recipe needs `name`, `image`, `totalTime`. Check Google's docs for each type.

**Invalid image URLs**: images must be absolute HTTPS URLs, not relative paths. Size requirements vary by type, so check each one; Article, for example, needs high-resolution images totaling at least 50,000 pixels (width × height).

**Blocking images in robots.txt**: Google must be able to crawl your images. Check that your robots.txt doesn't block `/images/` or similar paths.

**No visible content**: the structured data must match visible content on the page. Markup for a recipe that isn't on the page violates [Google's spam policies](https://developers.google.com/search/docs/appearance/structured-data/sd-policies).

**Syntax errors**: invalid JSON-LD breaks all structured data on the page. Validate with the Schema Markup Validator before deploying.

**Client-injected JSON-LD**: a script tag added via `useHead()` after hydration isn't reliably picked up by crawlers. Ship it in the initial server response instead; see the [Schema.org guide](/learn-seo/vue/mastering-meta/schema-org) for setup and code examples per type.

## Rich Results Aren't Guaranteed

Valid markup doesn't guarantee rich results will show. Google decides based on:

- Search query relevance
- User intent
- Competition for that result type
- Page authority

You can have perfect structured data and still not see a rich result. Add markup for the user benefit, better-organized data, not purely for search appearance.

## Checklist

<checklist id="vue-rich-results">

- Structured data is server-rendered, not injected client-side after hydration
- Schema.org markup validates in Rich Results Test with zero errors
- Product, Recipe, Event, Article, or Review markup added where content supports it
- FAQ and HowTo markup only added on government or health sites (they won't show elsewhere)
- Structured data matches the visible content on the page
- Search Console Enhancements reports checked for invalid items

</checklist>

Nuxt SEO handles Schema.org [automatically](/docs/schema-org/getting-started/introduction) with zero config: [Rich Results in Nuxt](/learn-seo/nuxt/mastering-meta/rich-results)