Yandex Webmaster
Query your own live Yandex Webmaster data (search queries by device) through the RankParse API, for any query Yandex reports, not only the ones you track.
The /v1/yandex/* routes read the Yandex Webmaster API for the hosts your connected Yandex account has verified. Every call is a live request to Yandex, so it covers any query Yandex reports for the host, not only your tracked keywords. It is the Yandex counterpart of Google Search Console and answers in the same shape, with the same filters, sorting and period comparison.
Yandex Webmaster reports search queries for the whole host only. There is no page dimension and no country dimension in its API, so there is no "top pages" route for Yandex. Device types (desktop, mobile, tablet) are available. One read covers the first 1000 queries by impressions.
Operations
| Operation | Route | Calls Yandex |
|---|---|---|
| List properties | GET /v1/yandex/properties | Yes |
| Query search analytics | GET /v1/yandex/search-analytics | Yes |
| Get site summary | GET /v1/yandex/summary | Yes |
| Get diagnostics | GET /v1/yandex/diagnostics | Yes |
| Get indexing history | GET /v1/yandex/indexing | Yes |
| List external links | GET /v1/yandex/links | Yes |
| List sitemaps | GET /v1/yandex/sitemaps | Yes |
List properties
The hosts verified in your Yandex Webmaster account.
Query search analytics
Clicks, impressions, CTR and position by query or by day, optionally by device.
Get site summary
Site quality index, pages in search and problem counts.
Get diagnostics
The problems Yandex reports for the host, worst first.
Get indexing history
Pages downloaded by status, and pages in search, per day.
List external links
The links Yandex found to your host.
List sitemaps
The sitemaps Yandex knows.
Before you call
Connect Yandex Webmaster
In the RankParse dashboard open Settings, Connections and connect Yandex Webmaster. Sign in with the Yandex account that has the host verified. If the host is not in Yandex Webmaster yet, add and verify it there first.
List your properties
Call List properties to see the hosts the connection can read. You can also pass a bare host such as example.com as site: it is matched to the verified host, preferring https.
Query it
Call Query search analytics with site, startDate and endDate.
Authentication and cost
Send your API key in X-API-Key. These routes cost 0 credits and need a role that can read live provider data (owner, admin or member). The rate limit is 60 requests per minute per key, and each workspace is limited to 300 live Yandex reads in any rolling 24 hours (429 yandex_daily_cap_reached: do not retry, read the stored data with Get rankings instead).
Errors shared by every route
All errors use the standard shape { "error", "code", "message" }. See Errors.
| HTTP | Code | When |
|---|---|---|
| 400 | yandex_not_connected | Yandex Webmaster is not connected. The message says where to connect it. |
| 400 | yandex_data_not_ready | Yandex has not loaded or indexed this host yet, so it reports no data for it. Do not retry now. |
| 400 | unsupported_filter | You sent country, filterPage, filterPageContains or dimension=page, which Yandex does not report. |
| 401 | invalid_api_key | Missing, invalid or revoked API key. |
| 401 | yandex_token_expired | The Yandex connection needs to be reconnected, or Yandex rejected it. |
| 403 | capability_missing | Your role is client. |
| 403 | yandex_access_denied | Yandex denied access to this host for the connected account. |
| 404 | yandex_site_not_found | No verified host matches site. The response lists valid_properties. |
| 404 | yandex_query_not_found | A query trend was asked for a query that is not among the host's popular queries for those dates. |
| 429 | rate_limited | More than 60 requests per minute for this key. |
| 429 | yandex_quota_exceeded | Yandex is rate limiting the account. Check Retry-After. |
| 429 | yandex_daily_cap_reached | The workspace used its 300 live Yandex reads for the last 24 hours. |
| 502 | yandex_api_error | Yandex failed in another way, or the token could not be refreshed (yandex_token_refresh_failed). |
| 503 | token_refresh_in_progress | Another request was refreshing the token. Retry after Retry-After. |
| 504 | yandex_upstream_timeout | Yandex did not answer in time. Retry the same request. |
MCP tools
| Tool | Operation |
|---|---|
get_yandex_properties | List properties |
get_yandex_top_queries | Query search analytics |
get_yandex_date_trends | The same with dimension=date, the host's daily trend |
get_yandex_query_trend | The same with dimension=date and a filterQuery, one query's daily trend |
get_yandex_site_summary | Get site summary |
get_yandex_diagnostics | Get diagnostics |
get_yandex_indexing | Get indexing history |
get_yandex_external_links | List external links |
get_yandex_sitemaps | List sitemaps |
The tools are on the API-key MCP endpoint and on the full OAuth server (scope workspace:read). See MCP Server.