Google Search Autocomplete Keyword Scraper Turn 1 seed keyword into 1,000+ long-tail ideas using Google Search Autocomplete – with smart prefix, suffix, alphabet, number and question-word expansion. --- ## 🎯 What Problem Does This Solve? Struggling to find long-tail keywords and real search questions? This Actor expands your seed keywords using Google Search Autocomplete and returns clean, de-duplicated suggestions ready for SEO and content planning. It's designed for automated workflows (n8n, Make, custom APIs) and supports prefixes, suffixes, alphabet, numbers, and question-word mining out of the box. --- ## ✨ Why This Actor? - 🔤 Smart expansion strategies: prefix, suffix, A-Z alphabet, optional number range, and language-aware question words - 🌍 Multi-language & region support: use Google's hl / gl parameters to target specific markets (English, Chinese, Japanese, Korean, Spanish, French, German) - 🧹 Clean output: de-duplicated suggestions with seed keyword, expansion type, and metadata (position, language, region, timestamp) - ⚙️ Workflow-ready: simple JSON schema output, ideal for n8n / Make / Zapier / internal automation tools - 📊 Summary statistics: total queries processed, unique suggestions collected, success rates, and per-keyword breakdown --- ## 🚀 Quick Examples ### Example 1: Basic Keyword Expansion Input: json { "keywords": ["seo tools"], "language": "en", "region": "US" } Output: ~20 suggestions like "seo tools free", "seo tools for small business", etc. --- ### Example 2: Question Mining for Content Ideas Input: json { "keywords": ["marketing"], "language": "en", "useQuestionWords": true } Output: ~150+ question-based suggestions like: - "how to marketing" - "what is marketing" - "why marketing is important" - "when marketing started" - ... (15 question words × keyword) Perfect for: Blog titles, FAQ content, YouTube video ideas --- ### Example 3: Product/Version Research with Numbers Input: json { "keywords": ["iphone"], "useNumberSuffix": true, "numberRange": {"start": 11, "end": 16} } Output: Suggestions for "iphone 11", "iphone 12", "iphone 13", "iphone 14", "iphone 15", "iphone 16" Perfect for: Product research, version comparisons, pricing analysis --- ### Example 4: Deep Keyword Mining with Alphabet Input: json { "keywords": ["best"], "useAlphabetSuffix": true } Output: 260+ suggestions from "best a" through "best z" (discovering niche categories like "best air fryer", "best budget phone", "best coffee maker"...) Perfect for: Comprehensive keyword mapping, finding hidden niches --- ### Example 5: List-Style Content Research (NEW in v0.4.0) Input: json { "keywords": ["best seo tools"], "useNumberPrefix": true, "numberRange": {"start": 1, "end": 10}, "numberPosition": "prefix" } Output: "1 best seo tools", "5 best seo tools", "10 best seo tools" Perfect for: Listicle headlines, ranking content ideas --- ## 📊 Configuration Reference ### Essential Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | keywords | Array | ✅ Yes | - | Seed keywords to expand (1-100 recommended) | | language | String | No | "en" | Google search language (en, zh-CN, ja, ko, etc.) | | region | String | No | "US" | Target country code (US, CN, GB, JP, etc.) | ### Expansion Methods | Parameter | Type | Default | When to Use | |-----------|------|---------|-------------| | useQuestionWords | Boolean | false | Content ideas, FAQ topics, blog titles | | useNumberSuffix | Boolean | false | Product versions, model numbers | | useNumberPrefix | Boolean | false | List-style content ("5 best", "10 top") | | useAlphabetSuffix | Boolean | false | Deep keyword mining, comprehensive A-Z coverage | | useAlphabetPrefix | Boolean | false | Alternative alphabet positioning | | usePrefix | Boolean | false | Add common prefixes ("best", "top", "how to") | | useSuffix | Boolean | false | Add common suffixes ("2025", "tutorial", "free") | ### Position Control (v0.4.0+) | Parameter | Values | Description | |-----------|--------|-------------| | alphabetPosition | "prefix" or "suffix" | Place letters before/after keyword | | numberPosition | "prefix" or "suffix" | Place numbers before/after keyword | | questionWordPosition | "prefix" or "suffix" | Place questions before/after keyword | ### Custom Lists | Parameter | Type | Description | |-----------|------|-------------| | customPrefixes | Array | Your own prefix list (replaces defaults) | | customSuffixes | Array | Your own suffix list (replaces defaults) | | customQuestionWords | Array | Your own question words (replaces language defaults) | ### Performance & Quality | Parameter | Type | Default | Description | |-----------|------|---------|-------------| | maxSuggestionsPerKeyword | Integer | 20 | Max suggestions per query (1-50) | | maxConcurrency | Integer | 3 | Parallel requests (1-10, higher = faster) | | requestDelayMs | Integer | 500 | Delay between requests (300-500 recommended) | | deduplicateResults | Boolean | true | Remove duplicate suggestions (recommended) | --- ## 📤 Output Format Each suggestion includes: json { "seed_keyword": "seo", "expanded_keyword": "how to seo", "suggestion": "how to seo optimize website", "position": 1, "expansion_type": "question", "expansion_term": "how to", "language": "en", "region": "US", "source": "google_autocomplete", "timestamp": "2025-12-12T10:30:00Z" } Download formats: JSON, CSV, Excel, HTML table --- ## 🌍 Multi-Language Support Built-in question words for: - English: how to, what is, why, where, when, who, which, can, should, does, will, how much, how many, best way to, is it - Chinese (Simplified): 什么是, 如何, 怎么, 为什么, 哪里, 哪个, 什么时候, 多少钱, 有哪些, 怎么样, 值不值得, 好不好 - Chinese (Traditional): 什麼是, 如何, 怎麼, 為什麼, 哪裡, 哪個, 什麼時候, 多少錢, 有哪些, 怎麼樣, 值不值得, 好不好 - Japanese: どうやって, なぜ, 何が, いつ, どこで, どれ, できる - Korean: 어떻게, 왜, 무엇이, 언제, 어디서, 어느, 할 수 있나요 Or define your own with customQuestionWords! --- ## 🔧 Integration Examples ### With n8n 1. Use the Apify node with "Run Actor" operation 2. Set Actor ID: your-username/google-autocomplete-scraper 3. Pass your keywords and configuration 4. Use another Apify node with "Get Dataset Items" to retrieve results 5. Process or store the data as needed ### With Make (Integromat) 1. Add Apify module → "Run Actor" 2. Configure with your Actor ID and input 3. Add "Get Dataset" module to fetch results 4. Connect to Google Sheets / Airtable / your CRM ### With Custom API bash curl -X POST https://api.apify.com/v2/acts/your-username/google-autocomplete-scraper/runs \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "keywords": ["seo tools"], "language": "en", "useQuestionWords": true }' --- ## 💡 Pro Tips ### Get More Results - ✅ Combine multiple expansion methods - ✅ Use specific seed keywords (not too broad) - ✅ Increase maxConcurrency for faster processing (8-10 for large jobs) ### Get Better Quality - ✅ Enable deduplicateResults (default: true) - ✅ Use custom prefixes/suffixes for your niche - ✅ Target specific languages/regions for local SEO ### Avoid Issues - ⚠️ Don't exceed 1000 total queries per run (automatic safety limit) - ⚠️ Use reasonable delays (300-500ms recommended) - ⚠️ Start small, then scale up --- ## 🚀 Version History - v0.4.1 (Latest) - Commercial positioning & marketplace optimization - v0.4.0 - Alphabet & Number prefix positioning control - v0.3.0 - Question words & number expansion with safety limits - v0.2.0 - Prefix/suffix/alphabet expansion with custom terms - v0.1.0 - Basic autocomplete scraping --- ## ⚙️ Technical Details - Uses official Google Autocomplete API (no HTML scraping) - Rate-limited to prevent blocking (configurable delays) - Automatic retry on temporary failures - Structured JSON dataset output with full metadata - Safety limits: max 1000 queries per run, 50 number range, 50 question words --- ## 🆘 Support & Contact - Email: For bug reports, feature requests, or any questions, contact me at 3294123368@qq.com - Documentation: Full guides at GitHub Repository --- ## 📝 License Apache-2.0 --- Made with ❤️ for SEO professionals, content marketers, and automation enthusiasts