Skip to content

Google Related Searches API

Google's related-search block lists queries that other people typed after the same starting query.

OUTPUT FORMATSHTMLJSONMarkdown

Pulling that block programmatically is useful for keyword expansion, content gap analysis, and intent mapping. This page explains what the endpoint returns, how to plan credit usage, and which plan tier matches your workload.

What the endpoint returns

The response is a list of queries related to the original search query. These are the suggestions Google shows beneath the main results, and they help refine or expand a search. In practice you get a set of short phrases rather than full result pages, so the output is compact and easy to feed into a keyword tool, a content brief, or a clustering step.

How Google generates related searches

Google looks at user queries and interaction data, then uses algorithms that weigh keyword associations and search patterns. The result is a set of terms connected to the initial search. Because the list is algorithmic and refreshed over time, treat any single snapshot as a point-in-time sample rather than a fixed taxonomy.

Decision checklist: is this the right tool?

Use this checklist before you commit to a plan.

  • You only need the related-search suggestions, not the full SERP layout. If you also need organic results, ads, or knowledge panels, pair this with a broader SERP endpoint.
  • You can tolerate a point-in-time snapshot. Related searches shift, so schedule recurring pulls rather than relying on one run.
  • You have a clear legal position. Scraping Google may conflict with Google's terms of service, so review those terms and get legal advice if you are unsure. {{OWNER_LEGAL_REVIEW}}
  • You know your concurrency target. The plan table below shows how many simultaneous requests each tier allows.
  • You know whether you need JavaScript rendering or premium proxies, because both change the credit cost per request.

Worked credit-cost example

The published credit rules are: each request starts at 1 credit; enabling JavaScript rendering adds 5 credits per successful request; premium proxies cost 10 or 25 credits depending on whether JS rendering is off or on. So a plain request costs 1 credit, a JS-rendered request costs 6 (1 base + 5 JS), a premium-proxy request without JS costs 10, and a premium-proxy request with JS costs 25. If you run 10,000 plain requests in a month you consume 10,000 credits; the same volume with JS rendering consumes 60,000 (10,000 base + 50,000 JS). Credits are valid for one month and do not roll over, so size the plan to your monthly volume rather than to a peak you might hit once.

Plan and control map

The plan table below is the source of truth for price, credits, concurrency, and feature inclusion. Read it in four passes: first the monthly price, then the API credit allowance, then the concurrent-request ceiling, then the feature rows (JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules, priority email support, dedicated account manager, team management). The lower three standard tiers exclude priority support, a dedicated account manager, and team management; those features appear from the Business tier upward. All prices are exclusive of VAT.

Three different failure modes

When a pull fails, the cause is usually one of three things, and each needs a different response. A legal or terms-of-service problem is a policy question, not a technical one: review Google's terms and your own compliance position before retrying. A blocking problem is technical: the target may rate-limit or challenge automated traffic, which is why the platform rotates proxies and uses headless browser rendering to mimic real browsing. A credit problem is commercial: if your monthly allowance is exhausted, requests stop until the next cycle, and credits do not roll over. Diagnosing which of the three you are facing saves time before you change plans or code.

Getting started

The workflow is short. Create an account to get an API key and starting credits ({{OWNER_FREE_CREDITS_OFFER}}). Add {{OWNER_SDK_PACKAGE}} to your project so you do not have to manage proxies or browsers yourself. Send requests with your key and receive rendered HTML ready for parsing. Then use the advanced features, such as extraction rules or JavaScript scenarios, when a page needs dynamic interaction. Code samples are available in Java, Python, Go, PHP, Curl, and JavaScript, and the documentation covers the common use cases.

Plan comparison (captured reference)
PlanMonthly priceAPI creditsConcurrent requestsJS 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. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JavaScript rendering adds 5 credits per successful request; premium proxies cost 10 or 25 credits depending on whether JS rendering is disabled or enabled. This is a captured reference; check current pricing before purchase.

Frequently asked questions

What are Google related searches?

They are additional search terms Google suggests based on what you queried. They appear at the bottom of the results page and can reveal what users tend to search next, which is useful for keyword expansion and SEO planning.

What does a Google related searches API do?

It lets you fetch the related-search suggestions programmatically instead of reading them off a page. You send a query and receive the suggested terms in a structured response you can plug into your own tools.

Is scraping Google related searches legal?

It may conflict with Google's terms of service, which can create legal exposure. Review those terms and your own compliance obligations, and seek legal advice if you are unsure. Respecting site policies and data-usage rules is part of the decision.

How does Google decide which related searches to show?

It analyzes queries and interaction data, then applies algorithms that weigh keyword associations and search patterns. The goal is to surface terms connected to the original search and improve the search experience.

What data comes back from the endpoint?

A set of queries related to the original search query. These suggestions help refine or expand results based on what other users commonly search.

How can I find related searches on Google?

You can use Google's autocomplete in the search bar, or parse the related-searches section of the results page HTML with a scraping tool.