🔍 SEO / GEO

Snippet

snippet · rich snippet · search snippet · serp snippet · featured snippet · result snippet

Definition

A snippet is the block describing a page in search results, made up of a title, a description, the address and additional elements, some of which are generated from structured data markup.

What a snippet is assembled from

A snippet is how a page looks in the search results. For the user it is the only source of information before the click, so at an equal position a difference in presentation converts directly into a difference in traffic.

Element	Where it comes from	How controllable it is
Title	The title tag, sometimes the H1 or anchor text pointing at the page	Partly: the engine may rewrite it
Description	The meta description or a fragment of the page text	Partly: rewritten often
Address	The URL or breadcrumbs from BreadcrumbList markup	Controllable through markup
Sitelinks	Generated algorithmically from the site structure	Indirectly: through navigation and internal linking
Price and availability	`Offer` markup	Controllable, but it must match the site
Rating and reviews	`AggregateRating` and `Review` markup	Controllable where real reviews exist
Questions	`FAQPage` markup	Controllable
Date	`Article` markup, a date in the text	Partly
Image	The page’s main image, markup	Indirectly

Why descriptions get rewritten

A meta description is not something that must appear in the results; it is a hint. The search engine is solving the problem of showing the user the fragment that best answers their query, and if such a fragment exists in the page text, that is what gets shown.

The usual reasons for a rewrite:

The description is too generic. “An electronics store with nationwide delivery” does not answer the query “Samsung fridge 300 litres 60 cm wide”.
One page, many queries. A category page ranks for dozens of phrasings, and a different fragment is selected for each.
The description does not match the content. A promise in the description that the page does not keep is a reason to replace it.
There is no description. Then a fragment is always taken from the text.

None of that is a reason to skip the description: it remains the default and is used in social previews. The right conclusion is different — write it specifically, and make sure the page content answers the query in the same words people use to ask it.

💡

A quick diagnostic: export from Search Console the queries with high impressions and low CTR at positions 3 to 10, then look by hand at how their snippets appear. Usually 5 to 7 of any 20 such URLs show the same problem — a truncated title, a description duplicated across the whole section, or no rich elements where neighbouring results have them.

Types of snippet

Type	What it shows	Where you see it
Ordinary	Title, description, address	Any page
Rich	Plus markup data: rating, breadcrumbs, questions	Product pages, articles, FAQs
Product	Price, availability, rating, sometimes an image	Product pages with Offer markup
With sitelinks	A block of section links under the main result	Homepages and major sections on brand queries
Featured snippet	A direct answer in a block above the results	Informational queries with a clear answer
Video	A clip preview with timestamps	Pages with video and VideoObject markup

The featured snippet deserves a separate note: it gives maximum visibility but often satisfies the need entirely — the user reads the answer and does not click through. It is a special case of zero-click search and should be treated accordingly: winning the block helps recognition, but judging it purely on click growth is wrong.

In practice: writing for click-through

Title. Main query near the beginning, length around 50 to 60 characters so it is not truncated. Then a differentiator: a “from” price, the size of the range, a delivery time, a warranty. A catalogue template usually looks like “{Category} — Buy in {City} | {N} models, delivery from {time}” and is populated from data rather than hand-written per page.

Description. 140 to 160 characters, specifics instead of adjectives: availability, the price range, delivery and returns terms, the number of products or reviews. Duplicating one description across a whole section is pointless — it will almost certainly be replaced.

Product pages. The main work is not in the text but in the markup: accurate price and availability, an honest AggregateRating, BreadcrumbList instead of a long address. A mismatch between the price in the markup and the price on the storefront is the most common reason for losing the product snippet.

Categories. Here an opening paragraph with a direct answer to the implied question helps (“412 models in the category, prices from $129, next-day delivery”), together with a correct ItemList. Such a paragraph both raises the chance of being picked as the fragment and works for generative answers.

What not to do: do not promise in the snippet what the page does not deliver; do not mark up a rating where there are no reviews; do not stuff the title with keywords — a title truncated by width loses precisely the part it was written for.

How to monitor

Search Console, Performance. Split by page and query: impressions, clicks, CTR, average position. Work with CTR at a fixed position — otherwise a rise in ranking will be mistaken for the success of a copy edit.
Search Console, Enhancements. Structured data errors that stop rich elements from appearing.
Yandex Webmaster. The structured data validator and query statistics for Yandex, if you work in Russia or CIS markets.
Rich Results Test and validator.schema.org. A spot check of the template before shipping.
A regular snapshot of the results. Once a month, collect the real snippets for 30 to 50 priority URLs and compare them with the intended ones: this is how you discover that descriptions are being rewritten across a whole section, or that the price in the markup has fallen behind the storefront.

Frequently asked questions

Why does the search engine rewrite my description?

Because a description is a recommendation, not a command. The engine picks, for each specific query, the fragment that answers it most precisely: if the description carries a generic line about the store while the page text has a paragraph about exactly what the user asked, the paragraph wins. Rewriting is neither an error nor a penalty. The cure is not to fight the algorithm but to make the description specific and consistent with the content: name the model, the specification, the delivery terms.

How does a rich snippet differ from an ordinary one?

An ordinary snippet is a title, a description and the address. A rich snippet adds data from structured markup: price and stock status, rating stars and review counts, breadcrumbs instead of a long URL, expandable questions from FAQPage, a publication date. It takes more space in the results and stands out more, so at an equal position it usually collects more clicks.

How do you raise a snippet's CTR?

Three levers. First the title: put the main query near the beginning and add a differentiator — a price, a delivery time, the size of the range. Second the description: specifics instead of generalities, an answer to the question implied by the query. Third the markup: rating, price and availability give you visual elements the neighbouring results lack. Measure the effect on CTR at a fixed position, otherwise a rise in ranking will be mistaken for the success of your edit.

What is a featured snippet?

A featured snippet is the block with a direct answer above the main results, assembled from the text of one page. It gives visibility, but it often satisfies the user completely and no click follows. Pages that win one tend to have a short structured answer to a specific question: a 40 to 60 word definition, a numbered list of steps, a compact table.

Where do you monitor how your snippets look?

In Google Search Console, the performance reports broken down by query and page show impressions, clicks, CTR and position together, and the enhancements section lists structured data errors. Yandex Webmaster offers a structured data validator and query statistics for Yandex, the dominant search engine in Russia and several CIS markets. For one-off checks use the Rich Results Test and the Schema.org validator; at scale, capture the real snippets for a sample of priority URLs.