SERP Features: understanding modern Google results

Quick Definition

SERP features are special elements on a Search Engine Results Page. A classic organic result has a title link, visible URL, snippet and sometimes sitelinks. SERP features add richer formats: a featured snippet may answer a question directly, People Also Ask opens follow-up questions, an image pack highlights visual results, a video result points to playable or linked video content, a local pack shows nearby businesses, and rich results can display product, event, recipe, review or breadcrumb information.

The useful way to think about SERP features is not "how do we force Google to show this box?" but "what answer format does this search deserve?" Google has to understand the intent, your page has to provide a suitable format, and Google's systems have to decide that the feature helps users in that moment. That makes SERP-feature work a blend of search observation, editorial quality, technical clarity and honest expectations.

Terms Covered Here

• Universal Search and modern SERP layouts
• Featured snippet
• People Also Ask
• Knowledge panel and Knowledge Graph
• AI Overviews and AI Mode
• Image pack and image results
• Video carousel and video results
• Sitelinks and breadcrumb rich result
• Product, recipe, job posting, event and review snippet
• FAQ rich result and How-To rich result as changed or removed Google appearances
• Top Stories, Preferred Sources and news visibility
• Shopping results, Local Pack and Map Pack
• Perspectives and exploratory features
• Measurement in Search Console and SERP tracking

Simple Explanation

A modern search results page is closer to an answer screen than a plain list of links. Search for a running shoe comparison and Google may show shopping units, reviews, images, videos, organic guides and related questions. Search for a tax advisor near you and the local pack becomes central. Search for a definition and a featured snippet may appear. Search for a concert, job, recipe or product and structured data can help Google understand the page type more precisely.

So the same site might appear as a normal text result for one query, as a video candidate for another, as a local entity for a third, and as a rich result for a transactional query. The trick is not to chase every possible element. The trick is to notice which format the searcher probably needs and make the page genuinely good at that format.

SERP Features Are Dynamic, Not Fixed

Google's own visual element documentation makes one point especially important: search result elements can vary by device, country, language, query and many other factors. That means a SERP-feature strategy cannot be built from a static checklist alone. It needs live SERP observation. For each keyword cluster, look at a group of related queries. Are image results common? Are local results dominant? Does Google show Top Stories? Is there a short answer box? Are AI Overviews appearing? Are shopping units pushing organic results down?

This is not just reporting. It changes the content plan. If a query is image-heavy, a text-only article is underprepared. If People Also Ask dominates, the page should answer adjacent questions cleanly. If the local pack owns the top of the page, a generic national landing page will struggle. If product results dominate, product data and offer quality matter more than another general paragraph.

Answer Features: Featured Snippets, People Also Ask and AI Overviews

Featured snippets are compact answers selected from web pages. They often appear for definitions, steps, comparisons, lists and direct informational questions. Good pages for featured-snippet eligibility do not hide the answer. They give a concise answer near the relevant heading, then expand with examples, nuance and next steps. A table helps when the query asks for comparison. A list helps when sequence or options matter. A paragraph helps when the user needs a definition.

People Also Ask is different because it exposes the searcher's next questions. For content planning, this is extremely useful. Not every question deserves a separate URL, but important questions deserve clear answers. A strong glossary entry can start with a plain-language definition, then answer the natural follow-ups without turning into a robotic FAQ dump.

AI Overviews and AI Mode add another layer to the SERP. Google says the same foundational SEO best practices remain relevant for AI features and that there are no special extra requirements to appear as a supporting link. In practical terms, the basics still matter: the page must be crawlable, indexable, eligible for snippets, genuinely useful, and written in a way that makes entities, claims, sections and evidence easy to understand.

Knowledge Features: Knowledge Graph, Panels and Entities

Knowledge panels and related knowledge features are entity-driven. An entity is an identifiable thing: a brand, person, organization, place, product or concept. This matters because search engines are not only matching strings. They try to understand what a thing is, how it connects to other things, and which sources confirm that understanding.

For SEO teams, the practical work is consistency. Use names consistently. Connect related pages with meaningful internal links. Make organization, author, product and local business information clear. Use structured data truthfully where it fits. Keep external profiles aligned. You usually cannot directly command a knowledge panel, but you can reduce ambiguity around the entity.

Media Features: Image Packs and Video Results

Image packs appear when visual information helps the user. This includes ecommerce, travel and design, but also screenshots, diagrams, charts, workflows and examples. Image SEO starts before alt text. Ask whether the image actually makes the page easier to understand. Then handle filename, surrounding copy, alt text, dimensions, compression, lazy loading, image quality and, when useful, image sitemaps.

Video results work the same way. Google needs a page it can access, a video that is clearly embedded or referenced, useful metadata, a good thumbnail and enough page context to understand the video. Video is strongest when the query needs demonstration: how a tool works, how a process looks, how options compare, or how a concept unfolds over time. A video does not rescue weak content, but it can make a strong page more complete.

Navigation Features: Sitelinks and Breadcrumbs

Sitelinks are extra links shown under a result. They help searchers jump to important parts of a site. Google chooses them algorithmically. You cannot force exact sitelinks, but you can help by maintaining clear navigation, descriptive titles, consistent internal links and a logical information architecture.

Breadcrumbs are more controllable. Breadcrumb structured data can describe the page's place in the site hierarchy and improve how the path is represented in search. The distinction matters: breadcrumbs are a technical and IA hygiene task; sitelinks are more of an interpretation outcome. The old sitelinks search box is also no longer an active Google Search target, because Google removed the documentation after the feature became unavailable in results.

Rich Results: Structured Data With Expectations

Many rich results rely on structured data. Product markup can describe price, availability, ratings and product identity. Recipe markup fits real recipes with ingredients, instructions, images and cooking details. JobPosting describes jobs. Event markup describes events. Review snippets can display rating information when the guidelines are met. Breadcrumb markup clarifies site structure.

But valid structured data is not a display guarantee. It is eligibility and clarity. Google may show a feature, not show it, show it only for some queries, or change how it appears. A professional rich-result plan therefore treats markup as data quality work. Does the visible page match the markup? Are prices current? Are reviews real and visible? Is the page actually a product, job, recipe or event? If the answer is weak, the markup is not an advantage; it is a liability.

Changed Features: FAQ, HowTo and Old Playbooks

SERP-feature SEO ages quickly. FAQ rich results were once a common target because many pages could add FAQPage markup. Google has now documented that FAQ rich results no longer appear in Google Search. HowTo rich results are also no longer a current Google Search lever; the documentation was removed after the result type stopped being shown. The same applies to the sitelinks search box as a feature target.

This does not mean questions, answers or step-by-step guidance are useless. It means they should be written for users, internal search, clarity and conversion, not sold as guaranteed Google decorations. The mature question is: does this element still exist, in this market, for this query type, under current guidelines? If not, keep the content value and drop the outdated promise.

News, Commerce, Local and Perspectives

Top Stories matters for publishers and news-oriented searches. Eligibility depends on news quality, freshness, technical accessibility, publication signals, author clarity and sometimes user-selected Preferred Sources. Shopping results are more commerce-driven: product data, merchant feeds, structured data, price, availability and offer quality work together.

The Local Pack, also called the Map Pack, is central for local intent. It depends on more than the website. Business profiles, proximity, relevance, reviews, categories, location consistency and local landing-page quality all interact. A strong local page should feel useful to someone choosing a provider now: services, service area, proof, photos, reviews, opening hours, contact options and local context.

Perspectives and exploratory features show that Google sometimes wants multiple viewpoints rather than one neat answer. For brands, this is not a switch to flip. It is a reminder that real experience, author voice, examples, discussion and clear positions can matter more than interchangeable summaries.

A Practical SERP-Feature Workflow

Start with SERP observation by keyword cluster. Look at related queries, not just one head term. Note recurring features, dominant sources, content formats and the amount of screen space taken by each element. Then classify the intent: answer, comparison, local, visual, transactional, news, product, event or exploration.

Next, map the page to that intent. Is the definition clear? Are the images original and helpful? Is there a video only where demonstration helps? Does the structured data describe visible content? Are local proof points present? Are the internal links guiding the reader to deeper topics?

Then prioritize. A local pack opportunity may be worth more than a small review snippet. A featured snippet may be more important for a glossary than a video result. Product visibility may matter more for a shop than another editorial paragraph. Finally, measure with a mix of Search Console, SERP tracking, screenshots, impressions, clicks, CTR changes and qualitative review. No single metric captures the whole SERP.

Typical Mistakes

The first mistake is feature-first thinking: "we want a rich result" instead of "what search task can we solve better?" The second is misleading markup. Structured data must match what users can see. The third is outdated playbook work, especially around FAQ, HowTo and the sitelinks search box. The fourth is ignoring media quality while hoping for image or video visibility. The fifth is measuring only rank and missing the layout changes that explain traffic movement.

Contextter Perspective

For Contextter, a SERP feature is a briefing signal. If the SERP shows many questions, the content plan needs clean answers. If images dominate, visual assets belong in the brief. If local packs appear, generic copy is not enough. If AI Overviews are possible, the page needs especially clear entities, evidence, sections and internal links.

That is the practical value: teams stop writing longer pages by default and start building better-fit pages. Good SERP-feature work is not decoration. It is the discipline of matching search intent, answer format, page structure and technical implementation so users and search systems can understand the page faster.

Sources and Further Documentation

• Google Search Central: Visual Elements Gallery - https://developers.google.com/search/docs/appearance/visual-elements-gallery
• Google Search Central: AI Features and your website - https://developers.google.com/search/docs/appearance/ai-features
• Google Search Central: Featured Snippets - https://developers.google.com/search/docs/appearance/featured-snippets
• Google Search Central: Structured Data Search Gallery - https://developers.google.com/search/docs/appearance/structured-data/search-gallery
• Google Search Central: Image SEO - https://developers.google.com/search/docs/appearance/google-images
• Google Search Central: Video SEO - https://developers.google.com/search/docs/appearance/video
• Google Search Central: Product structured data - https://developers.google.com/search/docs/appearance/structured-data/product
• Google Search Central: Recipe structured data - https://developers.google.com/search/docs/appearance/structured-data/recipe
• Google Search Central: Job Posting structured data - https://developers.google.com/search/docs/appearance/structured-data/job-posting
• Google Search Central: Event structured data - https://developers.google.com/search/docs/appearance/structured-data/event
• Google Search Central: Review Snippet structured data - https://developers.google.com/search/docs/appearance/structured-data/review-snippet
• Google Search Central: Breadcrumb structured data - https://developers.google.com/search/docs/appearance/structured-data/breadcrumb
• Google Search Central: Local Business structured data - https://developers.google.com/search/docs/appearance/structured-data/local-business
• Google Search Central: Article structured data - https://developers.google.com/search/docs/appearance/structured-data/article
• Google Search Central: Preferred Sources - https://developers.google.com/search/docs/appearance/preferred-sources
• Google Search documentation updates: FAQ Rich Result, HowTo and Sitelinks Search Box changes - https://developers.google.com/search/updates#removing-faq-rich-result, https://developers.google.com/search/updates#how-to-deprecation, https://developers.google.com/search/updates#bye-sitelinkbox