Use this when the user asks which searches bring their site visitors from Yandex: Yandex Webmaster queries for a property, with impressions, clicks, average impression position and average clicked position. IMPORTANT COVERAGE LIMIT: Yandex exposes only its top queries for the period (at most 3,000), so totals from these rows are a floor, not a complete figure, and any share is of the listed queries, not of the site; say so when reporting them. Yandex serves 500 rows per request and this tool pages through as many as `limit` allows, defaulting to the first 500 by `orderBy`, sorted by that metric, highest first; `totalAvailable` and `truncated` say how much of the pool was left. CTR is a percentage (0-100, like every other CTR this server returns), calculated from impressions and clicks because Yandex publishes no CTR metric; null when there were no impressions. Yandex has no query-by-page report, so these queries cannot be attributed to URLs. Not for Google or Bing queries: use query_top_queries or get_bing_query_stats. The dates select a real window, so a longer range returns more queries and larger totals; omitting them gives the last week only. Yandex finishes a day about four days late, so `range` echoes the window it actually served. The full set of caveats is in `limitations` on every response. Returns notConfigured: true (with a `reason`) when no Yandex account is connected, the connection has to be granted again, the property is not in it, or the caller holds a share of the property rather than owning it: Yandex data is owner-only.