Google Keyword Suggest. Long-Tail Keywords & Autocomplete avatar

Google Keyword Suggest. Long-Tail Keywords & Autocomplete

Pricing

from $1.80 / 1,000 keyword suggestion delivereds

Go to Apify Store
Google Keyword Suggest. Long-Tail Keywords & Autocomplete

Google Keyword Suggest. Long-Tail Keywords & Autocomplete

Scrape Google autocomplete for any seed keyword. A–Z expansion, question modifiers, prefix expansion. Hundreds of long-tail keywords per seed, with country and language targeting. No API key.

Pricing

from $1.80 / 1,000 keyword suggestion delivereds

Rating

0.0

(0)

Developer

Andrew

Andrew

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Share

Google Keyword Suggest — Long-Tail Keywords & Autocomplete

Scrape Google autocomplete for any seed keyword — A–Z expansion, question modifiers, prefix expansion. Hundreds of long-tail keywords per seed, with country and language targeting. No API key.

What you get

  • One row per autocomplete suggestion, deduplicated across all expansion queries
  • Relevance score for every suggestion (Google's internal ranking, 0–1300+) — sort by this for the most popular long-tails
  • Country and language targeting — get suggestions as a US English searcher, a UK searcher, a Brazilian Portuguese searcher, etc.
  • Five expansion modes — pick the volume / cost trade-off that fits your task
  • Direct export to JSON, CSV, Excel, or Google Sheets

Use cases

  • SEO content briefs — feed a seed topic and get a question-keyword cluster ("how does X work", "what is X", …) for FAQ sections
  • Long-tail keyword research — surface 100s of low-competition phrases per topic without paying $99/mo for Ahrefs or AnswerThePublic
  • PPC keyword discovery — find buyer-intent modifiers (buy X, X near me, X reviews) by running suffix + prefix expansion
  • Product/feature ideation — pull all autocompletes for your product category to see what users actually ask
  • AI/LLM seed data — generate diverse query lists for evals, RAG benchmarks, or prompt-injection tests
  • Trend tracking — schedule a daily run and diff today's suggestions vs. yesterday's to spot emerging searches

Expansion modes

ModeWhat it firesQueries per seed
noneJust the seed1
suffix-a-zseed, seed a, seed b, … seed z27
prefix-a-zseed, a seed, b seed, … z seed27
both-a-zSuffix + prefix combined53
questionsSeed plus who/what/when/where/why/how/can/are/is/do/does/will/should/which15
allSuffix + prefix + questions — maximum coverage67

Each query returns up to 15 suggestions; deduplication usually leaves 100–300 unique long-tails per seed in all mode.

How to use

  1. Enter one or more Seed keywords (e.g. crm software, personal trainer, kubernetes)
  2. Pick an Expansion mode — start with suffix-a-z (cheap, broad coverage)
  3. Set Country and Language for geo/locale-targeted autocomplete (e.g. us + en, br + pt, de + de)
  4. Set Max items (0 = no cap) and run
  5. Sort the dataset by relevance descending — top hits are what real users search most

Output format

{
"seed": "crm software",
"query": "crm software for",
"suggestion": "crm software for small businesses",
"relevance": 560,
"type": "QUERY",
"expansionType": "suffix-a-z",
"expansionToken": "f",
"country": "us",
"language": "en",
"fetchedAt": "2026-05-18T01:30:00.000Z"
}

The query field is the exact string sent to Google (seed + the expansion token); suggestion is what Google returned. relevance is Google's internal ranking — higher = more searched.

Input options

FieldTypeDescription
SeedsarrayOne or more seed keywords
Expansion modeenumnone / suffix-a-z / prefix-a-z / both-a-z / questions / all
CountrystringTwo-letter country code (us, uk, de, br, in, …)
LanguagestringTwo-letter language code (en, es, pt, fr, de, …)
Max itemsintegerCap on suggestions across all seeds. 0 = no cap

Notes

  • Suggestions are deduplicated per seed (case-insensitive)
  • type is Google's classification of the suggestion — QUERY for normal searches, NAVIGATION for site jumps, ENTITY for known entities
  • Country and language combinations should be plausible (gl=br hl=pt works; gl=br hl=ja will fall back to defaults)