Tell your AI assistant which pages changed and it tells Bing, Yandex and the other IndexNow engines. The GSC Wizard MCP gives Claude, ChatGPT and any MCP-capable assistant the whole IndexNow workflow: create the key, check the key file, submit the URLs, read back what happened. It checks the setup before it sends, so a submission that would be thrown away is never reported as done.
Same connector endpoint: mcp.gscwizard.com
One submission, every participating engine
Bing + Yandex + Naver + Seznam
IndexNow engines share what they receive, so one call reaches all of them. indexnow.org also lists Yep, the Internet Archive and Amazonbot.
Google does not take part in IndexNow. For Google, the same connector inspects URLs and submits sitemaps through Search Console, so one assistant covers both.
Two read the setup and the history, two change things. Ask in plain language; the assistant runs them in the right order.
Whether the property has a key, shown only by its last four characters, and whether the key file is really reachable on the site, fetched live. When it is not, the answer names the exact file to publish.
get_indexnow_settings
Generates a valid key and returns the file to publish, or saves a key your site already uses and checks its file straight away. It never overwrites a working key: rotating means clearing the old one first, on purpose.
update_indexnow_settings
Up to 100 URLs per call, grouped by host. The key file on each host is checked before anything is sent, and every URL comes back with its response code and what that code means.
submit_indexnow_urls
Every submission for the property, newest first, up to 500 at a time: the URL, the response code, when it went out and whether it came from the app or from an assistant.
list_indexnow_submissions
IndexNow does not reach Google, so the Search Console tools handle that side: URL Inspection in bulk to see what Google has indexed, and sitemap submission.
A submission is only confirmed by what the engines do next. The Bing Webmaster tools on the same connector show Bing's crawl activity, and the Yandex Webmaster tools show the pages that entered Yandex's index each day.
IndexNow answers almost every submission with 202: accepted, key not validated yet. The engines fetch your key file later, and if it is missing they drop the whole batch without telling anyone. A tool that reports 202 as "submitted" lets a site with no key file pile up hundreds of successful-looking submissions that never reach Bing.
So the MCP fetches the key file first. If it is definitely missing, those URLs are not sent at all and the answer says which file to publish. Every response carries an outcome the assistant can act on:
A check that cannot reach a verdict, such as a timeout or a bot rule in front of the file, never blocks a submission that would have worked.
{
"siteUrl": "sc-domain:example.com",
"submitted": 2,
"failed": 0,
"outcome": "pending_key_validation",
"keyFile": [
{ "host": "www.example.com", "verified": true }
],
"submissions": [
{
"url": "https://www.example.com/pricing",
"responseCode": 202,
"status": "accepted, key validation pending",
"accepted": true
},
...
],
"message": "2 of 2 URL(s) sent were accepted
by IndexNow. Accepted means \"key validation
pending\", not delivered: ..."
}Type these into Claude, ChatGPT or any MCP client in your own words. It works on the same properties you already have in GSC Wizard.
"Is IndexNow set up for my site, and is the key file actually reachable?"
"Set up IndexNow for example.com and tell me exactly which file to upload, and where."
"Submit the twelve pages we updated today to IndexNow."
"Show this week's IndexNow submissions and flag anything that was rejected or held back."
"We fixed the broken product pages. Push them to IndexNow for Bing and Yandex, then inspect them in Google."
"My submissions all say 202 but nothing shows up in Bing. What is wrong?"
No key yet? The assistant can do all of it except the upload, which needs access to your site.
The assistant generates one for the property and gets back the file to publish: its name, its address and its contents. Already use IndexNow? Give it your existing key instead and it checks the file you already publish.
Upload a plain-text file named after the key, containing only the key, to the root of every host you will submit URLs for. For a domain property that can mean both example.com and www.example.com; the tool lists each address.
Ask whether IndexNow is ready. Once the key file checks out, submit URLs whenever pages change. You can do the same in the app, on the IndexNow page of a property, which also imports URLs from a sitemap or a file.
Setting a key and submitting are write actions: they need a read & write API key, or the write permission left ticked when you approve the connector. Read-only access can still check the setup and read the history. Works with Claude, ChatGPT, Gemini, Grok and any MCP-capable client; see the configs for every MCP client.
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. An IndexNow MCP gives the assistant the IndexNow protocol as tools, so it can set up the key for your site, check the key file is published, tell the participating search engines which URLs changed, and read back what happened to each submission.
IndexNow is shared between its participating engines, so one submission reaches all of them. indexnow.org lists Microsoft Bing, Yandex, Naver, Seznam and Yep, as well as the Internet Archive and Amazonbot. Google does not take part in IndexNow; for Google, the same connector runs URL Inspection and sitemap submission through Search Console.
No. 202 means IndexNow accepted the batch and has not validated the key yet. The engines fetch your key file afterwards and discard the whole batch without notice if it is missing or wrong. Even a validated submission is a hint to crawl, not a promise to index. The MCP reports a 202 as accepted with key validation pending, never as indexed.
Before sending anything, the MCP fetches the key file on each host in the batch. When the file is definitely missing or holds the wrong key, it does not send those URLs, because the engines would accept them and then drop them. The response says setup_incomplete and names the exact file to publish. An inconclusive check, such as a timeout or a bot rule, never blocks a submission.
No. Submissions are tied to a property in your GSC Wizard account, and any URL that is not on that property is dropped before a single request goes out, then listed in the response. The engines also check the key file on the host itself, so a key only works for sites where you can publish that file.
Setting a key and submitting URLs are write actions, so they need a read & write API key, or the write permission left ticked when you approve the connector. With read-only access the assistant can still check the IndexNow setup and read the submission history. On a property shared with you, a full-access invite is needed to submit.
MCP access is included in every GSC Wizard plan, and every new account starts with a 7-day free trial. IndexNow itself is free. See pricing.
The core of the server: clicks, impressions, rankings, decay and indexing, including URL Inspection in bulk.
Site quality index, queries and indexing history from Yandex, including the pages that entered and left its index each day.
Nine months of CrUX field data for LCP, INP and CLS, by device, with regressions flagged.
Track important URLs in Google every day and get alerts when pages drop out of the index.
Set up IndexNow, check the key file and submit changed URLs to Bing, Yandex and the rest, on the same connector as Search Console, without a 202 ever passing for "indexed".
Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.