Bing Related Searches Scraper API
Our Bing related searches scraper pulls the People-also-search-for suggestions and the People-Also-Ask questions Bing attaches to a query, returning each as JSON on the same call that fetches the organic results, so you get the full query cluster from one request.
Why Bing makes Bing Related Searches data hard
The suggestions and questions around a Bing query are the keyword-research gold, but Bing has no API for them and only server-renders each block on some queries. Related searches ship reliably in the SERP HTML; the People-Also-Ask block renders only when Bing chooses to. We parse whichever blocks are present and return them as clean arrays, never failing the call over a missing one.
The Bing Related Searches Scraper API, one request away
curl "https://api.bingscraperapi.com/api/v1/bing/search?q=how+tall+is+mount+everest&api_key=$API_KEY"import requests
BASE = "https://api.bingscraperapi.com"
API_KEY = "YOUR_API_KEY"
data = requests.get(
f"{BASE}/api/v1/bing/search",
params={"q": "how tall is mount everest", "api_key": API_KEY},
timeout=30,
).json()
# People-also-search-for suggestions (present on most queries).
for s in data.get("related_searches", []):
print("related:", s["query"], "->", s["link"])
# People-Also-Ask questions (present when Bing renders the block).
for qa in data.get("related_questions", []):
print("Q:", qa["question"])
print("A:", qa["answer"])Parameters
| Parameter | Required | Default | Notes |
|---|---|---|---|
q | required | - | The seed query whose related searches and questions you want, e.g. how tall is mount everest. |
url | optional | - | A full bing.com/search URL to parse instead of building one from q. Pass q or url. |
country | optional | US | Two-letter market region, e.g. GB or DE. Sets mkt=en-XX so the suggestion set is the stable national one. Defaults to US. |
count | optional | 10 | Number of organic results to request alongside the blocks, 1 to 50. Defaults to 10. |
api_key | required | - | Your API key, passed as a query parameter. Get one free at signup. |
Fields returned by the Bing Related Searches Scraper API
{
"query": "how tall is mount everest",
"engine": "bing",
"results_count": 8,
"related_searches": [
{
"query": "how tall is mount Everest feet",
"link": "https://www.bing.com/search?q=how+tall+is+mount+Everest+feet&FORM=QSRE1"
},
{
"query": "how tall is mount fuji",
"link": "https://www.bing.com/search?q=how+tall+is+Mount+Fuji&FORM=QSRE3"
},
{
"query": "mount Everest height in meters",
"link": "https://www.bing.com/search?q=mount+Everest+height+in+meters&FORM=QSRE6"
}
],
"related_questions": [
{
"question": "How is the height of Mount Everest measured?",
"answer": "The most recent survey, published in 2020 by China and Nepal, put the snow height at 8,848.86 m using GPS and ground-based measurement.",
"title": "Mount Everest - Wikipedia",
"link": "https://en.wikipedia.org/wiki/Mount_Everest"
}
]
}| Field | Type | Description |
|---|---|---|
related_searches | array | People-also-search-for suggestions. Present on most queries. |
related_searches[].query | string | The suggested follow-up search phrase. |
related_searches[].link | string | The bing.com search URL for that suggestion. |
related_questions | array | People-Also-Ask entries. Present only when Bing server-renders the block for the query. |
related_questions[].question | string | The expandable question text. |
related_questions[].answer | string | The answer snippet from the expanded panel, or null when Bing shows none. |
related_questions[].link | string | The source URL cited for the answer, decoded from Bing's redirect. |
query | string | The seed query, echoed back from your request. |
What this data is good for
Keyword expansion
People-Also-Ask harvesting
Content brief building
FAQ and schema generation
Topic clustering
Assistant grounding
Why our Bing Related Searches Scraper API is reliable
One call returns the organic results plus the related searches and, when Bing renders it, the People-Also-Ask block, each parsed into a clean array with source links decoded from Bing's redirect wrapper. Every parser is defensive, so a missing block returns empty rather than erroring, and the request runs through rotating proxies with anti-bot handling and retries at a 2.6s median.
Related searches parsed
People-Also-Ask when present
Blocks on the organic call
Defensive, never fails on a block
Anti-bot and proxy rotation
Pinned market
Choosing between the Bing Related Searches Scraper API and the Bing API
| Our API | DIY (requests / headless) | Bing Web Search API (Azure) | |
|---|---|---|---|
| Related searches | Parsed to query + link | You write the selector | Available as relatedSearches |
| People-Also-Ask | Returned when Bing renders it | You parse the expansion block | Not a dedicated field |
| Availability | Live and maintained | Depends on your setup | Closed to new customers, sunsetting |
| Setup | API key only | Proxies, headless browser, parsers | Azure account and resource keys |
| Delivery | On the organic call, no extra request | Extra parsing per block | Separate response fields |
| Anti-bot and proxies | Built in | You build and maintain it | Not applicable |
Straightforward pricing
| Plan | Price | Best for |
|---|---|---|
| Free | 1,000 requests | Testing and small jobs |
| Pro | $0.60 / 1k | Production workloads |
| Pay-as-you-go | $0.90 / 1k | Spiky or one-off volume |
Median response 2.6s. You only pay for successful requests.
FAQ
A Bing related searches scraper reads the People-also-search-for suggestions Bing shows for a query and returns them in a structured format. Our API returns each suggestion as a query and a link, and on queries where Bing renders the People-Also-Ask block it also returns the related questions with their answer snippets and cited source links, all on the same call as the organic results.
No. Bing server-renders the People-Also-Ask block only for some queries, so the related_questions array is present when Bing chooses to show it and omitted otherwise. Related searches ship reliably in the SERP HTML and are present on most queries. Our parser is defensive: whichever blocks Bing renders are returned, and a missing block simply returns nothing rather than failing the request.
It is the same endpoint. A single bing/search call returns the organic results and attaches the related searches and, when present, the People-Also-Ask questions to the same response object. You choose which arrays to read. This landing focuses on the suggestion and question blocks, which are the parts useful for keyword and content research.
Related searches and People-Also-Ask reflect what Bing users search next right now, straight from the live SERP, so they capture fresh intent that a static keyword database may lag on. Pulling them per query also ties each suggestion to the exact SERP context, which is useful for building content briefs and topic clusters around real Bing behavior.
Yes. Call the endpoint once per seed term, collect the related_searches arrays, dedupe across them, and you have an expanded keyword set. Because each call is billed as one request and the free tier includes 1,000 requests, you can build a sizable cluster before paying anything.
The related_searches links are standard bing.com/search URLs for each suggested phrase, so you can follow them or feed the query text back into the endpoint. The source links inside related_questions are decoded from Bing's ck/a redirect to the real destination URL, so those point straight at the cited page.