Bing Search Scraper — SERP Results, Positions, Snippets

Scrape Bing Search organic results at scale. Get position, title, URL, displayed URL, and snippet for every result — perfect for SEO rank tracking, SERP analysis, keyword research, and competitive intelligence.

What you get

Each result record contains:

Field	Description
position	Organic rank (1, 2, 3, … across pages)
title	Result page title
url	Real destination URL (decoded from Bing's tracking redirect)
displayed_url	Breadcrumb URL shown on the SERP (e.g. https://example.com › path)
snippet	Description text shown below the title
query	Your search query
market	Bing market code used (e.g. en-US, de-DE)
page	SERP page number the result came from
parse_confidence	Parse quality score (1.0 = perfect; <0.5 = schema drift detected)

Inputs

Input	Type	Default	Description
query	string	required	Search term to submit to Bing
market	string	en-US	Bing market code: language + region (en-GB, de-DE, fr-FR, …)
count	integer	10	Results per request (Bing caps at ~10)
maxItems	integer	50	Max organic results to collect (0 = unlimited up to Bing's index depth)
proxyConfiguration	proxy	RESIDENTIAL	Apify Residential proxy recommended for cloud reliability

Pricing

Pay-per-result (PPE): you are charged only for records actually returned — zero results means zero charge. Charged at the result-item event rate.

Why this scraper

• Structural parser — anchored on id="b_results" + li.b_algo + h2 > a, not rotating CSS class names. Survives Bing redesigns.
• Real URL decoding — Bing wraps every href in a tracking redirect; we base64-decode it to give you the actual destination.
• Cross-page dedup — automatically drops duplicate results when Bing recycles its shallow index.
• RESIDENTIAL proxy — no external proxy account needed; billed to your Apify run.
• parse_confidence in every record — immediate visibility if Bing's HTML structure changes.

Usage examples

SEO rank tracking

Query your brand or target keywords daily; use position to track rank changes over time.

Competitor analysis

Scrape SERPs for competitive keywords to see which domains consistently rank.

Keyword research

Collect titles and snippets from top results to understand what content ranks for a given keyword.

Multi-market SERP comparison

Run the same query with different market values (en-US, en-GB, de-DE) to compare regional SERP differences.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.