yandex-wordstat

Yandex Wordstat MCP

Use this skill when the user asks for Russian-language keyword research, Yandex demand, seasonality, regional affinity, or query expansion.

Available tools

• get-regions-tree — free region hierarchy lookup.
• get-region-children — free region drill-down.
• top-requests — billed 30-day demand and associated queries.
• dynamics — billed daily/weekly/monthly history.
• regions — billed regional volume and affinity.

Workflow

1. Clarify the product, target geography, language, audience, and conversion goal.
2. Use get-regions-tree only when a region ID is unknown.
3. Start with top-requests using a small numPhrases value; expand only when useful.
4. Use Wordstat operators deliberately:
   • broad phrase for discovery;
   • quoted/exact forms for validation;
   • document the operator used alongside every count.
5. Use dynamics before interpreting spikes as stable demand.
6. Use regions when geography changes the business decision; compare volume and affinity separately.
7. Cluster phrases by search intent, not only lexical similarity.
8. Return a compact table with phrase, count, region, period/operator, intent, and recommended action.

Interpretation rules

• top-requests counts are Wordstat/Yandex demand signals for the reported period, not Google volume and not guaranteed clicks.
• Google Trends values are relative 0–100 indices and must never be presented as absolute searches.
• Regional affinity indicates overrepresentation relative to region size; it is not raw volume.
• A first-to-last trend percentage is only a summary. Inspect the full series for seasonality and outliers.
• Mention that GetTop and GetDynamics are billed at approximately 0.02 RUB per API request and regional distribution at approximately 0.05 RUB, based on the current Yandex Search API price page. Prices can change.

Cost discipline

• Prefer one well-scoped call over many speculative calls.
• Do not request 2000 phrases unless the user needs a bulk semantic core.
• The standard client guard is 10 requests/second and 100 requests/hour per folder.
• If a rate-limit error occurs, report the retry time instead of retrying in a loop.
• Never automatically retry top-requests, dynamics, or regions. After a timeout or unknown outcome, ask before making another paid attempt.
• Treat count fields as exact decimal strings; do not coerce them to JavaScript numbers.
• Use the free get-regions-tree operation for connectivity and release smoke tests.