Yandex Queries

What you get

• A line saying how many queries Yandex served and for which dates, and how many it says are available when the list was cut.
• A Queries table with Query, Impressions, Clicks, CTR, Avg. position and Avg. clicked position, sorted by impressions.
• The top 25 rows, with a button to show them all, plus copy and CSV export. The CSV filename carries the range Yandex actually served.
• What Yandex does not report: the caveats that apply to this page.

How to use it

1. Open a property, expand ANALYTICS, click Yandex Overview, then Yandex Queries.
2. Pick a device and a date range. A longer range returns more queries and larger totals.
3. Sort by any column. Avg. position is where the site was shown, and Avg. clicked position is where the results that were clicked sat.

Controls

• A device filter: All devices, Desktop, Mobile or Tablet.
• The date range. There is no comparison period.
• Sortable columns, show all rows, copy, and CSV export.

Data source and freshness

• Read live from the Yandex Webmaster API. Yandex serves 500 queries per request, so the report walks the whole pool, up to 3,000 queries, ordered by impressions.
• Cached for 60 minutes per property, date range and device.
• Yandex finishes a day about four days behind, so the end of the range is pulled back to the last finished day, and the report shows the range Yandex actually served.

Limits

• Yandex returns only its top queries for the period, at most 3,000. The long tail below that is absent from its API, so any total derived from these rows is a floor, not a complete figure.
• Yandex publishes no CTR metric. CTR here is calculated from impressions and clicks.
• Yandex positions are measured differently from Google’s. Never average a Yandex position together with a Google one.
• Yandex has no query-by-page report, so its queries cannot be attributed to URLs.
• There is no country dimension, and each device choice is a separate request to Yandex.