Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

How are featured snippets different from structured-data rich results?

A featured snippet is a passage Google’s systems select from a page’s visible content and show first in a result. A rich result is an enhanced display that depends on structured data the site has added to describe the page. The first cannot be requested with markup. Google’s documentation answers the question of how to mark a page as a featured snippet in two words: “You can’t” (Google’s featured snippets documentation). The second cannot exist without markup, since a page must include the required properties to be eligible. They differ in where the content comes from, in what the site owner controls, and in how each is checked.

Extracted search answers

The documentation defines the feature by its layout: “Featured snippets are special boxes where the format of a regular search result is reversed, showing the descriptive snippet first”. It adds that they can also appear within a group of related questions.

On selection, the same page says: “Google systems determine whether a page would make a good featured snippet for a user’s search request, and if so, elevates it”.

What this means for a site:

  • The text shown is drawn from the page’s own content.
  • There is no markup type that nominates a page.
  • Selection is made per search request.
  • A click, according to the documentation, “takes the user directly to the section of the page that appeared in the featured snippet”, without any annotation by the site.

What a site can do is limited to the content itself and to opting out.

Markup-eligible rich results

A rich result is a search listing with added elements, such as a rating, a price, a cooking time, or a breadcrumb, drawn from structured data. Google’s introduction to structured data says: “You must include all the required properties for an object to be eligible” for a rich result (Google’s introduction to structured data).

Characteristics:

  • Each rich result type has its own documentation, with required and recommended properties.
  • The markup must describe content visible on the page.
  • Eligibility can be tested before publishing.
  • Eligibility does not ensure display. Google’s guidelines say that structured data “enables a feature to be present, it does not guarantee that it will be present” (Google’s structured data general guidelines).

Source and control differences

Aspect Featured snippet Structured-data rich result
Source of the displayed content A passage from the page's visible text Properties in the page's structured data, which must match visible content
What makes a page a candidate Google's systems judge the page a good answer for the search The page carries valid markup for a supported type with all required properties
Can the site request it? No The site can make the page eligible; display is still Google's decision
Markup involved None JSON-LD, Microdata, or RDFa
Checking in advance Not a structured data type, so the Rich Results Test does not address it Rich Results Test
Reports in Search Console Not covered by the reports that are organized by structured data type Enhancement reports for supported types
Opting out nosnippet, data-nosnippet, or a lower max-snippet value Remove the markup
What the site controls The clarity and placement of the answer on the page The accuracy and completeness of the markup

The opt-out controls are worth a note because they are the only direct levers on featured snippets, and all of them remove or restrict. The documentation describes the nosnippet rule as blocking all snippets for a page, the data-nosnippet attribute as excluding marked text, and the max-snippet rule as a way to try keeping regular snippets while leaving featured snippets. On the last it is cautious: “Using a low max-snippet setting doesn’t guarantee that Google will stop showing featured snippets for your page”.

A page can have both. A recipe page might be shown as a rich result with a rating for one search and supply a featured snippet from its method for another. One does not cause or prevent the other.

Content implications

Because the mechanisms differ, the work differs.

For featured snippets, the work is editorial.

  • State the answer to the page’s question directly, near the heading that asks it.
  • Keep the answer self-contained, so it reads correctly when lifted out of the page.
  • Use lists and tables where the answer is a sequence or a comparison.
  • Make sure the passage is accurate alone. Qualifications placed three paragraphs later will not travel with it.

None of these is a documented requirement, and none guarantees selection. They make the page a clear answer, which is useful to readers whether or not Google features it.

For rich results, the work is technical and factual.

  • Choose the type that matches the page.
  • Supply every required property and the recommended ones the page can support.
  • Keep markup and visible content identical.
  • Test, and retest after template changes.

Confusions to correct:

Belief Correction
FAQ or HowTo markup produces a featured snippet Featured snippets are not produced by markup
A featured snippet is a kind of rich result that can be validated The Rich Results Test validates structured data; a featured snippet is selected from page text
Losing a featured snippet means the markup broke Selection is per search and can change without any change on the page
Structured data guarantees a rich result It establishes eligibility only
Opting out of snippets leaves rich results unaffected A nosnippet rule removes the snippet text; check each feature's documentation before applying it

Measurement differs as well. Rich result types that have a search appearance filter can be isolated in the performance report. A featured snippet is observed directly: search, and record what appears, with the date, device, and location noted.

Both features sit among several that answer a search on the results page itself. Knowledge panels are another, with a different source again, and they are explained in the guide to how Google knowledge panels satisfy searches without requiring a website visit.

The distinction to keep: a featured snippet is chosen from what the page says, and a rich result is built from what the markup declares.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *