SERP Features:
Types, Eligibility, and SEO

SERP features are the answer boxes, visual results, and listing enhancements on a search engine results page (SERP), including Google’s documented rich results, images, videos, and exploration features. Understanding each type helps identify which content, assets, or business information a search result requires.

This guide focuses on Google Search. Its results-page design varies with the query, device, country, language, and other factors, and changes over time. Record those conditions when assessing an observed appearance.

Common SERP features#

Product information and review ratings are among the supported rich-result presentations. Use both the visible appearance and its underlying data type when identifying a result.

SERP features, rich results, and rankings#

A standard text result contains a title link, snippet, and source information, and can include sitelinks or rich attributes, according to Google’s visual elements gallery.

Google selects featured snippets from website content, while its structured-data gallery explains the markup used for supported rich results. Adding structured data is therefore only one part of work on SERP features.

For SEO analysis, separate three questions: Does the feature appear for the query? Does it include the site’s content or information? Does that appearance produce useful visits? Recording each separately avoids treating a visible feature, an organic ranking, and a click as the same outcome.

How to optimize for SERP features#

Start by inspecting the searches the page needs to answer. Record the visible formats and the destinations they link to. Then choose the relevant work below: improve an answer, supply structured information, make a visual asset discoverable, or maintain business information.

Featured snippets and People Also Ask#

Google’s featured-snippet documentation states that publishers cannot mark a page as a featured snippet; its systems decide whether to select it for a search request.

Write a direct answer under a descriptive heading, then explain its conditions and supporting details. Use a paragraph for a definition, numbered steps for a procedure, or a table for a comparison when that format makes the answer easier to use. These are editorial recommendations, rather than documented selection requirements.

Avoid a fixed word-count target: Google does not specify an exact minimum length for featured snippets because the requirement varies with the content, language, and platform. Use related questions to identify gaps in an explanation, and keep each answer relevant to the page’s subject.

Rich results and structured data#

Choose a type from Google’s supported structured-data gallery that accurately describes the page. Follow that type’s guide rather than adding every available schema type.

Google’s general structured-data guidelines require information to represent the page’s content, remain current, and include the required properties for the selected feature. Hidden content, misleading information, and irrelevant markup can prevent eligibility. Google recommends JSON-LD and also supports Microdata and RDFa.

Use the Rich Results Test and URL Inspection tool to check technical issues. Treat validation as a technical check: Google does not guarantee display even when markup is correct, and some quality problems are not detectable by an automated tool.

Product and shopping results#

Google distinguishes product snippets from merchant listings: product snippets support pages such as editorial product reviews where the product cannot be purchased directly; merchant listings support pages where customers can buy it.

Select the appropriate implementation and maintain accurate product information, including applicable prices, availability, and policies. Google accepts product data through page markup, Merchant Center feeds, or both. Providing both helps Google understand and verify the data and broadens eligibility across shopping experiences.

Keep free product visibility and paid promotion separate in reporting. Google’s Search Network documentation identifies Shopping ads as advertising placements with labels such as Sponsored or Ad; a product appearing visually in search does not by itself establish that the placement is organic.

Images and videos#

For images, Google’s image SEO guidance recommends standard HTML image elements with a discoverable src URL, relevant surrounding text, and descriptive alt text; Google does not index CSS background images. Give the image a relevant landing page and balance image quality with loading performance.

For video, Google’s indexing requirements include an indexed watch page, an embedded video, and a valid thumbnail at a stable URL; a watch page’s main purpose is to show a single video (Indexing the page does not guarantee video indexing). Google also recommends video metadata through structured data, video sitemaps, or the Open Graph protocol.

Choose a visual format because it carries useful information. Before creating a new asset, identify what the image or recording needs to explain and where a searcher should land after opening the result.

Local results and knowledge panels#

For local visibility, Google recommends verifying the business and keeping its Business Profile complete and accurate. Maintain the business category, address where applicable, hours, and other customer-facing details. Google’s local-ranking guidance describes relevance, distance, and prominence, and says a business cannot request or pay for a better local ranking.

Knowledge panels follow a separate process. Google generates them automatically from multiple sources, including information across the web and, in some cases, data partners. The subject or an official representative can claim an existing panel and suggest changes. Google distinguishes Business Profiles, which can look similar but serve businesses with a customer location or service area.

AI Overviews and AI Mode#

Google’s AI-feature requirements say a page linked from AI Overviews or AI Mode must be indexed and eligible to appear in Google Search with a snippet; there are no additional technical requirements, special schema types, or new machine-readable files required for inclusion.

Follow the documented fundamentals: allow crawling, make important content available in text, and provide internal links. Keep structured data consistent with visible content. Google does not guarantee inclusion simply because a page meets the requirements.

Sitelinks and Top stories#

For sitelinks, Google’s documentation explains that selection is automated and recommends a logical site structure, links to important pages, concise anchor text, and informative titles and headings. Improve those elements without assuming that a particular link will be displayed.

For Top stories, publishers are automatically considered when they produce high-quality content and follow Google News policies. Google’s Article documentation says markup is not required for Top stories eligibility, although Article structured data can help Google understand article information such as titles, images, and dates.

How to track SERP features#

Use an observation record alongside search-performance data. The first records what a particular results page displayed; the second measures the site’s performance across searches.

1. Record the search conditions. Save the query, date, country, language, device, and a screenshot. Note which features appeared, which linked to the site, and the destination URLs. Repeat observations under comparable conditions instead of treating one search as a complete history.
2. Compare site performance. Google’s Search Console Performance report provides clicks, impressions, CTR, and average position, with dimensions for queries, pages, countries, devices, search appearance, and dates. Compare equivalent periods and apply the relevant filters before interpreting a change.
3. Use appearance filters with their limits. The Search appearance dimension groups supported result types, and its filter list includes only types for which the site has recorded impressions. Read these groups as property appearances, rather than an inventory of every feature on the SERP.

Pay attention to what each metric represents. CTR is clicks divided by impressions, while average position reflects the topmost result for the property or the grouping being measured. Neither metric alone identifies which feature caused a traffic change.

There are additional reporting limits. Google’s dimension documentation notes that some queries are anonymized and others may be omitted because of data limits. The same guidance warns that clicks under a Search appearance filter are assigned to a URL, so they are not guaranteed to have occurred on the link carrying that particular feature. Google reports AI Overviews and AI Mode traffic within the Web search type.

Treat a CTR change as a reason to investigate. Compare the saved results, the listing, the destination page, and any content or technical changes. Record the observed feature and the measured outcome separately; a before-and-after comparison alone does not establish that the feature caused the result.