SERP Feature Glossary

Type almost any query into Google today and the standard ten blue links are only part of what comes back. There might be a box that already answers your question, a strip of related questions you didn't ask, a panel about a company on the right side, a map with three pinned businesses, or a row of product images before a single organic result even appears.

Marketers throw these names around constantly — "we're in the snippet," "we lost the PAA box," "the knowledge panel is wrong" — but it's easy to mix them up or not know one exists until it's costing you clicks. This glossary defines every SERP feature you're likely to run into in 2026, what triggers it, and whether it's something your site can actually earn.

What is a SERP feature?

A SERP feature is any element on a search results page that isn't a plain organic listing — a title, URL, and description in a row. Google adds these features to answer a query faster, show a different content format, or surface an entity it already recognizes. Here's the current glossary, grouped by what they show:

• Featured snippet. A boxed answer pulled from a ranking page, shown above the first organic result, usually as a paragraph, list, or table extracted directly from on-page content.
• People Also Ask (PAA). An expandable stack of related questions; clicking one reveals a short answer and often triggers more questions to appear beneath it.
• Knowledge panel. A right-side (or top, on mobile) card about a recognized entity — a person, company, or place — pulled from Google's knowledge graph rather than any single page.
• Local pack (map pack). A cluster of three map-pinned local businesses shown for queries with local intent, drawing from Google Business Profile data rather than website content.
• Image pack. A horizontal row of images relevant to the query, shown for visually-oriented searches and linking through to Google Images.
• Video carousel. A scrollable row of video thumbnails, usually sourced from YouTube, shown for how-to and tutorial-style queries.
• Top stories. A carousel of recent news articles for a query with a current-events angle, sourced from indexed news publishers.
• Sitelinks. Extra links shown beneath a single organic result, usually for branded or navigational queries, pointing to other pages on that same site.
• Review-rich snippet. Star ratings and review counts shown beneath an organic listing, generated from review schema markup on the page.
• FAQ rich result. An expandable question-and-answer list attached to an organic listing, generated from FAQPage structured data.
• How-to rich result. A numbered, sometimes image-supported set of steps shown beneath a listing, generated from HowTo structured data.
• Shopping results. A row of product cards with images and prices, shown for commercial queries and sourced from merchant product feeds.
• Related searches. A set of alternate query suggestions, typically shown at the bottom of the results page.
• Instant answer. A direct fact — a calculation, definition, unit conversion, or similar — computed by Google itself rather than sourced from any page.

Some of these are ownable by any site with the right content and markup; others depend on an entity or listing Google already recognizes, which changes how you'd go about targeting each one.

Why SERP features matter

Ignoring which features appear for your target keywords means planning content for a results page that no longer exists:

• They redistribute clicks, not just attention. A featured snippet or instant answer can fully satisfy a searcher on the results page itself, pulling clicks away from every listing below it, including the one it's sourced from.
• They change what "ranking #1" is worth. A page can hold the top organic slot and still get a fraction of the clicks it would without a competing feature above it.
• Some are earnable without being #1. Featured snippets and PAA answers are often sourced from pages ranking lower on page one, which makes them a route to visibility that doesn't depend on outranking everyone else.
• They signal what Google thinks the query wants. The mix of features present for a keyword is a direct readout of the intent Google has assigned it — informational, local, transactional, or navigational.

Step-by-step: identifying features for your keywords

1. Search the exact keyword from the target location. Use an incognito window or a location-set SERP simulator so you're seeing what a real searcher there would see.
2. Record every feature present, not just the organic listings. Note snippets, PAA, packs, carousels, and rich results, along with which domain (if any) each one cites.
3. Classify each feature as ownable or entity-bound. Featured snippets and rich results are generally open to any well-structured page; knowledge panels and local packs depend on an entity Google already recognizes.
4. Match content format to the feature type. A paragraph-style snippet wants a direct-answer paragraph on the page; a list-style snippet wants an actual list, not a paragraph reformatted as one.
5. Add the matching structured data. Use FAQPage, HowTo, Review, or Recipe schema where the content genuinely fits that format, since markup alone doesn't force a feature to appear.
6. Re-check the SERP after publishing. Feature presence shifts over time and by device, so a one-time check isn't enough — track it the way you'd track a ranking position.

Common mistakes when targeting SERP features

1. Adding schema for a feature that isn't relevant to the query

Marking up FAQ or HowTo content on a page that doesn't answer a question-based query won't force that rich result to appear — the underlying content still has to match the query's intent.

2. Chasing a knowledge panel with on-page content alone

Knowledge panels are generated from entity recognition across the web, not from a single page's copy, so the fix is usually entity signals — consistent naming, sameAs links, and third-party mentions — rather than more on-page text.

3. Ignoring which feature is already citing a competitor

If a competitor already holds the featured snippet for a keyword, matching or beating their answer format is usually more effective than writing more content in a format the snippet isn't drawing from.

4. Treating all features as equally valuable to win

Some features, like related searches, carry little standalone value; effort is better spent on features proven to drive clicks or visibility for that specific query, not every feature present.

5. Not checking device differences

A feature mix confirmed on desktop can look completely different on mobile, where carousels and packs are often prioritized higher on the page.

Real-world examples by query type

How the feature mix typically shifts depending on what the searcher is actually trying to do:

The pattern across all four: the feature mix isn't random — it's Google's read on intent, which is exactly why checking the current SERP before optimizing matters more than assuming what should appear.

SERP feature comparison table

How the major feature types differ in what earns them and what they typically do to clicks.

Preview your SERP feature footprint — free

The Rebrixe SERP Simulator shows you exactly how a results page renders for any keyword — snippet, PAA, packs, and rich results included — so you know what you're actually competing against before you optimize a single page.

Frequently asked questions