Retrieve page content
Add You.com to your agent or IDE via MCP—every API in these docs is available on https://api.you.com/mcp (new accounts get $100 in free credits), and Search is free to try via https://api.you.com/mcp?profile=free, no signup required. MCP Server guide →
Overview
By default, search results include snippets—100–200 words of extracted text per result. Pass the extraction parameter to ask for richer content: full-page Markdown and HTML, or query-relevant highlights.
This unlocks:
- Deep RAG with full document context
- Knowledge base construction from live web data
- Comprehensive content synthesis across sources
- Full article bodies for news results
Two modes are available. Pick the one that matches the latency and token budget of your pipeline.
If you want query-ranked excerpts rather than whole pages, use extraction_mode: "highlights". The two modes are mutually exclusive—pick one per request.
How It Works
Add the extraction object to a POST /v1/search request. The API fetches each result in real time and attaches a contents object to it. The crawl_timeout parameter is a sibling of extraction at the top level of the request body.
When extraction_mode: "highlights", the server rejects crawl_timeout (it only applies to full_page). The Python SDK strips it automatically with a warning before the request goes out, so you can ignore the constraint unless you call the API directly.
Full-page extraction crawls every web and news result in the response. There is no per-section switch. Control the volume with count. With the default count=10, a call returns up to 10 web + 10 news pages.
markdown is recommended for LLM use cases—it strips navigation, ads, and boilerplate HTML, leaving only the core content.
highlights and full_page are two ways to attach content to search results. Use highlights when tokens are tight. Use full_page when you need whole documents.
Get Highlights
Set extraction_mode to highlights. Each result gains a contents.highlights array of query-relevant excerpts. Snippets are omitted in this mode—the search returns the ranked highlights instead.
Get Full Page Content
Set extraction_mode to full_page. Each successfully crawled result gains a contents.markdown (or contents.html) field.
Full Article Bodies for News
Combine full-page extraction with freshness for breaking news pipelines. Web results are crawled in the same call, so read results.news if articles are all you need.
Get Both Markdown and HTML
Pass both formats in extraction_formats to receive contents.markdown and contents.html on every crawled result.
Control Crawl Timeout
By default the crawler waits up to 10 seconds per page. For latency-sensitive applications, reduce crawl_timeout. For complex or slow-loading pages, increase it (up to 60 seconds). crawl_timeout sits at the top level of the request, not inside extraction, and only applies when extraction_mode: "full_page". Combining it with highlights is invalid.
HTML vs Markdown
Highlights or Full Page?
A few rules of thumb:
- You want fast, citation-anchored snippets. Use
highlightswith a moderatecount(10–25). Excerpts land incontents.highlights. - You need the document body to feed a downstream indexer or synthesizer. Use
full_pagewithextraction_formats: ["markdown"]. - You need rendered HTML for scraping or both formats in the same response. Use
full_pagewithextraction_formats: ["html", "markdown"]to receive bothcontents.markdownandcontents.htmlper result. - You already know the URLs. Use the Contents API directly. There is no need to search first.
Already Have URLs?
If you have a list of URLs and don’t need to search first, use the Contents API directly. It accepts URLs without a query and returns the same markdown or html content.
Legacy: livecrawl
Before extraction, page content came from the livecrawl parameter. It still works on both GET and POST /v1/search, so existing integrations keep running. It is deprecated and no longer developed. extraction covers the same job and adds query-relevant highlights, so new integrations should use it.
Moving off livecrawl on POST /v1/search:
extraction is available on POST /v1/search only. GET /v1/search keeps livecrawl for backward compatibility but receives no new features.