“Rich snippets” is the familiar SEO term for enhanced search listings; Google generally calls these appearances rich results. Structured data can make a page eligible for certain rich results by giving Google explicit clues about its content, but valid markup does not guarantee that Google will show an enhancement or improve the page’s ranking. The practical goal is accurate, useful markup that meets the requirements for a currently supported feature.
What are rich snippets?
Structured data is standardized markup that describes the meaning of information on a page. Google can use it to understand page content and, for supported content types, may use it to show a richer search appearance called a rich result. People often use “rich snippet” broadly for these enhanced listings, though Google’s documentation generally uses “rich result.”
The terms refer to different things: structured data is the information you add to a page; a rich result is a possible presentation Google may create from it. Adding markup is not the same as adding a feature directly to the search result, and schema.org markup by itself does not establish eligibility for every Google feature.
Google’s feature gallery includes types such as Article, Breadcrumb, Event, Product, Recipe, Review snippet, Software app, and Video. The appearance can vary from a feature preview, and each feature has its own required properties and policies. Choose a feature because it accurately fits the page’s main content, not because its preview looks prominent.
#1 Best Overall
How do I get rich snippets in Google?
You can make a page eligible by choosing a supported feature, adding accurate structured data that matches visible page content, and meeting both Google’s general guidelines and that feature’s requirements. Eligibility is not a promise of display: Google’s systems choose how to present results using multiple variables, including the search context.
- Choose a suitable page and feature. Start with a page whose visible main content genuinely matches a feature Google currently supports. Check the feature’s required properties and its policies rather than assuming a generic schema type qualifies.
- Write accurate markup. Include required properties and any relevant recommended properties. Every value should describe content a visitor can find on that page. Do not add hidden, misleading, irrelevant, or incomplete information to try to qualify.
- Use a supported format. Google supports JSON-LD, Microdata, and RDFa. It recommends JSON-LD when a site’s setup permits it because it is generally easier to implement and maintain at scale and less prone to user errors.
- Validate before launch. Run the page through Google’s Rich Results Test and address critical errors. A clean test is useful, but it does not guarantee that Google will display a rich result.
- Deploy and inspect the live page. Test the deployed URL and check that the rendered page still contains the content described by the markup. A CMS setting or plugin may add structured data, but you remain responsible for checking its output.
- Monitor and measure. Review the relevant Search Console rich result reports for validity issues and compare site performance over time. Reports show samples of detected items, not a complete inventory of every eligible page.
Which structured-data format should you use?
| Format | Google Search support | When it may fit |
|---|---|---|
| JSON-LD | Supported; recommended by Google when practical. | Often the simplest choice when the site can add and maintain a separate JSON-LD block describing the page. |
| Microdata | Supported. | A reasonable alternative where the existing site implementation embeds metadata in HTML elements. |
| RDFa | Supported. | A reasonable alternative where the site already uses RDFa or its implementation makes that format appropriate. |
Google does not present these formats as different ranking strategies. Use the format your site can output consistently and maintain accurately; changing formats is not a shortcut to a better ranking or guaranteed rich result.
Rank #2
How to add and validate structured data
Start with one representative page
Choose a page where the desired feature clearly matches the content users see. For example, a recipe page may be a candidate for Recipe structured data if it actually presents a recipe and satisfies that feature’s requirements. Do not mark up a whole site with one type merely because the CMS makes it easy. A page’s main content, not its template label, should determine the type.
Implement the properties the feature requires
Use Google’s feature-specific documentation to identify required properties, then add only recommended properties that are accurate and relevant. Required fields affect eligibility; optional fields are not a reason to invent information. Keep structured data aligned with visible page content as it changes. If a CMS or plugin generates markup, inspect the generated output on representative pages instead of assuming its defaults fit every page.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
Test, publish, and check again
- During development: Use the Rich Results Test to find critical errors and confirm whether the markup is recognized for the feature.
- After deployment: Test the live URL. Differences between a development page and the deployed page can reveal missing content or markup.
- In Search Console: Inspect URL-level information and monitor the available rich result reports for validity issues. Treat report counts as samples, not a full site census.
- When something changes: Revalidate pages after changing templates, plugins, content, or markup, especially if those changes could remove visible information described by the structured data.
A syntactically valid result is only one check. Google’s general guidelines also govern content quality and policy compliance. Hidden, irrelevant, misleading, incomplete, or policy-violating data can prevent eligibility or lead to a manual action. A structured-data manual action removes rich-result eligibility; Google’s guidance says it does not affect ranking in Google web search.
Does schema markup improve SEO?
Not by itself in the sense of a guaranteed ranking boost. Structured data is descriptive markup, not a ranking shortcut, and Google does not guarantee a rich result even when a page is marked up correctly and passes the Rich Results Test. Google can instead show a plain text result or another presentation according to the search context and other variables.
A richer appearance may affect how a result is presented, but the outcome for a particular site cannot be promised. Google’s documentation lists reported examples from individual organizations: Rotten Tomatoes reported a 25% higher click-through rate on pages enhanced with structured data versus pages without it; Food Network reported converting 80% of pages to enable search features and a 35% increase in visits; Rakuten reported 1.5 times more time spent on pages with structured data than pages without it, and a 3.6 times higher interaction rate on AMP pages with search features versus non-feature AMP pages; Nestlé reported an 82% higher click-through rate for pages that show as rich results versus non-rich-result pages. The cited Google page does not state the years for these individual figures. They are examples, not general causal estimates or forecasts for another site.
For your own site, compare performance over time instead of treating those examples as a prediction. Select reasonably stable pages, confirm that markup is valid and discovered, then compare Search Console performance over a period of months. Note other changes to the pages and account for seasonal or search-context differences before attributing a change to structured data.
FAQ rich results: what changed?
Google’s June 2026 documentation update says the FAQ rich result feature is no longer shown in Google Search results. Do not add FAQ markup as a way to obtain that Google search appearance. This change concerns the Google feature; it does not establish whether FAQ content or markup is useful to other systems. A page can still contain useful answers for readers without promising an enhanced result.
Common problems and fixes
- The test reports a critical error: Check the feature’s required properties and the exact values in the markup. Correct the underlying page or markup, then test again.
- The test passes but no enhancement appears: A pass indicates that the markup can be eligible, not that display is guaranteed. Check the deployed page and Search Console for issues; allow for Google’s choice of presentation.
- The markup describes content visitors cannot see: Remove or correct it so it reflects relevant visible page content. Do not use hidden or misleading data to qualify.
- A CMS or plugin produces inconsistent markup: Review output on more than one representative page and verify it matches each page’s main content. Adjust the CMS settings or plugin configuration where available.
- Search Console shows fewer items than expected: The reports are samples of detected items, not a comprehensive inventory. Inspect specific deployed URLs as well as monitoring reports.
- A feature is absent from Google’s supported options: Do not infer Google eligibility from the existence of a general schema.org type. Choose a currently supported feature with requirements that match the page.
Or skip the browser setup
If you need a visual record of a page while reviewing its content or search-related changes, ScreenshotNeo can capture a URL with one request. This is for documenting the page appearance, not a substitute for validating structured data in Google’s Rich Results Test or monitoring Search Console.
ScreenshotNeo API documentation
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with response headers identifying the page verdict and billing status. Its MCP server includes tools for AI agents to take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. See ScreenshotNeo and the API documentation.
Sign up free for 1,000 screenshots a month with no card.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchFrequently Asked Questions
Can valid structured data still be ignored by Google?
Yes. A valid test can establish eligibility, but Google decides whether and how to show a rich result.
Can I use more than one structured-data format on a site?
Google supports JSON-LD, Microdata, and RDFa; use an implementation your site can maintain accurately. The formats are not different ranking strategies.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
