# Keyword Research Tool · Google, YouTube, Amazon & More (`sauliusautomatesit/keyword-research-tool`) Actor

Turn seed keywords into thousands of real long-tail keyword ideas from the autocomplete of Google, YouTube, Amazon, Bing, eBay and DuckDuckGo. Bulk, multi-country, no API keys.

- **URL**: https://apify.com/sauliusautomatesit/keyword-research-tool.md
- **Developed by:** [Saulius Saulenas](https://apify.com/sauliusautomatesit) (community)
- **Categories:** SEO tools, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 keywords

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Keyword Research Tool · Google, YouTube, Amazon, Bing, eBay & DuckDuckGo

Turn a handful of seed terms into **thousands of real, long-tail keyword ideas** — pulled live from
the autocomplete of six major search engines, deduplicated, and ranked by cross-engine popularity.
No API keys, no monthly seat fees. Pay only for the keywords you get.

This is the pay-as-you-go, bulk, multi-engine alternative to tools like KeywordTool.io and
AnswerThePublic — built for SEO teams, content creators, Amazon/eBay sellers, PPC managers, and
automated content pipelines (n8n, Make, Zapier, MCP, AI agents).

### Why this actor

- **6 engines in one run** — Google, YouTube, Amazon, Bing, eBay, DuckDuckGo. Web SEO intent, video
  intent, and e-commerce buyer intent, side by side.
- **Real autocomplete data** — the exact "what people actually type" suggestions the engines serve,
  not made-up permutations.
- **Massive expansion** — each seed is grown with question words (who/what/how…), prepositions &
  modifiers (for/vs/best/cheap…), and A–Z / 0–9 variants to surface hundreds of long-tails per seed.
- **One clean row per keyword** — deduplicated across engines, with a **frequency** score (how many
  engine/query forms produced it), the best autocomplete **rank**, and Google's **relevance** signal.
- **Question detection** — instantly filter the question keywords that make great blog/FAQ/briefs.
- **Multi-country & multi-language** — localized suggestions per country (Amazon/eBay auto-map to the
  right marketplace).
- **Monitoring mode** — schedule runs and return **only newly-appearing keywords** via a persistent
  dedup store. Track emerging long-tails and trends over time.
- **No cookies, no login, no captchas.** Fast lightweight HTTP.

### Use cases

| You are a… | You use it to… |
|---|---|
| SEO / content marketer | Build topic clusters, find question keywords for briefs, expand a niche |
| YouTuber / video team | Discover what viewers search on YouTube for your topic |
| Amazon / eBay seller | Find buyer-intent product keywords & listing terms per marketplace |
| PPC manager | Mine long-tail positive & negative keywords across engines |
| Agency / SaaS builder | Power a keyword feature or content pipeline via the Apify API/MCP |

### Input

| Field | Type | Description |
|---|---|---|
| `keywords` | array | **Required.** Seed terms to expand (e.g. `coffee maker`, `crm software`). |
| `engines` | array | Any of `google`, `youtube`, `amazon`, `bing`, `ebay`, `duckduckgo`. |
| `modifiers` | array | `questions`, `prepositions`, `alphabet`, `alphabet_prefix`, `numbers`. |
| `includeSeed` | boolean | Also query the bare seed's own suggestions. Default `true`. |
| `country` | string | Two-letter country code (e.g. `us`, `gb`, `de`, `in`). |
| `language` | string | Two-letter language code (e.g. `en`, `de`, `fr`). |
| `matchType` | string | `any`, or `seed_included` (keyword must contain the seed). |
| `minLength` | integer | Drop suggestions shorter than N characters. |
| `maxKeywordsPerSeed` | integer | Cap keywords per seed (keeps the highest-ranked). `0` = no cap. |
| `dedupAcrossRuns` | boolean | Return only NEW keywords vs previous runs (monitoring). |
| `dedupStoreName` | string | Named store per watchlist for monitoring. |
| `concurrency` | integer | Parallel autocomplete requests (1–20). |
| `proxyConfiguration` | object | Apify Proxy recommended for geo-consistency. |

#### Example input

```json
{
  "keywords": ["coffee maker", "cold brew"],
  "engines": ["google", "youtube", "amazon"],
  "modifiers": ["questions", "prepositions"],
  "country": "us",
  "language": "en"
}
```

### Output

Each unique keyword is one dataset item:

```json
{
  "keyword": "which coffee maker is best",
  "seed": "coffee maker",
  "sources": ["google", "youtube"],
  "sourceCount": 2,
  "frequency": 5,
  "bestRank": 0,
  "relevance": 951,
  "isQuestion": true,
  "isSeed": false,
  "wordCount": 5,
  "characterCount": 26,
  "modifiers": ["questions"],
  "country": "us",
  "language": "en"
}
```

- **`frequency`** — how many engine/query forms surfaced this keyword. Higher = more broadly suggested
  (a strong relative popularity proxy).
- **`bestRank`** — best (lowest) position it held in any autocomplete list. `0` = top suggestion.
- **`relevance`** — Google's own relevance score when the keyword came from Google (higher = stronger).
- **`sources` / `sourceCount`** — which engines suggested it; keywords found by several engines are
  usually the most valuable.

A **run summary** (seeds, engines, calls made, unique keywords, keywords returned, skipped-as-seen) is
saved to the key-value store under `SUMMARY`.

### Pricing

Pay-per-event: you're charged per **unique keyword** returned (plus a small per-run start fee). No
monthly subscription, no seats. A typical single-seed run with the `questions` modifier across 3
engines returns a few hundred keywords. See the Pricing tab for the live per-event rate.

> Tip: use `maxKeywordsPerSeed` and `matchType: seed_included` to keep runs tight and costs predictable.

### FAQ

**Does this give exact monthly search volume?** No — Google/Amazon don't expose true volume without a
paid Ads account. Instead you get a robust **relative** popularity signal (`frequency`, `bestRank`,
Google `relevance`) that's ideal for prioritizing long-tails. This is the same autocomplete data that
powers popular paid keyword tools.

**How many keywords will I get?** Depends on seeds × modifiers × engines. One seed with `questions`
across 3 engines is typically ~300–600 unique keywords. Add `alphabet` for thousands.

**Which engines for which job?** Google/Bing/DuckDuckGo = web SEO; YouTube = video; Amazon/eBay =
e-commerce buyer intent.

**Can I monitor for new keywords?** Yes — set `dedupAcrossRuns: true` with a `dedupStoreName` and
schedule it. Each run returns only keywords not seen before.

### Limitations

- Autocomplete returns up to ~10–15 suggestions per query form; expansion (modifiers) is what scales
  coverage.
- Relevance scores are only provided by Google.
- Some engines geo-target by IP; use Apify Proxy with a matching country for best localization.

# Actor input Schema

## `keywords` (type: `array`):

One or more seed terms to expand into long-tail keyword ideas (e.g. `coffee maker`, `crm software`). Each seed is expanded with the chosen modifiers and sent to every selected engine's autocomplete.

## `engines` (type: `array`):

Which autocomplete sources to query. Google/Bing/DuckDuckGo = web SEO intent; YouTube = video/content intent; Amazon/eBay = e-commerce buyer intent.

## `modifiers` (type: `array`):

How to expand each seed for more long-tails. `questions` = who/what/how/… (great for content & SEO); `prepositions` = for/with/vs/best/cheap/…; `alphabet` = seed + a–z; `alphabet_prefix` = a–z + seed; `numbers` = seed + 0–9. More modifiers = more keywords and more autocomplete calls.

## `includeSeed` (type: `boolean`):

Also query the bare seed term itself (its direct autocomplete), not only the modified forms.

## `country` (type: `string`):

Two-letter country code for localized suggestions (e.g. `us`, `gb`, `de`, `in`). Applied to every engine that supports geo-targeting (Amazon/eBay map it to the matching marketplace).

## `language` (type: `string`):

Two-letter language code for suggestions (e.g. `en`, `de`, `fr`, `es`).

## `matchType` (type: `string`):

`any` keeps every suggestion returned. `seed_included` keeps only keywords that literally contain the seed term (tighter, more on-topic results).

## `minLength` (type: `integer`):

Drop suggestions shorter than this many characters (0 = keep all).

## `maxKeywordsPerSeed` (type: `integer`):

Cap the number of keywords returned per seed (0 = no cap, keep all unique suggestions). Keywords are ranked by cross-engine popularity, so the cap keeps the strongest ones.

## `dedupAcrossRuns` (type: `boolean`):

Skip keywords already returned by previous runs that share the dedup store below. Perfect for scheduled runs that surface only newly-appearing long-tails/trends.

## `dedupStoreName` (type: `string`):

Named storage used to remember keywords across runs. Use one distinct name per watchlist so histories don't mix.

## `concurrency` (type: `integer`):

Autocomplete requests made in parallel.

## `proxyConfiguration` (type: `object`):

Proxy settings. Apify Proxy (automatic) is recommended so requests are geo-consistent and not rate-limited.

## Actor input object example

```json
{
  "keywords": [
    "coffee maker"
  ],
  "engines": [
    "google",
    "youtube",
    "amazon"
  ],
  "modifiers": [
    "questions",
    "prepositions"
  ],
  "includeSeed": true,
  "country": "us",
  "language": "en",
  "matchType": "any",
  "minLength": 0,
  "maxKeywordsPerSeed": 0,
  "dedupAcrossRuns": false,
  "dedupStoreName": "keyword-research-dedup",
  "concurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `keywords` (type: `string`):

One item per unique keyword: the keyword, the seed it came from, which engines suggested it, a cross-engine frequency (popularity proxy), the best autocomplete rank, Google's relevance score when available, whether it is a question, and word/character counts.

## `summary` (type: `string`):

A JSON report: number of seeds and engines, query-forms per seed, autocomplete calls made, unique keywords found, keywords returned, keywords skipped as already-seen (monitoring), and whether the run stopped at your maximum charge limit.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "coffee maker"
    ],
    "engines": [
        "google",
        "youtube",
        "amazon"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sauliusautomatesit/keyword-research-tool").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["coffee maker"],
    "engines": [
        "google",
        "youtube",
        "amazon",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("sauliusautomatesit/keyword-research-tool").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "coffee maker"
  ],
  "engines": [
    "google",
    "youtube",
    "amazon"
  ]
}' |
apify call sauliusautomatesit/keyword-research-tool --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sauliusautomatesit/keyword-research-tool"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/5C1rYe2E4hoKJ6tUY/builds/xdKdnit6ZPt9vao5y/openapi.json