Rich snippets: How to get enhanced listings in Google

Rich snippets: How to get enhanced listings in Google is a question whose answer has changed a great deal in recent years. Rich snippets, officially called rich results, are Google results that show more than a title, address and description: rating stars, price and stock availability, questions with answers, event dates and product images. They appear when a page contains structured data that Google can read and when Google decides they are worth displaying.

The second condition is the one people forget. Correct markup does not guarantee a listing, and some types of rich results have been withdrawn for most sites.

Rich snippets: How to get enhanced listings in Google

Google reads the structured data on a page, usually in JSON-LD format, matches it to the result types it supports and displays it if the page is eligible. Eligibility depends on content quality, compliance with the rules for each type and the type of query.

In short: structured data is your admission ticket, not a guaranteed seat.

What you gain when they appear

• More space on the results page and a result that stands out visually from those around it.
• A higher click-through rate for commercial queries, where price and stars determine the click.
• Information delivered before the click, bringing visitors who know what they will find.
• A clear signal to Google's systems about what the page is: a product, article, event or local business.

The types that still work in 2026

The list of supported types is shortened periodically. Some of the most widely used have been restricted or removed, and a site implementing them today is wasting its effort.

Active types for most sites

• Product: price, availability and ratings for product pages. This is the most valuable type for shops.
• Article: for articles and news, with author, publication date and image. It contributes to appearances in Discover and news carousels.
• LocalBusiness and Organization: address, opening hours, phone number and legal identifiers. They support the knowledge panel and local results.
• Event: dates, location and tickets for events.
• Recipe: recipes with cooking time, calories and ratings.
• BreadcrumbList: the path within the site, displayed instead of the raw address.
• Review snippet: stars for reviews of products, books, films and courses, but not for your own services.
• VideoObject: for pages with embedded video.

Withdrawn or restricted types

FAQ results, with questions and answers displayed beneath the result, now appear only for highly authoritative government and health sites. HowTo results have been removed entirely. FAQPage markup remains valid and useful for AI systems, but has no longer produced enhanced listings since 2023.

The updated list, with the rules for each type, is the only reliable source; blog guides fall behind. The guide to implementing structured data goes into the details of each type.

How to implement structured data

Google accepts three formats: JSON-LD, Microdata and RDFa. Both the official and practical recommendation is JSON-LD: a script block on the page, separate from the visible HTML, easy to generate and check.

Step 1: choose the right type for the page

The type describes what the page is, not what you would like Google to display. A service page is Service or LocalBusiness, not Product. A blog article is Article, not FAQPage, even if it has questions at the end. Markup that does not match the visible content violates the rules and can trigger a manual action.

Step 2: write the JSON-LD block

A minimal example for a product page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Miere de salcâm 500 g",
  "image": "https://exemplu.ro/imagini/miere-salcam.webp",
  "description": "Miere de salcâm din Alba, recolta 2026.",
  "sku": "MS-500",
  "brand": {"@type": "Brand", "name": "ApisAlba"},
  "offers": {
    "@type": "Offer",
    "price": "32.00",
    "priceCurrency": "RON",
    "availability": "https://schema.org/InStock",
    "url": "https://exemplu.ro/produs/miere-salcam-500g/"
  }
}
</script>

Every value must match what the visitor sees on the page: the same price, the same availability and the same name. A price in the markup that differs from the displayed price is the most common reason for losing an enhanced listing.

Step 3: put the block on the page

The block goes in <head> or at the end of <body>. On WordPress, themes and SEO plugins generate some markup automatically; check what is already there before adding anything, so you do not end up with two Product blocks on the same page with different values.

On sites with a hash-based content security policy, a new JSON-LD block is allowed because it is not an executable script, but check the browser console for errors after adding it.

Step 4: validate

Two tools, with different roles:

• Google's Rich Results Test shows whether the page is eligible for supported types and which fields are missing.
• The schema.org validator checks syntax and vocabulary, including types that Google does not display.

For a check that combines both perspectives and adds Google's rules for each type, you can use the structured data validator on goai.ro, which also suggests corrected code.

Step 5: monitor in Search Console

After indexing, Search Console shows, in the enhancements section, how many pages are valid for each type, how many have errors and how many have warnings. The performance report lets you filter impressions by rich result type, so you can see exactly how many clicks they bring. The guide to Google Search Console shows where these reports are.

Why Google does not display the rich result

Valid markup, but still no stars or price in the results. The usual causes, in order of frequency:

• The page has not been reindexed since the markup was added. Request indexing in Search Console and wait a few days.
• The values in the markup do not match the page. Google checks and, if there is a mismatch, ignores the markup.
• The type is not displayed for that query. Stars appear for product searches, not informational searches.
• The reviews are written by the site about its own services. Google calls this a self-serving review and does not display it; the rule is described in the guide to E-E-A-T and ranking.
• The site has a manual action for misleading structured data. This is visible in Search Console.
• Google has simply decided not to display it. Display is at its discretion, and the proportion of eligible pages that actually receive a rich result varies from week to week.

Rules that prevent penalties

• Mark up only content visible on the page. Recipe markup on a page without a recipe is misleading.
• Do not put aggregate ratings on your own services, your home page or your company page.
• Do not copy markup for the same entity onto dozens of pages; Organization is added once, on the home or about page, and referenced elsewhere using its identifier.
• Keep the markup synchronised with the page whenever a price, stock level or date changes.
• Do not hide text solely to support the markup.

What changes with AI-generated results

Structured data has gained a new role: AI Overviews and Google's AI Mode read a page more easily when entities are explicitly declared, with author, organisation, product and price. Even if a classic rich result no longer appears for a type, markup helps systems understand the page and cite it in generated answers.

The guide to adapting content for AI Overviews shows which markup matters there and how it works with the text's structure.

An example with figures

A flower shop in GOAI's portfolio had product pages without Product markup. After adding JSON-LD with price, stock and ratings from genuine customer reviews, product rich results appeared in Search Console after two weeks, and the click-through rate for queries containing product names rose from 2,1% to 3,4% the following month, with the same number of impressions.

No rankings changed. All that changed was how much space and information the result had on the Google page.

How to check what your site already has

Before adding markup, find out what is there. On WordPress, SEO plugins, themes and review plugins each add a block, and the result is often a mixture: two Organization nodes with different names, a Product without a price and a WebPage with an empty description.

1. Open the page, view its source and search for ld+json. Count the blocks.
2. Run the Rich Results Test on the page's address and read the list of detected items, not just the verdict.
3. Check the enhancements section in Search Console to see whether the type you want already appears with errors; old errors block display even if you add new, correct markup.
4. Disable structured data output from overlapping plugins, keeping a single source for each type.

Only after cleaning up does new markup make sense. A site with contradictory markup will not receive rich results, however good the last block added is.

The recommended order for a service site

• Organization, once, with the legal name, address, phone number and identifiers, referenced from every page.
• WebSite and WebPage on every page, with BreadcrumbList.
• Article on every article, with an author linked to an author page and publication and update dates.
• Service or LocalBusiness on service pages, without self-ratings.
• FAQPage where the page really has visible questions and answers, for AI systems, not for a rich result.

Key takeaway

Rich results come from correct JSON-LD structured data, synchronised with the page, validated and monitored in Search Console, for types that Google still displays. They are not guaranteed and do not replace good content. The official starting point is Google's introduction to structured data, and the list of supported types, with the rules for each, is the rich results gallery.

If you want to know what markup your site has now and what is missing, a structured data check is included in GOAI's free SEO audit , while site-wide implementation is part of technical SEO services and SEO optimisation.

Source references

• Google Search Central, introducere în datele structurate
• Google Search Central, galeria de rezultate îmbogățite