wprichsnippets
Guide · Schema types · Formats and referencesCERT No. ST R002

How to Get Rich Snippets: The Eligibility Steps Google Documents

Schema type
Article BreadcrumbList
Checked against
Google Search Central documentation and Search Central changelog, read November 2026
Author
The wprichsnippets.com editors
Published
Updated
Direct answerField 01

To get rich snippets, choose a result type Google still supports, describe content that is visible on the page with JSON-LD, include every required property, follow the content policies, pass the Rich Results Test and keep the page crawlable and indexed. That makes a page eligible. Google then decides, search by search, whether to show it.

56 wordsUpdated November 18, 2026
FeatureFig. 01
Six stacked trays, each holding one labelled part of a search result, rising from plain text to a full result card
Each step removes one reason Google cannot show the result. None of them forces it to.

01How to get rich snippets: the six steps

A rich snippet is a search result that shows extra information, such as stars, a price, a cooking time or an event date, drawn from structured data on the page. Google's own documentation now calls these rich results. This guide sets out how to get rich snippets in the order Google's documents imply, with the line behind each step.

The eligibility steps and the document behind each one
StepWhat you doWhere Google documents it
1. Choose a featureMatch the page to a result type Google still supportsStructured data markup that Google Search supports
2. Mark up visible contentDescribe what readers can see, in JSON-LDIntroduction to structured data
3. Include required propertiesFill every required property; add recommended ones you can supportEach feature guide, and the general guidelines
4. Follow the policiesNo hidden, misleading or self-serving contentGeneral structured data guidelines
5. TestRich Results Test, then URL InspectionFeature guides, How to add structured data
6. Keep the page indexableNo robots.txt block, no noindex, no login wallGeneral guidelines, Access

The order matters. Testing before you know whether a feature exists wastes time, and passing the test does not help if the page is blocked or the content breaks a policy. Each step below removes one reason Google cannot show the result. None of them obliges Google to show it.

02Step 1: Is there still a rich result for your content?

Start with Google's list of supported structured data features. As of November 2026 it includes Article, Breadcrumb, Carousel, Course list, Dataset, Discussion forum, Education Q&A, Employer aggregate rating, Event, Image metadata, Job posting, Local business, Math solver, Movie, Organization, Product, Profile page, Q&A, Recipe, Review snippet, Software app, Speakable, Subscription and paywalled content, Vacation rental and Video.

The list has been shrinking, and several features that older tutorials promise are gone. Google's Search Central documentation changelog records each retirement:

Rich results that older guides still recommend
FeatureStatus as of November 2026Changelog entry
FAQNo longer shown from 7 May 2026; documentation removed8 May and 15 June 2026
How-toNo longer shown; documentation removedSeptember 2023
Sitelinks search boxNo longer available; documentation removed29 November 2024
Practice problemsNo longer shown; documentation removed6 January 2026
DatasetUsed by Dataset Search only, not Google Search5 November 2025

If your content type is not on the current list, markup can still describe it, but there is no rich result to earn. That is worth knowing before you spend an afternoon on it.

03Step 2: Mark up content that readers can see

Google's introduction to structured data defines it as a standardized format for providing information about a page and classifying its content. It supports JSON-LD, Microdata and RDFa and recommends JSON-LD where your setup allows, because it is the easiest to maintain at scale.

The same page sets the rule that trips most sites: do not add structured data about information that is not visible to the user, even if it is accurate. If the markup says a recipe takes 20 minutes, the page should say so too. On WordPress, the usual route is a plugin or theme setting; our testing guide shows how to see what is actually printed.

04Step 3: Include every required property

Each feature guide lists required and recommended properties. The general structured data guidelines are blunt about the first group: items missing required properties are not eligible for rich results. Recommended properties improve the result but are optional.

Google's introduction adds a useful caution. It is more important to supply fewer but complete and accurate recommended properties than to fill every field with badly formed or inaccurate data. A product with a real price and no rating is better than one with an invented rating.

05Step 4: Follow the content policies

Valid syntax is only half of eligibility. The general guidelines list quality rules that no testing tool can check:

  • Mark up only content that is visible to readers of the page.
  • Do not mark up irrelevant or misleading content, such as fake reviews.
  • Keep information current; Google will not show rich results for time-sensitive content that is no longer relevant.
  • Use the most specific schema.org type that applies, and put the markup on the page it describes.
  • Make sure image URLs in the markup are crawlable and indexable.

Some features add their own rules. Review snippets, for example, are never shown for a business reviewing itself; the review schema guide in this section explains that rule in full. Breaking a quality rule can lead to a manual action, which removes rich result eligibility without changing web ranking.

06Step 5: How do you test whether a page is eligible?

  1. Paste your JSON-LD into the Rich Results Test code tab while you build it, and fix every critical error.
  2. Publish, then run the live URL through the Rich Results Test to see what Google can fetch.
  3. Use Test live URL in Search Console's URL Inspection tool to confirm Google sees the same markup.
  4. If the test flags errors you do not recognize, look the message up in our structured data error map.

Google's feature guides say non-critical issues are worth fixing for quality, but are not needed for eligibility. Fix critical errors first.

07Step 6: Keep the page crawlable and indexed

The guidelines' access rule is short: do not block structured data pages to Googlebot with robots.txt, noindex or any other access control. A page Google cannot crawl cannot show a rich result, however good its markup.

After launch, Google's feature guides suggest submitting a sitemap and allowing time for recrawling. Then watch the matching rich result report in Search Console, where valid and invalid items appear once Google has processed the pages.

08Why do eligible pages still show plain results?

Google's guidelines say directly that it does not guarantee structured data will show, even when the Rich Results Test passes. The algorithm tailors results to the search, the location and the device, and sometimes a plain result is judged best. The guidelines also list markup that does not represent the main content, errors the test could not catch and content hidden from users.

If a page used to show a rich result and stopped, that is a diagnosis problem rather than a setup problem, and our checklist for rich snippets that stop showing starts there.

09When should you optimize for rich snippets?

When three things are true: the page's content matches a feature on Google's current list, the page already shows the information the feature needs, and the information stays accurate over time. A recipe site, an events calendar or a store with real customer reviews fits. A service page hoping for stars on its own testimonials does not.

Example 1 · a minimal product snippet with an offerJSON-LDDisplay only
1{2  "@context": "https://schema.org",3  "@type": "Product",4  "name": "Example Desk Lamp",15  "image": "https://example.com/photos/lamp.jpg",6  "offers": {27    "@type": "Offer",8    "price": "49.00",9    "priceCurrency": "USD",10    "availability": "https://schema.org/InStock"11  }12}
  1. 1Line 4name is required for product snippets
  2. 2Line 6one of offers, review or aggregateRating is required

The example uses only properties the page would visibly show. For how the pieces fit together across a whole site, start with the handbook's opening page, and browse the schema types section for each feature's own rules.

10Questions

Q1How long does it take for rich snippets to appear?

Google gives no fixed time. Its feature guides say it may take several days after publishing for Google to find and crawl a page, and recrawling and reindexing take longer for some sites. Submitting a sitemap and requesting a recrawl in Search Console helps Google find the change sooner.

Q2Do I need a plugin to get rich snippets in WordPress?

No. Google's introduction mentions CMS plugins as one route, but JSON-LD can be printed by a theme or a small custom plugin just as well. What matters is that the markup is valid, describes visible content and is not duplicated by two sources on the same page.

Q3Are rich snippets and rich results the same thing?

In practice, yes. Rich snippets was the earlier name for search results enhanced by structured data. Google's current documentation uses rich results for the whole family, which includes cards, carousels and other features as well as the classic snippet line.

Q4Can I get FAQ rich snippets in 2026?

No. Google's documentation changelog records that FAQ rich results stopped appearing in Google Search from 7 May 2026, and the FAQ documentation was removed in June 2026. FAQPage markup is still valid schema.org, but it no longer produces a Google rich result.

11Sources