Bing Scraper - Search Results & SERP Data

Bing Search Results Scraper

Extract Bing search results into structured data for keyword research, SEO monitoring, and competitor analysis. Submit search terms or Bing search URLs and choose your market, language, and page limits.

What you can extract

• Organic result titles, links, and description snippets
• Search keyword and source search URL
• Displayed result count and page number when available
• Related searches and People Also Ask content when present
• Available news, image, video, and knowledge-card sections on the web search page

Additional search features depend on Bing's response and markup. They are not available for every query. This Actor reads web search pages; it does not run dedicated image, video, or news searches, and does not extract paid advertisements.

How to scrape Bing search results

1. Enter search terms or full Bing web search URLs in queries.
2. Choose marketCode and optionally languageCode.
3. Set resultsPerPage and maxPagesPerQuery.
4. Keep direct access enabled by leaving platform proxies off, or configure your own proxies through proxyConfiguration.
5. Run the Actor and inspect or download the dataset.

Example input

{
  "queries": ["Apify web scraping"],
  "marketCode": "en-US",
  "languageCode": "en",
  "resultsPerPage": 10,
  "maxPagesPerQuery": 1,
  "maxConcurrency": 1,
  "csvFriendliness": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Direct access is the tested default on Bytewells. Custom proxy URLs can also be supplied. During migration testing, the platform-proxy route returned unrelated results for some queries while direct access returned relevant results. Verify query relevance before enabling platform proxies. Proxy location and Bing availability can affect results.

Choose your output format

Full search-page records

With csvFriendliness: false, each dataset record represents one fetched search page. Organic results are nested in pages, using title, link, and desc. Other available search sections are stored separately.

A dataset containing one record may therefore contain several organic results. Inspect the nested pages array or download JSON to see them all.

One organic result per row

Set csvFriendliness: true to save organic results as individual rows, each containing title, link, desc, and available search-page context. Additional rich search sections are omitted in this mode.

Common use cases

• Collect Bing results for keyword and content research.
• Compare which websites appear for a set of search terms.
• Monitor search results over time through repeated runs.
• Research related searches and available question sections.
• Compare results across selected markets and languages.

Limits and availability

• Bing controls how many organic results it returns; a requested count is not guaranteed.
• Search results vary by market, language, proxy location, and time.
• Start with maxPagesPerQuery: 1. In migration testing, Bing sometimes repeated page 1 for later-page requests. Detected first-page repeats are rejected rather than saved as valid pagination; multi-page completeness is not verified.
• Rich sections may be empty when Bing does not return supported markup.
• Blocked pages and request failures may produce a failed run with partial data.
• The Actor does not bypass login requirements or CAPTCHA challenges.
• This is an independent tool and is not affiliated with Microsoft or Bing.

Pricing

The monthly rental covers access to the Actor. Bytewells bills compute separately. Check applicable proxy charges before running large query batches.

Support

Provide the run ID, search query, market, and input settings with credentials removed. Explain which result fields or search pages were missing.