Skip to Content
Yandex Webmaster

Get indexing history

Pages Yandex downloaded per day by HTTP status, and the number of pages in Yandex search per day.

GEThttps://api.rankparse.com/v1/yandex/indexingFreeAPI key + connected Yandex account

How Yandex's crawl and index of your host move over a date range. Two dated series come back together: the pages Yandex downloaded each day by HTTP status class, and the number of pages in search each day. A fall in in_search with a rise in HTTP_4XX or HTTP_5XX points at a crawl problem.

Query parameters

sitestringrequired

The host, as returned by List properties, or a bare host or URL such as example.com, which is matched to a verified host (https first, www ignored). A host with no match returns 404 yandex_site_not_found with valid_properties. Missing returns 400 missing_site.

startDatestringrequired

First day, YYYY-MM-DD. Missing returns 400 missing_dates; any other format returns 400 invalid_date.

endDatestringrequired

Last day, YYYY-MM-DD; not before startDate.

Response

sourcestring

yandex.

sitestring

The website that was read.

requested_sitestring

Present only when your site was matched to a different website; site then holds the one used.

downloadedobject

An object keyed by status class, HTTP_2XX, HTTP_3XX, HTTP_4XX, HTTP_5XX and OTHER (only the ones Yandex sends), each an array of { date, value }: the pages downloaded that day.

in_searcharray

{ date, value } for each day: the number of pages in Yandex search.

notestring

What each series holds.

Behavior and limits

  • Credits: 0. Counts toward the daily cap of 300 live Yandex reads per workspace (one read, two Yandex requests).

Errors

See the shared errors. Parameter errors are 400 with the codes named above.

MCP tool: get_yandex_indexing.