Apify Public Data & Leads

Google Autocomplete Keyword Suggestions

google_autocomplete_keywords

Read-only

Generate localized Google Autocomplete keyword suggestions from seed phrases to uncover long-tail keywords, customer questions, and content ideas.

Instructions

Generate localized Google Autocomplete keyword suggestions from one or many seed phrases. Supports alphabet and question-prefix expansion and returns ranked, globally deduplicated keyword ideas.

Behavioral Transparency:

Execution: Network call executed synchronously in the cloud via Apify Actor 'captainhandsome/google-autocomplete-keyword-suggestions'.
Side Effects: Reads public sources and creates a billed Actor run and dataset on your Apify account.
Authentication: Requires APIFY_TOKEN environment variable.
Latency & Limits: Base queries normally finish in 5-20 seconds; expansion modes make additional requests; output is capped by max_results.

Usage Guidelines:

When to use: Use for long-tail SEO research, customer-question discovery, content planning, and localized keyword ideation.
When NOT to use: Do not treat suggestions as verified search-volume, CPC, or competition data.
Named alternatives: Use 'google_news_search' for current news coverage. This server does not include a general web search tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`country`	No	Two-letter country code used to localize suggestions.	US
`queries`	Yes	Seed phrases to expand.
`language`	No	Two-letter suggestion language code.	en
`max_results`	No	Maximum unique suggestions to return.
`expansion_mode`	No	Optional query expansion strategy.	none

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`error`	No
`status`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv1.1.0Sep 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "object"
+}
```
- changedOutput schema / properties / results / items / properties / country / description
```
Previous value: -"Country code used."New value: +"Country code used for the request."
```
- addedOutput schema / properties / results / items / properties / country / title
```
Added value: +"Country"
```
- changedOutput schema / properties / results / items / properties / expansion / description
```
Previous value: -"Expansion prefix, suffix, or base."New value: +"Suffix or prefix that generated the request, or base for the unexpanded seed."
```
- addedOutput schema / properties / results / items / properties / expansion / title
```
Added value: +"Expansion"
```
- changedOutput schema / properties / results / items / properties / language / description
```
Previous value: -"Language code used."New value: +"Language code used for the request."
```
- addedOutput schema / properties / results / items / properties / language / title
```
Added value: +"Language"
```
- changedOutput schema / properties / results / items / properties / rank / description
```
Previous value: -"Position in the source response."New value: +"One-based position in the source suggestion response."
```
- addedOutput schema / properties / results / items / properties / rank / title
```
Added value: +"Rank"
```
- changedOutput schema / properties / results / items / properties / request_query / description
```
Previous value: -"Exact expanded request phrase."New value: +"Exact phrase sent to the suggestion endpoint."
```
- addedOutput schema / properties / results / items / properties / request_query / title
```
Added value: +"Request Query"
```
- changedOutput schema / properties / results / items / properties / seed / description
```
Previous value: -"Original seed phrase."New value: +"Original seed phrase supplied by the user."
```
- addedOutput schema / properties / results / items / properties / seed / title
```
Added value: +"Seed"
```
- changedOutput schema / properties / results / items / properties / suggestion / description
```
Previous value: -"Autocomplete keyword suggestion."New value: +"Autocomplete suggestion returned by Google."
```
- addedOutput schema / properties / results / items / properties / suggestion / title
```
Added value: +"Suggestion"
```
- addedOutput schema / properties / run
```
Added value: +{
+  "type": "object"
+}
```
- addedOutput schema / properties / status
```
Added value: +{
+  "enum": [
+    "success",
+    "empty_unverified",
+    "partial",
+    "error"
+  ],
+  "type": "string"
+}
```
- changedOutput schema / required
```
Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "status"
+]
```
Addedv1.0.13Sep 14, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations, the description has a 'Behavioral Transparency' section detailing execution method (synchronous network call via Apify Actor), side effects (billed run and dataset creation), authentication (APIFY_TOKEN), and latency limits. This is rich, non-redundant disclosure that exceeds the annotation hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured into clear sections (Behavioral Transparency, Usage Guidelines) and front-loaded with the core purpose. Every sentence delivers information; no fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description supplies all necessary operational details: execution, side effects, auth, latency, and clear usage guidance. Nothing an agent needs to decide or call the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that expansion modes cause additional requests and that max_results caps output, providing behavioral context for those parameters beyond their schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Generate localized Google Autocomplete keyword suggestions from one or many seed phrases.' It also details supported features (alphabet/question expansion, ranking, deduplication) and later names a sibling alternative (google_news_search), making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

A dedicated 'Usage Guidelines' section explicitly states when to use (SEO research, question discovery, content planning) and when NOT to use (not as verified volume/CPC data). It also names the alternative tool 'google_news_search' for news coverage, satisfying the when/alternative requirement clearly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.