SERP Features: The Full Map, and Which Ones You Can Actually Earn

A SERP feature is any element on a Google results page that is not a standard organic listing: the answer box at the top, the questions other people asked, the star ratings under a link, the row of images, the map of nearby businesses. That is the industry's definition, and the first useful thing to know is that Google does not use the phrase. Google publishes its own vocabulary for the same page, and it draws a line that most published lists skip entirely: which elements a site owner can optimize for, and which ones Google generates on its own. This guide maps the results page using Google's names, sorts every element by the mechanism that produces it, and says plainly where no lever exists. It is written for founders, heads of growth, and first in-house SEO hires who want to know what they are looking at before deciding what to chase.

The short version

• Google does not use the term "SERP feature" in its own guide to the results page. It calls these things visual elements and sorts them into five kinds.
• Google's gallery states its own purpose as explaining what the elements look like, what they are called, and whether you can optimize your website for each one. That last part is the question most feature lists never answer.
• The useful split is by mechanism, not by name: earned by markup, earned by content, or automated and outside your control.
• The featured snippet does not appear as a named element in Google's gallery. It shows up inside the description of the People Also Ask block.
• There is no correct number of SERP features. Published counts run from five to "37+" because every list draws its own boundary, and rich results alone expand into dozens of types.

What is a SERP feature?

Any part of a search results page that is not a plain organic listing. That covers the featured snippet, People Also Ask, image and video blocks, knowledge panels, local packs, AI Overviews, and the star ratings and prices that decorate individual results.

The term is the industry's, not Google's. It emerged because SEO tools needed a filter label for "things on the page that are not the ten blue links," and it stuck. Nothing is wrong with using it, and this article uses it throughout. But if you go looking for Google's definition of a SERP feature, you will not find one, and that gap is why every guide on this subject publishes a different list.

What Google publishes instead is a Visual Elements gallery in Search Central, which defines a visual element as "the building blocks of the Google Search results page that a user can perceive or interact with." The gallery describes itself as an illustrated guide that explains what the elements look like, what they are called, and whether you can optimize your website for each element.

That third clause is the one worth stopping on. Google is not just naming the parts. It is telling you, element by element, whether there is anything you can do about them.

What does Google actually call the parts of its results page?

Visual elements, sorted into five types of search result. Google's categories are organized by what produces the result, which is a more useful organizing principle than the visual groupings most feature lists use.

• Text result: a result based on the textual content of the page. Google notes this was "formerly known as a 'web result' or 'plain blue link'."
• Rich result: a result that "typically relies on structured data in the markup of your page" to display graphical or interactive elements.
• Image result: a result based on an image embedded on the page, more likely to appear for image-seeking queries.
• Video result: a result based on a video embedded on the page, more likely to appear for video-seeking queries.
• Exploration features: elements that help searchers expand or refine their original search.

Each result type has child elements. A text result carries an attribution block, a title link, a snippet, and optionally a byline date, a sitelinks group, a text result image, or rich attributes. The attribution block itself breaks down further into favicon, site name, and visible URL, and the visible URL splits into domain and breadcrumb.

Google adds two caveats that matter for anyone planning work around this. Element appearance "can change over time," and a given result displays differently depending on device, country, query language, and other factors. Google also states plainly that you will never see a text result containing all of the possible visual elements at once.

How many SERP features are there?

There is no agreed number, and any specific count tells you more about the writer's boundary than about Google. Published guides range from "Top 5" to "37+," and both can be defended.

The reason is structural. Google's gallery names a modest set of individual elements, but one of its five categories, the rich result, is a doorway rather than an item. Rich results expand into the whole list of structured data features Google supports, covering page types from job postings and events to software apps, recipes, and vacation rentals. Count rich results as one feature and you get a short list. Count each supported type separately and the number climbs past thirty without anyone being wrong.

Treat the count as noise. What changes decisions is not how many elements exist but which of them respond to work, and that question has a stable answer even as the element set shifts.

The full map: which element is earned by what?

The table below maps each element to the mechanism that produces it and how much control you have. Grouping is by mechanism rather than appearance, because that is what decides whether a task belongs on a roadmap.

Visual element	What produces it	Your level of control
Rich result	Markup: structured data matching a supported feature type	High over the input. Google still decides whether to display it.
Rich attributes (review stars, recipe details)	Markup: Google describes these as "typically powered by structured data, provided by you"	High over the input, same caveat.
Breadcrumb	Markup: Breadcrumb structured data	High. Google documents how to specify the trail.
Site name	Markup: structured data declaring the site name	High. Google documents how to provide it.
Favicon	File: a crawlable favicon you provide	High over the file. Display is Google's call.
Title link	Content: page title and on-page context	Medium. Google may rewrite it.
Snippet	Content: page text, plus snippet controls such as max-snippet and nosnippet	Medium. You can limit it more reliably than you can dictate it.
Byline date	Content: a clear published or updated date on the page	Medium. Google estimates the date.
Text result image	Content: the most relevant image on the page for the query	Medium, via image best practices.
Image result	Content: an indexed image embedded on the page	Medium, via image best practices.
Video result	Content: an indexed video embedded on the page	Medium. Thumbnail and upload date are documented.
Featured snippet	Content: a clean, liftable answer to the question	Medium. No markup exists for it.
AI Overview	Content: being indexed and eligible to show with a snippet	Low. No special markup or submission exists.
Sitelinks group	Automated: Google clusters links from your domain	Low. Google states sitelinks are automated, with best practices only.
Related searches group	Automated: generated from the query and what others searched	None.
Related questions group (People Also Ask)	Automated: a cluster of questions related to what the user initially searched for	None over the questions. You can influence the snippet shown inside one.

Two rows on that table already have depth coverage worth reading before you act on them: how Google generates the title link, and the structured data that earns rich results.

Which features can you actually earn?

Three classes, and knowing which one an element belongs to is more useful than knowing its name.

Class 1, earned by markup: rich results, rich attributes, breadcrumbs, and site name. Structured data is the lever, the work is concrete, and the outcome is verifiable with Google's testing tools. You control the input completely. What you do not control is the display decision: valid markup makes a rich result possible, never certain.

Class 2, earned by content and format: the title link, snippet, byline date, text result image, image and video results, featured snippets, and AI Overview citations. No markup produces these. They come from writing the answer clearly, structuring the page so the relevant part is liftable, and giving Google clean signals like a real published date. Control here is genuine but partial, and Google reserves the right to rewrite what you supply.

Class 3, automated: related searches, related questions, and to a large extent sitelinks. Google's language on exploration features is unambiguous: "While you can't control what shows up here, it can be helpful to pay attention to the related search queries when you're thinking about topics you could write about for your site." Google states that related searches are "automatically generated based on the initial query and other things people have searched for," and files related questions under the same no-control heading.

Sitelinks sit slightly apart and are worth stating precisely, because they are commonly listed as something you optimize for. Google's wording is that "sitelinks are automated," followed by an acknowledgment that some best practices exist for improving their quality. That is influence over quality, not control over appearance, and it belongs in a different mental bucket from structured data work.

The practical consequence: any hour budgeted against a Class 3 element is an hour spent on something with no documented mechanism. Read them as free research into what people ask. That is the use Google suggests for related search queries, when thinking about topics you could write about. Do not put them on a roadmap as targets.

Why are AI Overviews, knowledge panels and local packs missing from Google's gallery?

Because the gallery documents the anatomy of a search result, not every surface that can appear on the page. As of its last documented update, the Visual Elements gallery does not name AI Overviews, knowledge panels, or local packs anywhere. It covers the four result types plus the exploration blocks around them.

That is a real limit on the gallery as a complete map. The industry term "SERP feature" covers more ground than Google's "visual element" does, and neither vocabulary is complete on its own.

For AI Overviews specifically, Google documents the mechanism in a separate guide on AI features and your website, and the guidance there is unusually direct: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." Google adds that you do not need to create new machine readable files, AI text files, or markup to appear in these features. Eligibility comes from being indexed and eligible to be shown with a snippet.

The controls that do exist are subtractive rather than additive. Google points to nosnippet, data-nosnippet, max-snippet, and noindex as ways to limit what appears. You can restrict what Google shows more reliably than you can compel it to show something, which is a pattern worth noticing across the whole Class 2 group. Our guide to how AI Overviews choose what to quote goes into what that means for content structure.

Which features are not worth chasing, even when you can earn them?

Most of them, for most B2B and SaaS sites. Earnability and value are separate questions, and conflating them is the most expensive mistake in this subject area.

Features tied to page types you do not have: a large share of the rich result catalog covers recipes, events, job postings, vacation rentals, movies, and product listings. Across the sources we reviewed, these types make up much of the "37+" counts that circulate, which inflates the apparent opportunity for a software company that has none of those page types. Check the structured data feature list against your actual templates before budgeting anything.

Local packs, for companies without premises: a local pack is earned through a verified business location and proximity to the searcher. For a distributed SaaS company selling to a national or global market, it is not a target. It is not a failure to be absent from one.

Anything in Class 3: covered above. No documented mechanism, no roadmap entry.

The zero-click question deserves care rather than a statistic. More elements push organic listings further down, and an answer displayed in full reduces the reason to click through. Both effects are real in direction, but the measurement is contested: published estimates vary widely depending on whether they count all queries or only commercial ones, which devices they sample, and how they treat searches that end in another search. Our research suggests the honest framing is that a feature above you changes what a ranking position is worth, which is a reason to model traffic conservatively rather than to abandon a keyword.

One angle deliberately not covered here: reading the features on a results page to infer what the searcher wants. That is a different job from earning them, and it is covered in our guide to reading intent from the results page.

How do you find out which features appear for your keywords?

Three methods, in increasing order of effort.

Search Console, for what you already receive: the performance report offers a Search appearance dimension alongside queries, pages, countries and devices. It groups your existing impressions and clicks by the appearance type that produced them. This is the only one of the three that reports on your own site rather than the SERP in general, and most teams have never opened the tab.

A manual check, for your target set: search your ten most important queries and record what sits above the first organic result. Ten queries takes about fifteen minutes and produces a more accurate picture of your specific SERPs than any aggregate report. Use an incognito window, and expect the result to differ by device.

A rank tracker, for scale: most tools carry a SERP feature filter that flags which features appear for tracked keywords. Useful for monitoring change over time across a large keyword set. Treat their feature taxonomies as vendor-specific labels rather than Google's, for all the reasons covered above.

What is the difference between a rich result and a featured snippet?

A rich result decorates your own listing using your markup. A featured snippet lifts your text out of the listing and places it at the top of the page.

Dimension	Rich result	Featured snippet
What triggers it	Structured data in your page markup	Content that answers a question in a liftable form
Where it appears	Attached to your normal listing, in place	Above the organic results
How you work on it	Implement and validate supported schema types	Structure the answer clearly, near the question

The two are confused often enough that it distorts planning, usually in the direction of assuming schema will win an answer box. It will not. There is no markup that produces a featured snippet, and Google's gallery reinforces the separation in an unexpected way: the featured snippet is not listed as a visual element of its own. It appears in the description of the related questions group, where Google notes that expanding a People Also Ask question shows the user a featured snippet.

If the answer box is the target, the mechanism is editorial rather than technical. Our guide to how to win a featured snippet covers the formats Google lifts and how to structure for them.

Where this fits in the rest of your SEO work

Feature work is a layer on top of ranking, not a substitute for it. Almost every element in Class 1 and Class 2 requires you to rank on page one before it can appear, so relevance, coverage and technical health come first. Our complete guide to SEO sets out that sequence.

The order that works: rank first, then audit which elements your page types are eligible for, then implement markup where it is supported, then structure content for the format-driven elements. Reversing that order produces valid schema on pages nobody sees.

The habit worth building: look at the results page before you write the page, not after it publishes. Two minutes spent on what already occupies the top of a SERP tells you what format the answer needs to take, whether a feature is already absorbing the click, and whether the query is worth the effort at all. Most content brief templates skip this entirely.

This week: open Search Console, go to the performance report, and click the Search appearance tab. You will find out which features your site already earns without anyone having planned for them, and that list is usually the fastest guide to which ones are realistically within reach.