# Google Trends & Autocomplete Keyword Research - 12 Countries (`myceworks/multi-country-demand-signals`) Actor

Keyword research for 12 countries in one run: Google Trends 12-month interest, long-tail autocomplete keywords from Google, YouTube, Amazon, Bing, Naver, Yahoo Japan and Baidu, plus a search intent breakdown (free, buy, bulk, how-to, compare, tool). No search volumes.

- **URL**: https://apify.com/myceworks/multi-country-demand-signals.md
- **Developed by:** [Gyuni](https://apify.com/myceworks) (community)
- **Categories:** SEO tools, E-commerce
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.50 / 1,000 keyword signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Google Trends & Autocomplete Keyword Research (12 Countries)

Type one keyword. For every country you choose, get:

- **Autocomplete tails** from the search boxes people actually use there — Google, Bing, YouTube, Amazon (US/JP), Naver (KR), Yahoo! JAPAN (JP), Baidu (CN)
- **Buyer-intent breakdown** of those tails: `free`, `buy`, `bulk`, `howto`, `compare`, `tool`, `other` — with up to five examples each
- **Google Trends** 12-month interest for the keyword in that country (optional)

Use it before you build or stock something: a tail full of "free" means people want it free; tails with "price", "best", "bulk", "批量", "一括", "일괄" mean someone is ready to pay.

### Use cases

- **Before you build a product or tool** — see whether people in a country add "free", "price" or "bulk" after your keyword.
- **Picking a market** — run the same idea in each country's own language and compare the intent mix (not the Trends numbers).
- **Content and SEO briefs** — the `howto` and `compare` tails are ready-made article and video topics.
- **Marketplace sellers** — Amazon (US/JP) and Naver/Yahoo! JAPAN tails show how shoppers phrase the product.

### Example output (shortened)

```json
{
  "keyword": "invoice template",
  "country": "US",
  "suggestionCount": 23,
  "intentShare": {"free": 0.348, "buy": 0.0, "bulk": 0.0, "howto": 0.0, "compare": 0.0, "tool": 0.043, "other": 0.609},
  "topBuyTails": [],
  "trends": {"first4w": 69.0, "last4w": 46.5, "mean12m": 73.7, "scale": "relative 0-100 within this country; not comparable across countries"}
}
```

Real run on 2026-10-07. Reading: a third of US tails ask for "free" and none show buying words — a free tool or lead magnet fits better than a paid template here.

### FAQ

**Is this search volume?** No. It tells you *what* people type and *what they want*, not how many. Pair it with a volume tool if you need counts.

**How much does a run cost?** One keyword in three countries = 3 results = $0.015 on the free plan. Paid Apify plans get Store discounts: $4.50 (Starter), $4.00 (Scale) and $3.50 (Business) per 1,000 results. Pairs where every source failed are free.

**Is there a ready-made example?** Yes — [Keyword demand in English-speaking markets](https://apify.com/myceworks/multi-country-demand-signals/examples/english-markets-keyword-demand) runs two keywords across the US, UK, Canada, Australia and India.

**Can I schedule it?** Yes — use Apify Schedules and get a fresh snapshot every week.

### Input

```json
{
  "keywords": ["invoice template", "請求書 テンプレート"],
  "countries": ["US", "JP"],
  "includeTrends": true
}
```

Write each keyword in the language people search in that country. Supported countries: US, GB, CA, AU, IN, KR, JP, DE, FR, ES, BR, CN.

### Output (one item per keyword × country)

| Field | Meaning |
|---|---|
| `keyword`, `country` | What was checked |
| `suggestionCount` | Unique autocomplete tails across sources (the seed itself excluded) |
| `intentCounts`, `intentShare` | Tails per intent, and share of all tails. A tail can match more than one intent |
| `intentExamples`, `topBuyTails` | Example tails per intent |
| `suggestions` | Raw tails per source |
| `sourceErrors` | Sources that failed this time. Failures are shown, never hidden |
| `trends` | `first4w`, `last4w`, `mean12m` on Google's 0-100 scale **within that country** — do not compare countries with it. Includes the Google Trends attribution |

### Pricing

Pay per result: one **keyword-signal** event per keyword × country. Apify also adds its standard **actor start** fee of $0.00005 per run (once per GB of memory; default runs use 256 MB), which covers the first seconds of compute. You are **not charged** when every autocomplete source fails for that pair. The run stops when your spending limit is reached.

### Limits — read before you rely on it

- Autocomplete shows what people type, not how many. There are no search volumes here.
- Google Trends values are relative and may be rate-limited; when that happens the field says so.
- Intent words are a fixed multilingual list. Tails it does not recognise fall into `other`.
- Sources are public search-box suggestion endpoints and can change without notice.

Data source for trend values: Google Trends (https://www.google.com/trends).

Not affiliated with, endorsed or sponsored by Google, Microsoft, Amazon, Naver, LY Corporation (Yahoo! JAPAN) or Baidu. Their names are trademarks of their owners, used here only to describe the public data sources.

# Actor input Schema

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

Seed keywords. Write each in the language people search in that country (e.g. 'invoice template' for US, '請求書 テンプレート' for JP).

## `countries` (type: `array`):

ISO country codes. Supported: US, GB, CA, AU, IN, KR, JP, DE, FR, ES, BR, CN.

## `includeTrends` (type: `boolean`):

Adds 12-month Google Trends interest for the keyword in each country (relative 0-100 within that country). Slower, and Google may rate-limit; failures are reported, not charged differently.

## Actor input object example

```json
{
  "keywords": [
    "invoice template"
  ],
  "countries": [
    "US"
  ],
  "includeTrends": true
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `full` (type: `string`):

No description

# 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": [
        "invoice template"
    ],
    "countries": [
        "US"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("myceworks/multi-country-demand-signals").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": ["invoice template"],
    "countries": ["US"],
}

# Run the Actor and wait for it to finish
run = client.actor("myceworks/multi-country-demand-signals").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": [
    "invoice template"
  ],
  "countries": [
    "US"
  ]
}' |
apify call myceworks/multi-country-demand-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,myceworks/multi-country-demand-signals"
        }
    }
}
```

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/5vZGsJwrfP4JeVqJc/builds/B6viKueJKhOE77RhH/openapi.json