Ubersuggest Keyword Suggestions by Country & Language: MCP config, n8n workflow and API

{
  "keywords": [
    "coffee"
  ],
  "country": "us",
  "language": "en",
  "autoMatchLanguageToCountry": true,
  "sortBy": "-searchVolume",
  "maxSuggestionsPerSeed": 1,
  "maxItems": 1,
  "includeSeedOverview": false,
  "outputFormat": "perSeed"
}

---
name: ubersuggest-keyword-suggestions-by-country
description: "Ubersuggest keyword suggestions with search volume, CPC, competition, difficulty and intent, plus optional seed overviews. Runs the Apify Actor dataspryva/ubersuggest-keyword-suggestions-by-country. Use when the user needs Ubersuggest data with fields such as type, keyword, country, language, suggestions, seedOverview and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/ubersuggest-keyword-suggestions-by-country"
  store-url: "https://apify.com/dataspryva/ubersuggest-keyword-suggestions-by-country"
---

# Ubersuggest Keyword Suggestions by Country & Language

Use this skill to fetch Ubersuggest data with the Apify Actor `dataspryva/ubersuggest-keyword-suggestions-by-country` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `keywords` | array | Keywords to expand. Each seed returns its own suggestions. Add several to research a topic. |
| `urls` | array | Optional domains or URLs converted into rough keyword seeds (make.com becomes make). This is not a domain keyword report; use the keywords field for real research. |
| `country` | string | Market for the suggestions. `worldwide` returns the global list. Russia and Belarus are not available from the source. |
| `language` | string | Language of the suggestions. Leave English with auto-match on to use the market's main language automatically. |
| `autoMatchLanguageToCountry` | boolean | When language is English and the chosen market has another main language, switch to it automatically (Germany to German, Japan to Japanese). Turn off to keep English. |
| `sortBy` | string | Order of the suggestion list. |
| `maxSuggestionsPerSeed` | integer | Maximum suggestions returned for each seed. The default keeps runs fast; raise it for deep keyword lists. |
| `maxItems` | integer | Maximum suggestions across all seeds in one run. |
| `includeSeedOverview` | boolean | Fetch each seed's own metrics: search volume, CPC, competition, difficulty, intent, 4-month trend, global volume and device shares. Adds one request per seed. |
| `outputFormat` | one of `perSeed`, `perSuggestion` | One record per seed with nested suggestions (legacy), or one flat record per suggestion. |

Example `input.json` (the Actor's published prefill):

```json
{
  "keywords": [
    "coffee"
  ],
  "country": "us",
  "language": "en",
  "autoMatchLanguageToCountry": true,
  "sortBy": "-searchVolume",
  "maxSuggestionsPerSeed": 1,
  "maxItems": 1,
  "includeSeedOverview": false,
  "outputFormat": "perSeed"
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~ubersuggest-keyword-suggestions-by-country/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~ubersuggest-keyword-suggestions-by-country/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `type`, `keyword`, `country`, `language`, `suggestions`, `seedOverview`, `scrapedAt`, `seedKeyword`, `searchVolume`, `cpc`, `seoDifficulty`, `paidDifficulty`, `searchIntent`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.