Part of the GSC Wizard MCP

Yandex Webmaster SEO MCP

Ask your Yandex Webmaster data in plain language and get real numbers, with Yandex's caveats attached. The GSC Wizard MCP gives Claude, ChatGPT and any MCP-capable assistant your live site quality index, queries, clicks, positions and indexing history from Yandex, on the same connector as your Google Search Console and Bing data.

Same connector endpoint: mcp.gscwizard.com

One connector, three search engines

Google + Bing + Yandex

The Yandex tools live on the same MCP as the Search Console and Bing Webmaster tools. Your assistant can ask how a property does in Google and in Yandex in one conversation, which is worth having if you get traffic from Russia, Turkey, Kazakhstan, Belarus or Uzbekistan.

The Yandex tools read Yandex Webmaster live, through your own Yandex connection. The model reads the numbers, it does not invent them.

Which Yandex data the MCP can read

Four read tools cover Yandex Webmaster, and one write tool tells Yandex when pages change. Ask in plain language; the assistant picks the right tool.

Sites & verification

The sites in your Yandex Webmaster account, with their verification status and the canonical mirror Yandex resolved for each, so the assistant knows which properties have Yandex data before it asks.

list_yandex_sites

Site quality & problems

Yandex's site quality index (SQI), pages in search, excluded pages, and the problems Yandex currently reports against the site, by severity.

get_yandex_site_summary

Search queries

The queries Yandex reports for the window you choose, with impressions, clicks, CTR and both of Yandex's position metrics, filterable by device. Yandex serves 500 rows per request; the tool pages through its pool of up to 3,000.

get_yandex_query_stats

Indexing history

The HTTP status codes Yandex's crawler received by day, how many pages are in Yandex search, and how many pages appeared in or were removed from the results each day.

get_yandex_indexing_history

Push changes with IndexNow

Tell Yandex (and Bing and Seznam) that pages changed, up to 100 URLs per call. A write tool, so it needs a read & write key and an IndexNow key on the property. A 202 means accepted, not indexed.

submit_indexnow_urls

Google and Bing alongside

The same assistant can call the Search Console and Bing Webmaster tools for the property, so it can set the Yandex side next to the other two. It compares trends and query lists; it never averages a Yandex position with a Google one.

Honest numbers

Yandex's caveats travel with the data

Yandex publishes much less than Google, and the gaps change how its numbers must be read. They are not gaps GSC Wizard can close: the data is not in Yandex's API. So every Yandex tool response carries a limitations list, written once and shared with the app's Yandex reports, and the assistant passes it on instead of presenting a floor as a total.

  • Query totals are a floor. Yandex returns its top queries for the period, at most 3,000, so sums of the rows understate real traffic.
  • No queries by page. Yandex has no report joining queries to URLs, so its queries cannot be attributed to pages.
  • CTR is calculated. Yandex publishes no CTR, so it is derived from impressions and clicks (0-100, like every CTR the server returns).
  • Two positions, neither Google's. Average position when shown and when clicked, measured Yandex's way.
  • No country, no comparison. There is no country dimension, device is a request filter, and Yandex serves no previous-period series.
  • About four days behind. Yandex finishes a day later than Google, so the tool echoes the range it actually served.
  • Whole hosts. A property with a path is matched to its host, and the response says so when that applies.
get_yandex_query_stats · response, trimmed example data
{
  "siteUrl": "https://example.com/",
  "range": { "startDate": "2026-09-09", "endDate": "2026-10-06" },
  "totalAvailable": 2140,
  "truncated": true,
  "queries": [
    {
      "query": "koşu ayakkabısı",
      "impressions": 4210,
      "clicks": 388,
      "ctr": 9.22,
      "avgImpressionPosition": 3.1,
      "avgClickPosition": 2.4
    },
    ...
  ],
  "limitations": [
    "Yandex returns only its top queries for the
     period, at most 3,000 of them. ...",
    "Yandex publishes no CTR metric. CTR here is
     calculated from impressions and clicks.",
    "Yandex has no query-by-page report, ...",
    ...
  ],
  "dataSource": "yandex"
}

The default is the first 500 queries; totalAvailable and truncated tell the assistant how much of the pool it has not read yet.

Only in Yandex

Watch pages enter and leave the index, day by day

Yandex reports, every day, how many of your pages appeared in its search results and how many were removed. Google Search Console has no equivalent. Through the MCP, your assistant can find the days a batch of pages dropped out, line them up with the crawl response codes for the same days, and tell you whether it was a server problem or a quality call.

For the same question on Google, the Search Console tools run URL Inspection in bulk; see the Google Search Console MCP.

Appeared in search Removed from search Illustrative data, 14 days

A few things you can ask it

Once Yandex is connected, type these into Claude, ChatGPT or any MCP client in your own words. It reads from the same properties you already have in GSC Wizard.

"How is my site doing in Yandex? Give me the site quality index, pages in search and any problems Yandex is reporting."

"Which Yandex queries brought the most clicks in the last 28 days, and where do they rank when they get clicked?"

"Did Yandex drop pages from its index this month? Show the days with the most pages removed from search and the crawl responses on those days."

"Which queries get clicks in Yandex but barely show up in Google Search Console for the same site?"

"Is Yandex's crawler hitting errors? Break down the 4xx and 5xx responses it got by day for the last month."

"Submit the pages I updated today to IndexNow so Yandex and Bing recrawl them."

Setup

Connect Yandex in a few minutes

1

Verify the site in Yandex Webmaster

Yandex only reports on sites already added and verified in Yandex Webmaster itself. A newly verified site can take a few days before Yandex has data to show.

2

Connect Yandex in GSC Wizard

Open Account settings and click Connect Yandex Webmaster. Yandex has no read-only permission that returns data, so its consent screen also mentions adding and verifying sites. GSC Wizard only issues read calls with it and never adds, verifies or removes a site.

3

Ask your first Yandex question

Add mcp.gscwizard.com as a connector in your AI assistant (or paste an API key). If Yandex is not connected yet, or the connection has to be granted again, the tools answer with a short notConfigured note and the reason instead of an error.

Works with Claude, ChatGPT, Gemini, Grok and any MCP-capable client; see the configs for every MCP client. Yandex data is read with the property owner's connection, so on a property shared with you the Yandex tools answer with an owner-only note for now.

Frequently asked questions

What is a Yandex Webmaster MCP?

An MCP (Model Context Protocol) server is a standard connector that lets an AI assistant such as Claude or ChatGPT read live data and call tools. A Yandex Webmaster MCP exposes your Yandex Webmaster account to the assistant, so it can pull your real site quality index, queries, clicks, positions and indexing history from Yandex instead of guessing them.

Which Yandex data can the MCP read?

Four read tools cover Yandex Webmaster: the sites in your Yandex account with their verification status and canonical mirror; a site summary with the site quality index (SQI), pages in search, excluded pages and the problems Yandex currently reports; search queries with impressions, clicks, CTR and two position metrics; and an indexing history with the crawl response codes Yandex received by day, pages in search, and the pages that appeared in or were removed from Yandex search each day. A separate write tool submits changed URLs to IndexNow, which Yandex takes part in.

Why do Yandex query totals look lower than my real Yandex traffic?

Yandex returns only its top queries for a period, at most 3,000 of them. GSC Wizard fetches the whole pool, but the long tail below that cut-off is absent from the Yandex API, so any total summed from the query rows is a floor, not a complete figure. Every Yandex tool response carries this and the other Yandex caveats in a limitations list, so the assistant reports the numbers with the caveat attached.

What permission does the Yandex connection need?

Yandex publishes no read-only permission that returns data: the permission that unlocks queries, indexing and site quality is the same one that covers adding and verifying sites, so the Yandex consent screen says so. GSC Wizard only issues read calls with it and never adds, verifies or removes a site. You can withdraw the permission at any time from your Yandex account.

Does it work on properties that are shared with me?

Not yet. Yandex data is read with the property owner's Yandex connection, and that connection is not shared with invited users. On a shared property the Yandex tools answer with a short owner-only note instead of an error. The Search Console, Bing and GA4 tools on the same connector follow their own sharing rules.

Do I need a subscription?

MCP access is included in every GSC Wizard plan, and every new account starts with a 7-day free trial. Yandex Webmaster support is available on every plan that includes reports. See pricing.

The rest of the connector

Put Yandex next to Google in your AI assistant

Site quality, queries and indexing history from Yandex Webmaster, on the same connector as Search Console and Bing, with Yandex's own caveats attached.

Search Console tips in your inbox

Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.