Index of every page on this site: llms.txt

Rich Results in Vue

Check current Google rich result types for Vue. Understand FAQ retirement, JSON-LD testing, and why valid markup does not guarantee display.
Harlan Wilton10 mins read Published Updated
What you'll learn
  • Render structured data in initial HTML when practical. Google also supports JavaScript-generated structured data
  • Google ended FAQ rich results in May 2026. HowTo rich results ended in 2023
  • Product, Recipe, Article, and Event remain supported types. Valid markup creates eligibility, not a display guarantee
  • Test with Rich Results Test before deploying: valid markup doesn't guarantee a display

Rich results can add information such as ratings, prices, dates, or images to search listings. Google supports selected structured data types. FAQ rich results ended in May 2026. HowTo rich results ended in September 2023.

Google supports JavaScript-generated structured data. SSR or prerendering makes the markup available in the initial response. Test the public URL to confirm Google can access the markup.

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.

Google ended FAQ rich results on May 7, 2026. The former government and health exception no longer applies.

Check the current Search Gallery when choosing a feature. Google can retire features after an article is published.

Rich Results That Still Work

TypeShowsExample
ArticleHeadline, image, dateNews, blog posts
BreadcrumbNavigation pathHome > Category > Page
EventDate, location, ticket infoConcerts, conferences
LocalBusinessHours, location, reviewsStores, restaurants
ProductPrice, availability, reviewsE-commerce
RecipeCook time, calories, ratingsFood sites
ReviewStar ratingReviews of eligible item types
VideoThumbnail, duration, upload dateYouTube, Vimeo embeds

See the full list in Google's Search Gallery.

In one Google case study, Rotten Tomatoes added structured data to 100,000 pages and measured a 25% higher click-through rate versus pages without it.

Testing Your Markup

Use Rich Results Test 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 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 provides reports for supported rich result types it detects:

  1. Open Search Console
  2. Go to Enhancements in the sidebar
  3. Open an available rich result report, such as Product or Recipe

Each report shows valid items that can display as rich results, and invalid items with errors blocking display. Fix errors on affected invalid items. Other valid items can remain eligible. Address warnings where practical.

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 for Course Info, Estimated Salary, Learning Video, Special Announcement, Vehicle Listing, and Claim Review in September 2025.

Should You Remove FAQ/HowTo Markup?

Existing accurate FAQ or HowTo markup can remain for other consumers. Google Search no longer provides these rich results. Do not keep the markup solely for an unsupported promise of AI citations.

For Google rich results, choose a currently supported type that matches your visible content. Check the Search Gallery before adding markup.

Common Rich Result Mistakes

Missing required fields: Requirements differ by feature. Check the current Product and Recipe guides, including their alternative properties.

Invalid image URLs: Use public, crawlable image URLs. Requirements vary by type. For example, check the current Article image recommendations.

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.

Syntax errors: invalid JSON-LD can prevent Google from reading the affected block. Validate with the Schema Markup Validator before deploying.

Missing rendered JSON-LD: JavaScript-generated markup must be accessible to Google. Check the rendered page with Rich Results Test. Initial HTML simplifies this check; see the Schema.org guide.

Rich Results Aren't Guaranteed

Valid markup does not guarantee a rich result. Google's policies require accessible pages, accurate markup, and compliance with feature-specific rules. Google chooses a search appearance for the user and query.

Even perfect structured data may produce no rich result. Add markup to organize the data for users, rather than relying on a search appearance.

Reported structured data updates typically took hours to 1 to 2 weeks, with slow cases reaching weeks or never completing because of quality. Validating your deployed markup does not prove Google has processed it or chosen a rich result. See Google Search timelines for the separate checks.

Checklist

Checklist
  • Structured data appears in the HTML Google can access
  • 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 is not expected to produce Google rich results
  • Structured data matches the visible content on the page
  • Search Console Enhancements reports checked for invalid items

Nuxt SEO handles Schema.org automatically with zero config: Rich Results in Nuxt

Was this page helpful?