Skip to content

Bing Custom Search Results in Structured JSON

Bing Custom Search result pages depend on JavaScript and active bot detection.

OUTPUT FORMATSHTMLJSONMarkdown

A managed scraping API can absorb both concerns so your application only needs to send an HTTP request with a target URL. This page explains what the API returns, which request controls matter, and how to choose between raw HTML, CSS-based extraction, and AI-driven extraction for a curated search corpus.

What the API does

The API accepts a Bing Custom Search URL and returns the page after rendering. You can receive parsed HTML or structured JSON. The structured path is built around extract_rules, which maps CSS selectors to fields such as position, URL, title, and snippet, or ai_extract_rules, which describes the data you want in natural language. The service handles proxy rotation and headless-browser rendering so your client stays a thin HTTP call.

Common tasks for a curated corpus

Teams typically use this API for three jobs. First, collecting SEO keyword data from a configured corpus: ranking position, snippets, and metadata for queries. Second, checking whether a Custom Search engine surfaces relevant pages for target queries, which helps tune corpus inclusion and exclusion rules. Third, scraping vertical results from any configured engine to monitor how a niche corpus performs against query patterns. Each job benefits from the same structured output fields, so downstream analysis can compare results across queries and engines.

Output fields and what they support

A typical Bing Custom Search SERP returns position, URL, title, snippet, and SERP-feature flags. The API can also return ad placements and SERP-feature appearances when you request structured JSON. Use this field map to decide what to capture:

  • Position: rank of a result for a query against your corpus.
  • URL: destination page for the result.
  • Title: visible result title.
  • Snippet: descriptive text shown under the title.
  • SERP-feature flags: indicators of special result treatments on the page.
  • Ad placements: paid result positions when present.

If you need a field not listed here, use extract_rules with a CSS selector or ai_extract_rules with a natural-language description.

Request controls checklist

Use this checklist before sending a request:

  • render_js=true when the target page needs JavaScript execution; the API runs the page in a headless browser and returns post-render HTML.
  • stealth_proxy when a target shows aggressive blocking; this is the escalation path after standard proxy rotation.
  • country_code when content varies by geography; this routes the request through a residential IP in the selected country.
  • extract_rules with CSS selectors when you know the page structure and want parsed JSON.
  • ai_extract_rules when you want natural-language extraction without writing selectors.
  • A pre-saved request configuration when you reuse the same setup across runs.

Telling failure modes apart

Three problems look similar in a failed run but need different fixes. If the response is missing content that appears in a browser, the page likely needs JavaScript rendering; set render_js=true. If the request is blocked or challenged, the target may be reacting to traffic patterns; enable stealth_proxy. If the same query returns different results depending on where it is sent from, the content is probably geo-variant; set country_code. Checking these in order avoids adding controls that do not address the actual cause.

Worked example: a query against a configured corpus

Suppose your team has a Custom Search engine configured for a niche set of sites and you want to check how it ranks pages for a target query. Send the Bing Custom Search URL for that query with render_js=true so the page fully loads. Add extract_rules mapping CSS selectors to position, URL, title, and snippet. The response is JSON you can store alongside the query and engine identifier. If you later want SERP-feature flags or ad placements, extend the extraction rules or switch to ai_extract_rules with a description of the additional fields. This example uses only the controls and outputs described on this page; it does not assume a specific corpus or query.

Getting started

Create an account to receive an API key and free test credits. Install an SDK for Python, Node.js, Go, PHP, Ruby, or Java, or use raw cURL. Send a GET request with the target URL and your API key. The API renders the page, rotates proxies, and returns the data. The dashboard also includes a request builder that lets you paste a URL, set parameters, and copy a generated snippet in your preferred language.

Plan comparison
PlanMonthly priceAPI creditsConcurrent requestsJavaScript renderingRotating & premium proxiesGeotargetingScreenshots & extraction rulesPriority email supportDedicated account managerTeam management
Hobby$19 /mo75,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49 /mo250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

All prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. Each successful request that enables JS rendering costs 5 API credits. Each successful request that enables Premium proxies costs 10 or 25 API credits, depending on whether JS rendering is disabled or not. Geotargeting routes through any of 200+ countries and territories (40+ on classic proxies). Screenshots & extraction rules capture full-page screenshots and pull structured data using CSS or XPath extraction rules. Team management allows inviting multiple users and assigning a custom quota of credits and concurrency. This plan table is a dated reference from the source page; check current pricing and terms before purchase.

Frequently asked questions

What data can I extract from Bing Custom Search?

Whatever is visible on the public result page is available to capture. For structured JSON output, map fields with extract_rules using CSS selectors, or describe the fields you want in plain language through ai_extract_rules instead of writing selectors.

How do I get started scraping Bing Custom Search?

Sign up, grab your API key, and send a GET request with the target URL. The API renders the page, rotates proxies, and returns the data. Free test credits are available to start.

Will I get blocked when scraping Bing Custom Search?

Traffic goes out through rotating residential proxies and a real headless browser, so each request carries the profile of a normal visitor. When one target starts pushing back harder, switch on stealth_proxy for that request.

Can I scrape Bing Custom Search without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping Bing Custom Search?

Pass render_js=true on the request. The API runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML.

Can I scrape Bing Custom Search from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.