Google Autocomplete Scraper

Export Google autocomplete keyword suggestions by seed query, language, country, and client type.

Use this actor when you need a repeatable CSV, JSON, Excel, or API export of long-tail keyword ideas for SEO research, content planning, PPC research, market analysis, or AI-agent workflows.

At a glance

• Input: Seed queries, language, country, suggestion limit, Google client, retry settings, and optional proxy.
• Output: Original query, suggestion, rank, language, country, client, source URL, and fetch timestamp.
• Localization: Collect suggestions by country and language.
• Best for: Keyword research, content ideation, autocomplete exports, and Google Suggest API alternative workflows.
• Low-cost runs: Suggestions are lightweight; start with direct requests before enabling proxy.

What can it do?

• Export Google autocomplete suggestions: Save ranked suggestion rows for each seed query.
• Find long-tail keywords: Collect phrase variants that users may type into Google.
• Localize keyword research: Use country and language settings for market-specific suggestions.
• Support SEO workflows: Feed suggestions into content plans, keyword maps, and search-intent analysis.
• Use as a Google Autocomplete API alternative: Run from the Apify UI, API, schedules, webhooks, or the official Apify MCP server.

Common workflows

• SEO keyword research: Build long-tail keyword lists from seed topics.
• Content planning: Turn autocomplete suggestions into article ideas, FAQs, and page titles.
• PPC research: Discover wording variations for ad groups and landing pages.
• Market comparison: Run the same seed terms across countries and languages.
• AI-agent briefs: Fetch live suggestion rows before asking an agent to cluster or prioritize keywords.

Input example

{
  "queries": ["best running shoes", "how to start a podcast"],
  "language": "en",
  "country": "us",
  "maxSuggestionsPerQuery": 10,
  "client": "chrome",
  "requestDelayMs": 250,
  "maxRetries": 3,
  "useProxy": false,
  "proxyGroups": []
}

Output example

{
  "query": "best running shoes",
  "suggestion": "best running shoes for flat feet",
  "rank": 1,
  "language": "en",
  "country": "us",
  "client": "chrome",
  "sourceUrl": "https://suggestqueries.google.com/complete/search?...",
  "fetchedAt": "2026-07-03T10:00:00.000Z"
}

Tips for best results

• Use natural seed phrases instead of single generic words.
• Run separate jobs for different countries and languages.
• Keep maxSuggestionsPerQuery close to the number you actually need.
• Increase requestDelayMs or enable proxy if Google throttles requests.
• Cluster duplicate suggestions downstream when running many related seeds.

Limits and caveats

• Suggestions vary by country, language, time, Google experiments, and client type.
• This actor exports autocomplete suggestions only. It does not provide search volume or keyword difficulty.
• Google can return fewer suggestions than requested.
• Proxy groups must exist on your Apify account before you use them.

API usage

curl "https://api.apify.com/v2/acts/fetch_cat~google-autocomplete-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "queries": ["best running shoes"],
    "language": "en",
    "country": "us",
    "maxSuggestionsPerQuery": 10
  }'

MCP and AI agents

You can run this actor through the official Apify MCP server at https://mcp.apify.com.

For a focused single-actor tool, use:

https://mcp.apify.com?tools=fetch_cat/google-autocomplete-scraper

Agent-friendly inputs are queries, language, country, maxSuggestionsPerQuery, client, requestDelayMs, maxRetries, useProxy, and proxyGroups.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.