SERP

also known as: search engine results page

The page a search engine actually renders for a query, organic results, and increasingly, AI-generated modules sitting above or inside them. Once AI Overviews and AI Mode became part of the page, "the SERP" stopped meaning just ranked links; it is now the whole rendered surface an answer engine or organic result competes for.

In AI Search API

google_search captures the real, rendered results page browser-first and returns it as the same Envelope contract as every AI-surface capture: any answer-bearing module normalized into the answer (answer.text/markdown), and, when you opt in with include.html, the whole rendered page returned as a proof-of-page HTML snapshot (a top-level html URL, fetchable at GET /v1/artifacts). That shared contract is the point: whether the AI Overview above the organic results names you, or does not, is captured through the same parser as every AI surface. google_search and google_ai_overview are deliberately separate surfaces requested together on the same query, so the control group (the classic SERP) and the AI layer above it are never conflated into one ambiguous result.

Envelope excerpt, the SERP capture
"answer": { "text": "…", "markdown": "…" },
"html":   "/v1/artifacts/…"  // opt-in via include.html

Related terms

See it in the product

Every definition here is enforced in the Envelope contract. Run a capture and read the fields yourself.