rowfeed/keyword-search-volume
rowfeed--keyword-search-volumeDestructive
This tool calls the Actor "rowfeed/keyword-search-volume" and retrieves its output results. Actor description: Keyword research tool and Keyword Planner alternative, no SEO subscription: bulk Google and Bing search volume, CPC, competition and 12-month trend, keyword difficulty, search intent and AI search volume (ChatGPT), or keyword ideas from seed words. No per-keyword fee for keywords without data.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | "Search volume" returns one row per keyword you enter. "Keyword ideas" returns related keywords Google Ads suggests for your seeds, sorted by search volume. Example values: "volume" | volume |
| keywords | No | In "Search volume" mode: the keywords to measure (thousands are fine; looked up 1,000 at a time). In "Keyword ideas" mode: seed words (up to 20 per lookup). Max 80 characters and 10 words each. Google Ads does not accept symbols like ! @ % , * ( ) or emoji, so such keywords are skipped with a warning row. Example values: ["web scraping","price tracking","keyword research","seo tools","lead generation"] | |
| language | No | Language name, e.g. "English", "German", "Spanish". Codes (de, fr, sk) and native names (Deutsch, Slovenčina) work too. Leave empty for all languages. Example values: "English" | English |
| location | No | Country, region or city as Google Ads names it, e.g. "United States", "United Kingdom", "Germany", "London,England,United Kingdom". Leave empty for worldwide (each batch then counts as 4 lookups, $0.16, instead of 1). Example values: "United States" | United States |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| maxResults | No | Keyword ideas mode only: stop after this many keyword rows (Google Ads can suggest up to 20,000 per lookup). Example values: 500 | |
| searchEngine | No | Search volume from Google (Google Ads data), Bing (Bing Ads data) or both. Keyword ideas are Google only. A Bing lookup counts as 3 lookups. Example values: "google" | |
| includeDifficulty | No | Also add keyword difficulty (0-100, how hard it is to rank in Google top 10) and search intent (informational, commercial, transactional, navigational) to every Google keyword with data. +2 lookups ($0.08) per started 100 keywords. | |
| includeAiSearchVolume | No | Also add AI search volume: how often each keyword is asked in AI assistants such as ChatGPT per month, with a 12-month series (Google keywords with data). +1 lookup ($0.04) per started 100 keywords. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |