Bing Rank Tracker & SERP Scraper

Export public Bing organic result rows from keywords or Bing search URLs. Save observed positions, titles, destination links, snippets and collection times for your own research, reporting or dated comparisons.

Quick start

Use this bounded two-query example, then open the completed run’s dataset. The cap is per query or search URL, rather than a guaranteed total yield.

{
  "queries": ["apify web scraping", "open source crawlee"],
  "maxResultsPerQuery": 10,
  "market": "en-US",
  "language": "en",
  "safeSearch": "Moderate",
  "includeRelatedSearches": true,
  "connectionMode": "direct"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a small preconfigured input, then adjust its queries and limits for your run. These examples collect snapshots. They do not schedule recurring monitoring.

• AI-agent keyword rankings — Export organic positions for AI-agent search terms.
• Related searches for keyword expansion — Include related suggestions when Bing exposes them.
• UK-market search results — Start with en-GB. Change market for a separate US snapshot. The example does not compare markets automatically.

What you get

One row per saved organic result, with query, observed position, page, title, destination URL, display URL, snippet and collection time. Cached links, sitelinks and related-search suggestions are included only when Bing exposes them. Market and language are request settings rather than output fields.

Who is it for?

• Search researchers reviewing where public websites appear for selected Bing queries.
• Market and competitor analysts preparing a cited set of relevant public pages.
• Content teams inspecting related-search suggestions for their own topic planning.
• Data teams keeping dated organic-result exports in a spreadsheet or database.

How you can use the data

• Prepare a cited search-result sheet. Search apify web scraping with a small cap and keep query, position, title, url, snippet and scrapedAt. Open the destination links before using a result in research.
• Compare a website's observed position over time. Join separate exports by query and URL, deriving website domains in your own workflow when useful. Bing can change or localize results, so these are dated observations rather than permanently reproducible ranks or a measure of ranking improvement.
• Review related-search ideas. Keep available relatedSearches beside the originating query, then choose which phrases to investigate in a separate workflow. The Actor does not automatically turn those suggestions into a new research plan.
• Compare requested markets carefully. Make separate US and UK requests and label your own exports with the inputs used. Market and language are not columns returned on each result row, and the Actor does not compare markets automatically.

Input settings

Provide at least one nonempty query, a public HTTPS Bing /search URL containing a query, or valid resumeSeeds. Use at most 100 combined seeds per run. Queries are limited to 2048 characters and search URLs to 8192. Requests are processed sequentially, with no concurrency setting.

Setting	JSON key	What to enter
Queries	queries	Bing keywords or phrases, one per row.
Bing search URLs	startUrls	Optional direct Bing SERP URLs with query parameters.
Maximum results per query	maxResultsPerQuery	Number of organic rows to save per query or URL.
Market	market	Bing market code such as en-US, en-GB, de-DE, or fr-FR.
Language	language	Preferred result language such as en, de, fr, or es.
SafeSearch	safeSearch	Off, Moderate, or Strict.
Include related searches	includeRelatedSearches	Adds related-search suggestions to each row when found.
Connection	connectionMode	Direct by default. Automatic uses the existing managed proxy route. See input help for costs and precedence.
Legacy proxy settings	proxyConfiguration	Optional existing managed settings or customer proxy pool.
Run time budget	maxRunSeconds	Optional shared processing budget, capped at 270 seconds.
Resume seeds	resumeSeeds	Copy PENDING_SEEDS into a new run, retaining query, URL, page, saved count and optional skipOnPage.

Output data

Illustrative output shape, not a captured result or a guarantee of current rankings:

{
  "query": "apify web scraping",
  "position": 1,
  "page": 1,
  "title": "Apify: Full-stack web scraping and browser automation platform",
  "url": "https://apify.com/",
  "displayUrl": "apify.com",
  "snippet": "Apify is a cloud platform for web scraping...",
  "cachedUrl": null,
  "sitelinks": [],
  "relatedSearches": ["apify actors", "crawlee"],
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

Field	Description
query	Search query or decoded query from the start URL.
position, page	Organic rank and result page number.
title, url, displayUrl	Result title, destination URL, and displayed URL.
snippet, cachedUrl	Result snippet and cached URL when Bing exposes one.
sitelinks	Additional links grouped under the result.
relatedSearches	Related-search suggestions found on the result page.
scrapedAt	ISO timestamp when the row was created.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing: a one-time start event after seed validation, then a result event for each saved organic result. A started search can incur the start charge even if Bing returns no usable rows. Error summaries are not charged as result rows.

See the live Pricing tab for current rates and account discounts. Bound work with the number of queries, maxResultsPerQuery (up to 100 per query or URL), and maxRunSeconds. Proxy choices can affect usage costs. Inspect the run's cost breakdown.

Tips for best results

• Start with 10–20 results per query. Inspect the saved organic rows before collecting broader query batches.
• Use a Bing search URL when its parameters matter. Keywords are simpler when you only need a normal query.
• Keep related searches when they help your research. The field depends on what Bing returns and can be absent.
• Review the summary before continuing interrupted work. Copy the actual saved pending seeds, preserving their query, URL, page and saved count.
• Reduce request volume if access is limited. The existing optional proxy settings are described in the input help, and they do not guarantee access.

Limits and caveats

• This actor extracts organic Bing results. It does not promise paid ads, shopping modules, maps modules, or every rich SERP element.
• Bing can personalize, localize, or test result pages, so repeated runs may differ.
• Start URLs must be public HTTPS Bing /search URLs without credentials or custom ports. The Actor follows at most three redirects and reads at most 2 MiB of decompressed HTML per request, with up to three attempts and 20 pages per seed. HTML parsing stops above 20,000 tags, 256 attributes per tag or 20,000 attributes in total. A page may contain at most 100 organic records; extracted text fields are limited to 32,768 characters, raw and normalized destination URLs (including sitelinks and cache links) to 8192 characters, and the page's serialized output to a conservative 4 MiB UTF-16 estimate. Retained deduplication keys have a conservative 16 MiB payload-and-overhead estimate. Oversized or incomplete extraction is reported rather than silently accepted.
• Supported memory allocations are 256 or 512 MiB, with 256 MiB retained as the default. The higher setting provides additional parsing headroom, not extra requests or guaranteed access. Pathological pages can still reach a safety bound; they are reported as incomplete extraction rather than empty results.
• The processing deadline is measured from the original run start. Automatic restart refuses to repeat charged work. For an interrupted run with available PENDING_SEEDS, copy the full entries into a new run's resumeSeeds. Live results can change between runs.
• Explicit source-reported no matches succeed with zero rows and reasons in RUN_SUMMARY. A challenge, unknown empty page, repeated page or failed required query is not proof of no matches: the run fails while keeping useful rows. Essential dataset, billing and summary-storage failures also fail.
• At the event-charge budget the Actor stops new requests, preserves saved rows and records pending work and saved/charged counts in RUN_SUMMARY. A budget stop is not a claim that all requested searches completed.
• Organic position is the observed public Bing position at scrape time. Market and language request result context but do not guarantee a personalized or permanently reproducible ranking.
• Some result pages omit sitelinks, cached URLs, or related searches.
• Respect Bing's terms and applicable laws when using exported data.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl "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,
    "market": "en-US"
  }'

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,
  market: 'en-US',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

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

MCP and AI agents

You can ask your AI assistant to collect data with Bing Search Results Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Bing Search Results Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Bing Search Results Scraper by Fetch Cat, or give it the identifier fetch_cat/bing-search-results-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Bing Search Results Scraper to collect up to 5 organic results for apify web scraping in the US market. Show observed positions, titles, destination links and snippets, keeping collection time.”
• “Collect at most 5 organic results for open source crawlee in the UK market, including related searches when available. Keep the original query and links so I can review the suggestions separately.”
• “Retrieve up to 5 organic results from this public Bing search URL. Keep page, position and source links, and explain any partial progress before I compare the export with my earlier snapshot.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I scrape multiple Bing keywords in one run?

Yes. Add multiple values to queries. The Actor saves ranked rows for each query.

Can I export to CSV or Excel?

Yes. Download the Apify dataset as CSV, Excel, JSON, XML, RSS, or through the Dataset API.

Does it include ads?

No. The actor is designed for organic search result rows.

Why are some fields empty?

Bing does not expose every field for every result. Nullable fields are expected.

Related Actors

• Google News Scraper — Collect Google News headlines, publishers, dates and feed descriptions for news research alongside web search results. Full article text is not included.
• Google Trending Searches Scraper — Collect current trending search topics by country, with traffic estimates and optional related news, for timely topic research.
• Google Autocomplete Scraper — Collect ordered Google autocomplete suggestions from seed phrases for keyword research. These suggestions do not include search-volume estimates.
• Google Shopping Results Scraper — Collect Google Shopping result cards with prices, merchants and available ratings for product comparisons.
• Website Content Crawler Lite — Crawl public website pages and export text, Markdown, HTML and discovered links when you need page content beyond search snippets.

Privacy and data handling

This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses the supplied Bing queries, public search URLs and supported continuation seeds to produce the organic-result dataset. Results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥