Bing Search Results Scraper

Export Bing organic search results for SEO research, lead generation, competitor monitoring, and market analysis.

What does Bing Search Results Scraper do?

Bing Search Results Scraper turns public Bing search result pages into a structured SERP dataset for SEO, research, and monitoring workflows.

Capability	What it does
Search by query	Build Bing search URLs from one or more keywords.
Use existing URLs	Start from direct Bing result URLs when you need specific market or filter parameters.
Export organic results	Save rank, title, URL, display URL, snippet, sitelinks, related searches, and scrape timestamp.
Control locale	Set market, language, and SafeSearch values.
Stay honest	Does not access private Bing data, ads dashboards, signed-in results, or guaranteed personalized rankings.

Use it when you need repeatable Bing SERP exports without manually copying results from a browser. If your workflow needs Google SERP coverage instead of Bing coverage, use a Google-specific search actor so the source and ranking context stay explicit.

Who is it for?

Team	Use case
SEO teams	Track keyword positions and organic SERP changes on Bing.
Growth marketers	Research competitors, content gaps, and market terms.
Lead generation teams	Collect companies, directories, and niche prospects from search results.
PR and brand monitoring teams	Check what appears for names, products, campaigns, or reputation terms.
Data teams	Build search-result benchmarks for dashboards and recurring reports.

Why use this Bing scraper?

• Bing is still a meaningful discovery channel for many industries and regions.
• The output is clean enough for CSV, JSON, Excel, Google Sheets, dashboards, and databases.
• Query, position, page, and timestamp fields make repeated runs easy to compare.
• The first version focuses on reliable organic results and keeps the input simple.

What data can you extract?

Field	Description
query	Search query that produced the result
position	Organic rank for that query
page	Bing results page number
title	Result title
url	Result landing page URL
displayUrl	Visible URL shown on Bing
snippet	Search result description
cachedUrl	Cached result URL when available
sitelinks	Extra links shown below a result
relatedSearches	Related search suggestions found on the page
scrapedAt	ISO timestamp for the scrape

Pricing

This Actor uses Apify pay-per-event pricing. The prices below come from the current Actor pricing configuration. Apify public plans map to Store discount tiers, so the table shows both the user-facing plan context and the pricing tier name. The final price shown in Apify depends on the user account plan and any custom agreement.

Event	What is charged	Price
start	One-time fee charged when a run starts. Covers fixed startup cost.	$0.005

Event	What is charged	Free / no discount	Starter / Bronze	Scale / Silver	Business / Gold	Custom / Platinum	Custom / Diamond
result	Charged per Bing organic search result extracted.	$0.0303 / 1,000	$0.02635 / 1,000	$0.02055 / 1,000	$0.01581 / 1,000	$0.01054 / 1,000	$0.01 / 1,000

Apify may also charge platform usage for compute, storage, proxies, or data transfer outside this Actor pricing. Check the Actor run and the Apify Pricing tab for the exact cost shown to your account.

Quick start

1. Open the actor on Apify.
2. Add one or more Bing search queries.
3. Set the maximum results per query.
4. Choose market, language, and SafeSearch settings if needed.
5. Run the actor.
6. Download the dataset or connect it to your workflow.

Input: queries

Use queries when you want the actor to build Bing search URLs for you.

Example queries:

[
  "apify web scraping",
  "best crm software for agencies",
  "site:example.com pricing"
]

Each query is scraped separately and ranks restart at position 1 for each query.

Input: start URLs

Use startUrls when you already have Bing search URLs.

Example:

[
  { "url": "https://www.bing.com/search?q=apify&count=10" }
]

The actor reads the query from the URL and continues pagination from the URL page.

Input options

maxResultsPerQuery controls how many organic results to save for each query or start URL.

market requests a Bing market such as en-US, en-GB, de-DE, or fr-FR.

language requests a preferred result language such as en, de, fr, or es.

safeSearch can be Off, Moderate, or Strict.

includeRelatedSearches adds related search suggestions to result rows when Bing provides them.

Output example

{
  "query": "apify web scraping",
  "position": 1,
  "page": 1,
  "title": "Apify: Full-stack web scraping and data extraction platform",
  "url": "https://apify.com/",
  "displayUrl": "https://apify.com",
  "snippet": "Apify is a platform for web scraping, browser automation, and data extraction.",
  "cachedUrl": null,
  "sitelinks": [],
  "relatedSearches": ["apify pricing", "apify actors"],
  "scrapedAt": "2026-06-17T00:00:00.000Z"
}

Tips for better results

• Keep early tests small, then scale once the output looks correct.
• Use exact phrases for brand monitoring.
• Add site: operators for domain-specific research.
• Use market and language settings for regional checks.
• Split very different keyword groups into separate runs for easier analysis.

Pagination behavior

Bing normally shows around 10 organic results per page.

When you request more than 10 results per query, the actor requests additional result pages until it reaches your limit or Bing stops returning organic results.

Each row includes both position and page so you can filter by page or rank range.

Integrations

You can connect the dataset to:

• Google Sheets for keyword research reviews.
• BigQuery or Snowflake for search monitoring dashboards.
• Slack alerts for brand or competitor checks.
• CRM enrichment flows for lead generation.
• Scheduled Apify tasks for recurring SERP snapshots.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/bing-search-results-scraper').call({
  queries: ['apify web scraping'],
  maxResultsPerQuery: 10,
});

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

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/bing-search-results-scraper').call(run_input={
    'queries': ['apify web scraping'],
    'maxResultsPerQuery': 10,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage with cURL

curl -X POST "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}'

MCP: use from Claude tools

You can call this actor from Apify MCP-enabled clients.

Claude Code MCP URL pattern:

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

Add it in Claude Code with:

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

Claude Desktop JSON configuration example:

{
  "mcpServers": {
    "apify-bing-serp": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/bing-search-results-scraper"
    }
  }
}

Claude Desktop can use the same Apify MCP server URL with your Apify token.

Example prompts:

• "Scrape the top 20 Bing results for best no-code database and summarize the domains."
• "Run Bing Search Results Scraper for these 10 keywords and export titles and URLs."
• "Find related searches for my brand query on Bing."

Scheduling

Create an Apify task with your keywords and run it daily, weekly, or monthly.

Recurring runs are useful for rank tracking, competitor monitoring, and campaign snapshots.

Common SEO workflows

• Track whether your domain appears for target keywords.
• Compare page-one competitors across markets.
• Collect titles and snippets for content analysis.
• Monitor brand SERPs after launches or press releases.
• Export SERP data for internal dashboards.

Common lead generation workflows

• Search for niche directories.
• Find companies using keyword modifiers.
• Collect URLs for later enrichment.
• Combine with website contact scrapers.
• Build prospect lists from regional searches.

Limits and reliability

Search engines can change markup and may throttle repeated automated requests.

Start with moderate limits, use scheduling responsibly, and enable proxy settings if direct traffic is throttled.

The actor is designed to stop gracefully when Bing returns no more organic results.

Troubleshooting

If you get fewer results than requested, Bing may have returned fewer organic results for that query or region.

If a run returns no results, try a simple query such as apify web scraping, lower the limit, or enable Apify Proxy in the input.

If regional results look unexpected, check the market, language, and SafeSearch values.

Legality

This actor extracts publicly available search result information.

You are responsible for using the data lawfully, respecting applicable terms, privacy rules, and rate limits, and avoiding collection of sensitive personal data where it is not appropriate.

FAQ

Can I scrape multiple keywords?

Yes. Add multiple strings to queries. The actor processes each query separately.

Can I scrape direct Bing URLs?

Yes. Add Bing search result URLs to startUrls.

Does it include ads?

Version 0.1 focuses on organic search results. Paid ads and rich answer modules may be added later.

Does it work with markets outside the United States?

Yes. Set market and language to request localized results.

Why are some fields empty?

Bing does not show every field for every result. For example, cached URLs and sitelinks are optional.

Related Actors

Explore other Apify actors from the same publisher for search, SEO, and lead-generation workflows:

• Google Shopping Results Scraper
• Google News Scraper
• Google Maps Lead Finder
• Website Contact Finder
• GitHub Repositories Search Scraper

Support

If the actor stops returning expected fields, open an issue with the run URL, input, and a short description of what looked wrong.

Small reproducible inputs help us diagnose markup changes quickly.