Bing Organic Results, Position-Ranked JSON
This page describes a scraper API that runs a Bing search and returns the ten organic results as a ranked list.
Each entry carries a position number, the result URL, the page title, a snippet description and a display URL. Ads, related-question blocks and knowledge-card material are excluded from the response, so the array you receive is the blue-link ranking rather than a mirror of the whole SERP. The sections below cover what the API returns, how to shape the request, what each option costs in credits, and how the plan tiers differ. Pricing figures and plan names are a snapshot and should be re-checked against the current pricing page before purchase.
What the scraper returns
A single request produces one organic results array for one query. Every row in that array has five fields: position, URL, title, meta description and display URL. The array is capped at the top ten results. Position numbers are assigned after duplicate URLs are removed and after SERP-feature blocks are skipped, so a position of 1 means the first true organic listing, not the first item on the page. If you need the raw page as well, the same request can return rendered HTML; the structured array is what most ranking workflows consume.
Shaping the request
The endpoint accepts either POST or GET with the Bing Organic Results URL. A minimal call needs only the query. Optional parameters change what comes back and what it costs:
- country_code routes the request through a chosen country or territory so the ranking reflects that market.
- device selects the device profile used for the SERP.
- language sets the result language.
- render_js turns on JavaScript rendering.
- stealth_proxy routes through premium proxies for pages that block ordinary requests.
- extract_rules maps CSS selectors to field names and returns parsed JSON.
- ai_extract_rules accepts a natural-language extraction spec and also returns parsed JSON.
A request that omits all optional parameters still returns the ten organic rows; the options exist to match a specific market, device or anti-bot situation.
Field and control map
Use this map to decide which request option you actually need before you spend credits.
Credit figures are the values captured from the product page and apply per successful request; confirm current rates on the pricing page before committing to a volume.
A weekly ranking refresh, worked through
Suppose you track forty keywords for one site and want a Monday snapshot. For each keyword you send one request with country_code set to your main market and no rendering, because Bing's organic list is server-rendered. You receive forty arrays of ten rows. Store each run with a run date, then compare position values for your domain between this week and last week. A domain that moves from position 6 to position 3 shows as a delta of −3; a domain that drops out of the ten shows as absent rather than as position 11, because the array is capped. That absence is itself a signal worth logging. If a keyword returns an anti-bot block instead of an array, re-run that single keyword with stealth_proxy rather than switching the whole batch, and record the extra credit cost against that keyword.
Three different failure modes
Requests can fail for reasons that look similar in a log but need different fixes.
- Concurrency limit. The plan caps how many requests can run at once. If you exceed it, requests queue or are rejected until a slot frees. The fix is to lower parallelism or move to a plan with a higher concurrent-request allowance.
- Target throttling. Bing may slow responses to aggressive patterns even when your concurrency is within plan. The fix is to space requests out or spread them across sessions.
- Anti-bot blocking. The target serves a challenge instead of results. The fix is stealth_proxy, which carries a higher credit cost.
Separating these three before changing anything avoids paying for stealth proxies when the real problem was a concurrency cap.
Choosing an output format
The API can return rendered HTML, parsed JSON via extract_rules, parsed JSON via ai_extract_rules, LLM-ready Markdown, or a full-page screenshot. For ranking work the parsed JSON array is the usual choice because it removes the parsing step. Markdown suits pipelines that feed a language model. Screenshots suit visual QA of a SERP layout. JavaScript scenarios suit cases where you must click, scroll or type before the page settles. Pick one format per workflow rather than mixing them in the same batch, so downstream schemas stay stable.
Plan tiers and limits
The product page lists two groups of plans. Standard plans run from Hobby through Business +, and enterprise plans run from Enterprise 14 through Enterprise 120. Each tier pairs a monthly credit allowance with a concurrent-request cap. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included from the Hobby tier upward. Priority email support, a dedicated account manager and team management appear only from the Business tier upward. All listed prices exclude VAT, and credits are valid for one month without rollover. The full numeric table is a pricing snapshot, not a live quote.
Commercial terms and service claims
Beyond the technical behaviour, several commercial and service terms shape a purchase decision. Each is stated here with the value the operator must confirm:
Getting from zero to a first request
Create an account to receive an API key and the free starting credits. Install the SDK for your stack, or skip the SDK and send a plain HTTP request. Copy a snippet from the documentation, replace the placeholder key with your own, and send one query. Check that the response contains ten rows and that the position values start at 1. Once that works, add country_code and any extraction rules you need, then measure the credit cost of one request before scaling to a batch.
| Plan | Price / month | API credits | Concurrent requests | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included |
Prices exclude VAT. Credits are valid for one month and do not roll over. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots and extraction rules are included on every listed tier.
| Output field | Where it comes from | Notes |
|---|---|---|
| position | Bing ranking after de-dupe and SERP-feature offsets | Integer, 1–10 |
| URL | The organic result link | Absolute URL |
| title | The page title as shown in the SERP | Text |
| meta description | The snippet shown under the title | Text |
| display URL | The breadcrumb-style URL shown in the result | Text |
| Request control | Effect | Credit note |
|---|---|---|
| render_js | Enables JavaScript rendering | 5 credits per successful request |
| premium_proxy without JS | Premium proxy routing | 10 credits per successful request |
| premium_proxy with JS | Premium proxy plus rendering | 25 credits per successful request |
| stealth_proxy | Stealth proxy routing | 75 credits per successful request |
| country_code | Geo-targeted routing | No separate credit line captured |
| extract_rules / ai_extract_rules | Parsed JSON output | No separate credit line captured |
Frequently asked questions
Do I need an account to scrape Bing organic results?
You do not need a Bing account. You do need an API key from this service. Sign up, receive 1,000 free credits without a card, then send the target URL and the service handles the request.
Is scraping Bing organic results legal?
Public-facing pages are generally the safe zone, but the target site's terms of service should be reviewed before you deploy at scale. Content behind a login is out of scope.
What is the rate limit for scraping Bing organic results?
Limits are expressed as concurrent requests per plan rather than as a per-target rate. If Bing throttles an aggressive pattern, space the requests out or spread them across sessions.
How do I get structured JSON from Bing organic results?
Send extract_rules with CSS selectors mapped to field names, or send ai_extract_rules with a natural-language spec. Either way the response arrives as parsed JSON.
Which programming languages can I use to scrape Bing organic results?
Any language that can send an HTTP request. Published SDKs cover Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well.
How much does it cost to scrape Bing organic results?
Signup includes 1,000 free credits with no card required. Paid plans begin at $19 per month for higher volume and concurrency. Per-request credit cost depends on options: 5 credits for JavaScript rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.