Bing SERP & Search Results Scraper

Export ranked Bing organic search results from keywords or direct Bing SERP URLs.

Use this actor when you need a repeatable CSV, JSON, Excel, or API export of Bing result pages for SEO research, market monitoring, competitive tracking, lead discovery, or search-data pipelines.

At a glance

• Input: Bing search queries or direct Bing search URLs.
• Output: Ranked organic results with title, URL, snippet, display URL, cached URL, sitelinks, related searches, market, language, and scrape time.
• Localization: Set Bing market, language, and SafeSearch.
• Best for: Bing SERP exports, keyword monitoring, search result audits, and API workflows.
• Proxy optional: Start without proxy for low-cost tests; enable Apify Proxy only if Bing throttles direct requests.

What can it do?

• Export Bing search results: Save organic ranks, titles, links, snippets, and display URLs.
• Track keyword positions: Collect repeatable ranked result rows for the same query over time.
• Research related searches: Capture Bing related-search suggestions when available.
• Use direct SERP URLs: Run from an existing Bing URL when you already have query parameters.
• Use as a Bing Search API alternative: Run from the Apify UI, API, schedules, webhooks, or the official Apify MCP server.

Common workflows

• SEO monitoring: Track where domains, competitors, and articles appear in Bing search results.
• Market research: Export result pages for categories, vendors, products, or regional searches.
• Lead discovery: Find public websites ranking for a topic and enrich them downstream.
• SERP archiving: Keep dated snapshots of result titles, snippets, and URLs.
• Automation: Feed ranked results into spreadsheets, dashboards, or a custom database.

Input example

{
  "queries": ["apify web scraping", "open source crawlee"],
  "maxResultsPerQuery": 10,
  "market": "en-US",
  "language": "en",
  "safeSearch": "Moderate",
  "includeRelatedSearches": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output example

{
  "query": "apify web scraping",
  "position": 1,
  "page": 1,
  "title": "Apify: Full-stack web scraping and browser automation platform",
  "url": "https://apify.com/",
  "displayUrl": "apify.com",
  "snippet": "Apify is a cloud platform for web scraping...",
  "cachedUrl": null,
  "sitelinks": [],
  "relatedSearches": ["apify actors", "crawlee"],
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

Tips for best results

• Start with maxResultsPerQuery set to 10-20 before scaling to larger exports.
• Use startUrls only when you need exact Bing URL parameters; otherwise queries is cleaner.
• Keep includeRelatedSearches on for keyword research and off only if you want smaller rows.
• If Bing throttles direct requests, enable Apify Proxy and retry with a smaller concurrency pattern.

Limits and caveats

• This actor extracts organic Bing results. It does not promise paid ads, shopping modules, maps modules, or every rich SERP element.
• Bing can personalize, localize, or test result pages, so repeated runs may differ.
• Some result pages omit sitelinks, cached URLs, or related searches.
• Respect Bing's terms and applicable laws when using exported data.

API usage

curl "https://api.apify.com/v2/acts/fetch_cat~bing-search-results-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "queries": ["apify web scraping"],
    "maxResultsPerQuery": 10,
    "market": "en-US"
  }'

MCP and AI agents

You can run this actor through the official Apify MCP server at https://mcp.apify.com.

For a focused single-actor tool, use:

https://mcp.apify.com?tools=fetch_cat/bing-search-results-scraper

Agent-friendly inputs are queries, startUrls, maxResultsPerQuery, market, language, safeSearch, includeRelatedSearches, and proxyConfiguration.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.