Bing Search Scraper

Bing Search Scraper is an Apify Actor for capturing Bing.com search results from a query or a direct Bing search URL. It accepts free-text queries or full https://www.bing.com/search?q=... URLs, and it returns one record per SERP item in the default dataset. Each record can include the fields that matter for search analysis and agent workflows: query, position, type, title, url, displayUrl, snippet, date, sitelinks, sources, marketCode, scrapedAt, and source. The output is designed for downstream use in dashboards, SEO workflows, RAG pipelines, and AI agents.

Best fit and connected workflows

This Actor fits workflows that need Bing Web Search data in a structured, record-based format. It is a strong routing choice for:

• SEO research on Bing, including organic results and search features.
• Brand monitoring across Bing SERPs and Copilot answer blocks.
• Competitive research that benefits from ads, featured snippets, PAA questions, and related searches.
• AI agent workflows that need a Bing SERP tool through Apify MCP.

It supports localized extraction through country and language, and it can return multiple SERP block types in one run. When a direct Bing scrape produces zero records for a query, the Actor can use managed Bing fallback according to fallbackMode. Each emitted record carries a source value so you can trace whether it came from bing-direct or managed-fallback.

Input

Field	Type	Description
queries	array of strings	Free-text search queries or full Bing search URLs. Required.
country	string	Two-letter ISO country code used for geo-targeting and Bing market hint. Default: US.
language	string	Two-letter ISO language code used with country to form the Bing market code. Default: en.
safeSearch	string	Bing SafeSearch level: off, moderate, or strict. Default: moderate.
maxResultsPerQuery	integer	Hard cap on result records per query, across organic, ads, Copilot answer, PAA, and related searches. Range: 1-200. Default: 50.
includeAds	boolean	Include sponsored ads as type: ad. Default: true.
includeCopilotAnswer	boolean	Include the Microsoft Copilot AI answer block as type: copilot_answer. Default: true.
includeRelatedSearches	boolean	Include PAA questions and related searches as type: paa or type: related. Default: true.
fallbackMode	string	Managed Bing fallback mode: auto, always, or never. Default: auto.
proxyConfiguration	object	Apify Proxy configuration. Default uses residential proxies.

Focused input example

{
  "queries": [
    "suitable crm software 2026",
    "https://www.bing.com/search?q=apify+web+scraping"
  ],
  "country": "US",
  "language": "en",
  "safeSearch": "moderate",
  "maxResultsPerQuery": 30,
  "includeAds": true,
  "includeCopilotAnswer": true,
  "includeRelatedSearches": true,
  "fallbackMode": "auto"
}

Output

The Actor stores all scraped SERP records in the default dataset. Each record follows the dataset contract below.

Field	Type	Description
query	string	Original search query string.
position	integer	1-based position within the record type group.
type	string	Record type: organic, ad, copilot_answer, featured_snippet, paa, related, or sitelink.
title	string or null	Result title, question, or heading.
url	string or null	Destination URL, cleaned where possible.
displayUrl	string or null	Breadcrumb-style URL shown by Bing.
snippet	string or null	Snippet, description, or answer text.
date	string or null	Raw date string when Bing surfaces one.
sitelinks	array	Sitelinks under an organic result.
sources	array	Citation URLs for Copilot answer records.
marketCode	string	Bing market code such as en-US.
scrapedAt	string	ISO timestamp of extraction.
source	string	bing-direct or managed-fallback.

Illustrative output record

{
  "query": "suitable crm software 2026",
  "position": 1,
  "type": "organic",
  "title": "Example CRM result title",
  "url": "https://example.com/crm",
  "displayUrl": "example.com",
  "snippet": "Example snippet text from the Bing result.",
  "date": null,
  "sitelinks": [
    {
      "title": "Pricing",
      "url": "https://example.com/crm/pricing"
    }
  ],
  "sources": [],
  "marketCode": "en-US",
  "scrapedAt": "2026-06-13T14:22:31.812Z",
  "source": "bing-direct"
}

How it works

This Actor scrapes Bing.com SERP pages and emits structured records for the supported result blocks. The current contract shows direct Bing extraction plus managed Bing fallback for queries that return zero records or for runs configured to use fallback more broadly.

Implementation facts visible in the live contract and schema:

• It uses Apify residential proxy by default.
• It supports multi-market extraction through country and language.
• It emits a flat dataset with one record per SERP item.
• It distinguishes record types with the type field.
• It adds a source field so you can tell direct Bing records from managed-fallback records.

Pricing

This Actor uses Pay per event pricing, plus Apify platform usage. Review the live Pricing tab for the current billing details.

The charged events are:

• actor-start: charged once per run.
• result-extracted: charged per SERP record emitted from the direct Bing.com scrape.
• managed-fallback-result: charged per record when managed Bing fallback is used.

For example, if you run 10 queries and each query produces 30 records, the run emits 300 result events, plus one actor start event. That is the basic event-count model to use when estimating cost. If fallback records are emitted through the managed Bing path, those records use the managed fallback event instead.

Use with AI agents (MCP)

This Apify Actor is usable through Apify MCP as khadinakbar/bing-search-scraper. The tool returns Bing SERP records that an agent can read, compare, and summarize with the dataset fields above. Because the output is normalized, an agent can inspect result types, source provenance, market code, and sitelinks without extra parsing.

Use khadinakbar/bing-search-scraper to scrape Bing for "suitable crm software 2026" in the US market with Copilot answer, ads, and related searches enabled. Return the dataset items and summarize the top organic results by title, URL, and snippet.

Output interpretation guidance:

• type separates organic results from ads, Copilot answers, featured snippets, PAA, related searches, and sitelinks.
• source shows whether the record came from direct Bing scraping or managed Bing fallback.
• marketCode identifies the market context used for the query.
• sources is relevant for Copilot answer records and contains citation URLs.
• Pagination is controlled by maxResultsPerQuery, which sets a hard cap on emitted records per query.

Cost guidance when using agents:

• Each extracted record is a billable event.
• A higher maxResultsPerQuery can increase the number of emitted records for a query.
• Managed Bing fallback uses a separate event title and rate from direct extraction.

Apify API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const run = await client.actor('khadinakbar/bing-search-scraper').call({
  queries: ['suitable crm software 2026'],
  country: 'US',
  language: 'en',
  safeSearch: 'moderate',
  maxResultsPerQuery: 10,
  includeAds: true,
  includeCopilotAnswer: true,
  includeRelatedSearches: true,
  fallbackMode: 'auto',
});

const items = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.items);

Best results and outcome guidance

Use a query list that matches the SERP question you want to study. If you want only organic results, you can keep the feature flags enabled and filter by type in the dataset. If you want market-specific results, set both country and language so the Actor can build the relevant Bing market code. If you are comparing direct Bing extraction and fallback behavior, inspect the source field alongside type.

Continue the workflow

• Then use Localized Bing Organic Rank Tracker for Domains to extend Bing Search Scraper research with a complementary monitor contract.
• Then use Broken Link Checker for SEO Website Audits to extend Bing Search Scraper with a neighboring search visibility work source when the brief calls for Broken data.

Design note

I found that the dataset contract includes a dedicated source field with two explicit values, bing-direct and managed-fallback, which makes provenance visible in every record.

FAQ

Can this Actor return Bing ads and answer blocks together?

Yes. Set includeAds and includeCopilotAnswer to true, and the dataset can include ad records and the Copilot answer record alongside organic results.

Can I pass a Bing search URL instead of a plain query?

Yes. The queries input accepts free-text search queries or full Bing search URLs.

How do I get localized Bing results?

Set country and language. The Actor combines them into the Bing market code used for extraction.

How do I separate organic results from PAA and related searches?

Use the type field. Organic results are labeled organic, while PAA and related search suggestions are labeled paa and related.

How do I know whether a record came from direct Bing or fallback?

Check the source field in the dataset output.

Responsible use

This Actor extracts publicly accessible Bing search results. Use it in ways that align with applicable Bing terms, proxy rules, copyright requirements, and data-protection laws. Review and respect any obligations that apply to the content you collect and process.