New format
Search snippets: Title, description, and rich results
A snippet is the page block in search results: title, URL/breadcrumbs, description, and sometimes extensions (rating, price, FAQ). It decides whether people click your position.
Below: the basic anatomy, rich results, and schema.org markup. A strong snippet lifts CTR; rankings grow from content, tech, and links — not from one structured-data block alone.
What a regular snippet includes
Classics: Title (often from `<title>`), URL or breadcrumbs, description from meta description or page text. Display lengths drift — keep the meaning early.
Write title and description for humans: benefit, difference, no keyword sheet. Stuffing the description kills the click.
Basic checklist:
- unique Title for the intent
- description with value and a CTA
- readable URL / breadcrumbs
- snippet promise matches page content
Rich results (extended snippets)
Extensions depend on type: product (price, availability), reviews, FAQ, how-to, organization. Not every site gets every type — there are content and policy requirements.
An extension helps you stand out and answer before the click. Don’t promise in markup what’s not on the page: that leads to manual actions and lost rich results.
Why bother:
- more visibility at the same position
- clearer offer (price, rating)
- fewer empty clicks past the intent
Breadcrumbs and the path in results
On the site, breadcrumbs are navigation “Home → Section → Page.” In results the search engine may show a similar path.
BreadcrumbList markup (JSON-LD or microdata) helps machines understand hierarchy. First put real breadcrumbs in HTML, then markup — not the other way around.
Schema.org and JSON-LD
Schema.org defines entity types: Product, Article, Organization, FAQPage, and others. You mark fields (name, price, author); the search engine decides whether to show an extension.
JSON-LD is convenient: one script block, less layout mess. Microdata sits in tags — also valid, harder to maintain. After rollout, run the URL through the official rich results test and Search Console / webmaster reports.
Rollout practice:
- pick a type that matches real content
- don’t mark up invented reviews/prices
- align with visible page text
- validate
- watch whether the type appears in reports (it can take time)
FAQ
Does the meta description guarantee the snippet text?
No. The search engine may take another page fragment if it answers the query better. Description is a strong hint, not an order.
Does the snippet affect rankings?
There’s no direct “points” factor for a pretty snippet. Indirectly — via CTR and behavior. The main thing is a relevant page.
What are rich results?
SERP extensions: stars, price, FAQ, recipe, and so on. They appear with valid structured markup and when the result type’s rules are met.
JSON-LD or microdata in HTML?
Both are understood. JSON-LD in `<script type="application/ld+json">` is usually easier to maintain. Check with a rich results validator.
Do I need breadcrumbs?
Yes for on-site navigation; in the SERP a path also helps show the section. Add BreadcrumbList markup if you want, following the spec.
SERP lines look dull and CTR lags behind the position?
We’ll tune Title/description, breadcrumbs, and valid schema for rich results — without TOP myths.
Discuss the task
