Bing Search API Replacement: scrape SERP results for $1.05/1K

Devil Scrapes Posted on May 31 Bing Search API Replacement: scrape SERP results for $1.05/1K # webscraping # seo # python # apify Quick answer: Microsoft retired the Bing Search API on August 11, 2025. There is no longer an official endpoint. A Bing search scraper hits the same www.bing.com/search HTML endpoint any browser hits, decodes the bing.com/ck/a redirect wrappers to canonical URLs, and returns clean typed rows — query, position, title, URL, snippet, country, language, timestamp. The Apify Actor below costs $0.001 per row (~$1.05 per 1,000), with TLS fingerprint rotation, residential proxy routing, and Bing's pagination handled for you. Microsoft's retirement notice landed on August 11, 2025, and thousands of teams who had wired Bing SERP data into rank trackers, brand-monitoring dashboards, and RAG pipelines found themselves holding a dead api.bing.microsoft.com call. The official replacement — "Grounding with Bing Search" inside Azure AI — is gated behind an Azure subscription and priced for LLM workflows, not raw SERP pulls. SerpApi and DataForSEO fill the gap at $75–225/month. DIY means debugging redirect wrappers at 11pm. This post covers where a naive scraper breaks and how I packaged the fix as a cheap Apify Actor. What is Bing Search? 🔎 Bing is Microsoft's web search engine. For SEO practitioners it matters because its ranking signals diverge from Google's — it weights on-page keyword density and anchor text differently, surfaces more forum content, and runs its own crawler ( bingbot ) with independent crawl frequency. For AI and RAG applications, Bing's index includes different long-tail pages than Google's; an LLM agent that only queries one engine has blind spots the other would fill. The SERP itself — www.bing.com/search?q=<query> — is a server-rendered HTML page. It returns 10 organic <li class="b_algo"> blocks per page, paginated via &first=0,10,20,... . Everything the old API gave you (titles, URLs, snippets) is in that HTML.