Brave Search API

More Search API pages

API glossary

Search engine results page (SERP)

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

A search engine results page (SERP) is the page a search engine returns in response to a query. On modern search engines, it is usually a blend of elements rather than a simple list: ranked organic (unpaid) links, paid ads, and SERP features such as featured snippets or knowledge panels that answer parts of the query directly. On some queries and engines, AI-generated overviews may also appear, often near the top of the page.

In short: a SERP is what you see after you search, meaning the mix of links, ads, and answer features a search engine returns for your query.

How a SERP is built

A SERP is assembled on the fly from an index:

  1. Crawling and indexing: Search engines use crawlers to discover pages and build an index of web content.
  2. Ranking: When a query arrives, the engine scores and orders indexed pages by relevance to produce the core list of organic results.
  3. Assembling features: Alongside organic links, the engine may add features such as ads, knowledge panels drawn from a knowledge graph, featured snippets, “People Also Ask” boxes, images, or location-specific widgets.
  4. Optional AI layers and modes: Some products add AI overviews for certain queries or offer a conversational AI Mode as an alternative interface.
  5. Render: The engine lays out all selected modules into the page the user sees, influenced by factors such as location, device, and query intent.

The key shift is that a SERP is no longer only a ranked list of links; it is increasingly an interface that can blend links with direct answers.

SERP vs. search API responses and answer engines

  • Organic results are the ranked, unpaid links a SERP returns; SERP features such as snippets, knowledge panels, and AI overviews are additional modules layered around them.
  • Rendered SERP is an HTML page built for people to read; a search API returns overlapping core result types as structured data (JSON) for software to consume directly, without parsing HTML. API output may not map one-to-one to every on-page module, ad unit, or personalization treatment in a rendered SERP.
    • Note: This is often the difference between using a scraper vs. a search API powered by its own index. While a capable scraper can extract structured data when a page already exposes that data, the scraper can still be limited to a point-in-time snapshot of one page. By contrast, an API backed by its own index can enrich those results with signals and metadata gathered across the Web over time, yielding richer, more consistent output for agents and chatbots.
  • Traditional SERP gives users a set of sources to choose from; an answer engine composes a direct answer, and AI overviews can blur the line by doing both on one surface.

Where the SERP matters

  • SEO and AEO: Ranking on the SERP and appearing in its features is central to search optimization, and as AI features expand, answer engine optimization (AEO) focuses on being cited in AI-generated summaries.
  • Zero-click search: Because SERP features and AI overviews can answer queries directly on the results page, many searches may end without a click through to the source website, shifting value from traffic to visibility.
  • Programmatic access: Developers who need results data use a programmable search engine or search API to fetch structured results instead of scraping the rendered page. These result types are often exposed as separate API endpoints (for example, “News” or “Images”).
  • RAG and AI answer engines: Structured SERP-derived results often serve as the retrieval layer for RAG, providing grounding context for LLM responses.

The SERP matters because it is where search visibility is won or lost, and as it evolves from a link list into an answer surface, clean programmatic access to result data becomes increasingly important.

Organic results, SERP features, featured snippet, knowledge graph, AI web crawler, crawl budget, programmable search engine, search API, answer engine optimization (AEO), retrieval-augmented generation (RAG).