SERP tracking
Use Yahoo Search endpoints to turn serp tracking into repeatable API requests with documented inputs and JSON responses.
Turn Yahoo's public web, image, video, news, and local search results into structured JSON — organic results, autocomplete suggestions, and a recency filter, for SERP tracking and web-discovery workflows. Credential-free.
Search Yahoo web, image, video, news, and local results, plus autocomplete suggestions, as structured JSON.
Endpoint families
6
Documented params
15
Examples
6
Live catalog snapshot
Active endpoints
6
Methods
GET
Required params
12
Schema refs
6
{
"platform": "Yahoo Search",
"endpoint": "yahoo-search",
"method": "GET",
"path": "/yahoo-search/search",
"auth": "apiKey"
}Use cases
Search Yahoo web, image, video, news, and local results, plus autocomplete suggestions, as structured JSON.
Use Yahoo Search endpoints to turn serp tracking into repeatable API requests with documented inputs and JSON responses.
Use Yahoo Search endpoints to turn search monitoring into repeatable API requests with documented inputs and JSON responses.
Use Yahoo Search endpoints to turn discovery workflows into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Yahoo Search endpoint catalog — 6 endpoints, 15 documented request parameters, and 6 published response schemas — the same catalog Docs and Playground run against.
6 documented Yahoo Search endpoints, grouped into 6 request families — Images, Local and News, plus 3 more.
15 request parameters are documented across those Yahoo Search endpoints, 12 of them required — the full input contract is public before you write any integration code.
6 of the 6 Yahoo Search endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Yahoo Search endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
6 hosted MCP tools back the Yahoo Search endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/yahoo-search/images
/yahoo-search/local
/yahoo-search/news
/yahoo-search/search
/yahoo-search/suggest
/yahoo-search/videos
Endpoint catalog
/yahoo-search/searchReturns normalized Yahoo web search results for a query string: title, destination URL, description, and hostname, plus page-based pagination. Yahoo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link. Results are fetched from Yahoo's own server-rendered search page.
Response notes
- Yahoo wraps every result link in its own click-tracking redirect (`r.search.yahoo.com/...`); `url` in the response is always the decoded destination URL, never the raw redirect link. - An unrecognized `time_range` value returns `400`, not a silent fallback to unfiltered results. - A blocked or CAPTCHA-served response returns `503`. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "openai", "results": [ { "position": 1, "title": "OpenAI | Research & Deployment", "url": "https://openai.com/", "description": "We believe our research will eventually lead to artificial general intelligence, a system that can solve human-level problems.", "hostname": "openai.com" } ], "pagination": { "page": 1, "next_page": 2 } } } ```
MCP tool yahoo_search
/yahoo-search/suggestReturns Yahoo's own search-box autocomplete suggestions for a partial query: a flat list of suggested search terms, each optionally carrying knowledge-panel entity metadata (type, image, subtitle, description) when Yahoo resolves the term to a known company, place, product, or similar entity rather than a plain phrase.
Response notes
- `entity` is omitted entirely for a plain phrase suggestion (not returned as an empty object). - A query with no matches returns a genuine empty `suggestions` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "openai", "suggestions": [ { "text": "OpenAI", "entity": { "type": "company", "image_url": "https://s.yimg.com/zb/imgv1/4101d01f-a338-3734-958b-9574654493d2/t_140x140", "description": "OpenAI is an American artificial intelligence research organization headquartered in San Francisco, consisting of OpenAI Group PBC, a for-profit public benefit corporation, partially controlled by OpenAI Foundation, a nonprofit." } }, { "text": "openai chat gpt" } ], "source_url": "https://search.yahoo.com/sugg/gossip/gossip-us-fastbreak?command=openai&nresults=10&output=sd1", "fetched_at": "2026-08-14T00:00:00Z" } } ```
MCP tool yahoo_search_suggest
/yahoo-search/imagesReturns Yahoo's image-search results for a query: title, direct image URL, the page hosting the image, source domain, thumbnail, and original image dimensions when available. Results are fetched from Yahoo's own server-rendered image-search page.
Response notes
- `image_url` is the direct image file Yahoo indexed; `page_url` is the web page that hosts it. These are always distinct upstream fields, never the same URL. - `width`/`height` are omitted when Yahoo did not carry the original image's dimensions for a given result. - A query with no matches returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "chatgpt", "results": [ { "position": 1, "title": "Chatgpt Cheat Sheet For Writing Prompts", "image_url": "https://gizmodo.com/app/uploads/2024/07/ChatGPT-Voice-Chat.jpeg", "page_url": "https://example.com/chatgpt-cheat-sheet", "domain": "example.com", "thumbnail_url": "https://tse4.mm.bing.net/th/id/OIP.example", "width": 1920, "height": 1080 } ] } } ```
MCP tool yahoo_search_images
/yahoo-search/videosReturns Yahoo's video-search results for a query: title, destination page URL, source domain, description, thumbnail, and duration. Results are fetched from Yahoo's own server-rendered video-search page.
Response notes
- `url` is the real page hosting the video (e.g. a youtube.com watch link), not an embeddable player URL. - `domain` is the source site name as Yahoo labels it (e.g. "YouTube"). - `duration` is omitted when Yahoo did not carry a duration badge for a given result. - A query with no matches returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "chatgpt", "results": [ { "position": 1, "title": "You can just launch Sites | ChatGPT Work", "url": "https://www.youtube.com/watch?v=6VwIXjFj6YQ", "domain": "YouTube", "description": "ChatGPT Work gathers context across your surfaces.", "thumbnail_url": "https://tse2.mm.bing.net/th?id=OVF.example", "duration": "00:29" } ] } } ```
MCP tool yahoo_search_videos
/yahoo-search/newsReturns Yahoo's news-search results for a query: title, destination URL, description, source, and relative publish age. Results are fetched from Yahoo's own server-rendered news-search page (news.search.yahoo.com) -- a distinct product from the yahoo-news family, which covers the www.yahoo.com/news portal itself. Yahoo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link.
Response notes
- Yahoo wraps every result link in its own click-tracking redirect (`r.search.yahoo.com/...`); `url` in the response is always the decoded destination URL, never the raw redirect link. - A query with no matches returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "chatgpt", "results": [ { "position": 1, "title": "I Asked ChatGPT How To Retire Early at 55", "url": "https://www.aol.com/articles/asked-chatgpt-retire-early-55.html", "description": "I asked ChatGPT how to retire at 55. The roadmap it built was mostly right.", "source": "MoneyLion", "age": "29 minutes ago", "thumbnail_url": "https://s.yimg.com/fz/api/res/example.jpg" } ] } } ```
MCP tool yahoo_search_news
/yahoo-search/localReturns Yahoo's local-business-search results for a query: name, category, price range, address, phone, open status, rating, and review count. Location is resolved from the query text itself, the same way a user would type into Yahoo's own local search box (e.g. "pizza near seattle wa"), not a separate coordinate parameter. Results are fetched from Yahoo's own server-rendered local-search page.
Response notes
- `id` is Yahoo's own internal listing id, carried in case a caller wants to distinguish repeat listings. Yahoo's list view does not link out to the business's own website -- there is no `url` field. - `rating` is a 0-5 integer star count (Yahoo's own list view does not expose a finer-grained decimal rating). - A query with no local-business intent (or no matches) returns a genuine empty `results` array, not an error. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "pizza near seattle wa", "results": [ { "position": 1, "id": "36383310", "name": "Serious Pie Downtown", "category": "Pizza", "price_range": "$$", "address": "2001 4th Ave", "phone": "(206) 838-7388", "open_status": "Closed", "rating": 4, "review_count": 4870, "image_url": "https://s.yimg.com/fz/api/res/example.jpg" } ] } } ```
MCP tool yahoo_search_local
Related APIs
Search & Web Discovery
Extract Google search results, organic rankings, result URLs, titles, snippets, and related queries as structured JSON for SERP monitoring, rank tracking, and search visibility workflows.
Search & Web Discovery
Use a Google Trends API — an API for Google Trends data — to track search demand, trending terms, interest over time, regional interest, related and rising queries, plus Google Suggest discovery, as structured JSON for demand research and trend monitoring.
Search & Web Discovery
Extract Google News results — headlines, source names, article URLs, snippets, thumbnails, and recency — as structured JSON for media monitoring, brand mention tracking, and news aggregation workflows.
How to scrape Yahoo Search
Yahoo shut down its BOSS search API years ago and has no public replacement, yet Yahoo results still differ from Google's and matter in a few markets. The Yahoo Search API turns Yahoo's public web, image, video, news, and local search results into structured JSON, plus search-box autocomplete suggestions — no credentials required.
Pass q with the search terms; page and time_range (day/week/month) refine the web search endpoint's result set.
Each organic result comes back with its title, destination URL, description, and hostname; the image/video/news/local endpoints return the same field shape for their own verticals.
Yahoo wraps every result link in its own click-tracking redirect. This endpoint always returns the decoded destination URL, never the raw redirect, so rank tracking joins cleanly against your own domains.
Send a partial query to /yahoo-search/suggest to get the same search-box suggestions Yahoo's own UI shows, including entity metadata for recognized companies, places, and products.
Run the same query on a schedule and diff the result set to monitor position changes, new entrants, and lost placements.
FAQ
No. Yahoo shut down its BOSS search API and has published no public replacement. Crawlora's endpoints read Yahoo's own server-rendered search pages and JSON suggestion service, returning normalized JSON.
The real one. Yahoo wraps every result link in a click-tracking redirect; these endpoints decode it and return the destination URL, which is what makes rank tracking against your own domains work at all.
The page parameter walks Yahoo's result pages — there is no cursor, and page numbers map to the same pagination Yahoo's own interface uses.
Yes — pass time_range=day, week, or month to /yahoo-search/search to match Yahoo's own "Anytime/Past day/Past week/Past month" filter.
Yes — /yahoo-search/images, /yahoo-search/videos, /yahoo-search/news, and /yahoo-search/local cover each of those verticals as structured JSON, the same as the main web search endpoint.
Send a keyword as q to Crawlora's /yahoo-search/search endpoint and get normalized organic results as structured JSON — no Yahoo account required.