Bing Rank Tracker & SERP Scraper
Pricing
from $0.02 / 1,000 result extracteds
Export Bing organic search results with positions, titles, URLs, snippets and available related searches. Choose market and language for each search snapshot.
Bing keywords, one per row; at most 2048 characters each. Use at most 100 combined queries, URLs and resume seeds per run.
Public HTTPS Bing /search URLs with a nonempty query, no credentials or custom ports, and at most 8192 characters. At most 100 combined seeds per run. Remote URL-list expansion is not supported.
Maximum number of organic results to save for each query or start URL.
Bing market code, for example en-US, en-GB, de-DE, fr-FR, or es-ES; at most 64 characters.
Preferred result language code, for example en, de, fr, or es; at most 64 characters.
Bing SafeSearch level to request.
Direct (default) sends requests without a proxy and never switches to a paid proxy. Automatic uses the existing managed Apify Proxy route from the first request, with the same bounded retries and run budget. It does not try Direct first or guarantee access. Managed proxy usage can incur additional costs. Explicit legacy proxyConfiguration settings override this selector, including Direct/Automatic values supplied by the form.
Add related search suggestions found on the result page to each result row.
Processing deadline measured from the original run start, at most 270 seconds with a shutdown reserve. It cannot be renewed by a timeout override or automatic restart. Deadline-incomplete runs fail with saved rows and pending seeds available; charge-budget stops are reported separately.
Copy actual PENDING_SEEDS into a new run, retaining query, URL, page, savedForQuery and optional skipOnPage. Query/page must match the URL. The saved page offset avoids re-saving already completed rows from a budget-limited page. Automatic resurrection never repeats charged work. Live search results may change between runs; inspect combined output for changes.
Optional legacy connection settings. Explicit settings override Connection. useApifyProxy: false or omitted preserves Direct with no paid fallback, even if Automatic is selected. useApifyProxy: true preserves the existing SDK route: a nonempty proxyUrls pool uses those customer proxies, otherwise managed Apify Proxy options apply. Supported SDK groups, country/subdivision aliases, password, access-check and tier options remain accepted. Custom pools cannot be combined with managed groups/location options. Empty active proxy pools and malformed settings are rejected before charging/search work. Omit this object to use Connection. Never share proxy URLs or credentials in support examples.
