IndexNow is an open protocol that lets your website tell participating search engines the moment a page is added, updated or deleted, so they don't have to wait for a crawler to stumble across the change. You submit the changed URL with a key you control, the engine verifies it, and the page is queued for a fresh crawl. It supports Bing, Yandex, Naver, Seznam.cz, Yep and Amazon. Google is not on that list. It's free, it takes about fifteen minutes on most sites, and it's worth doing, as long as you know what it can and can't do.
This guide covers how the protocol works, who supports it, how to set it up by hand or through a plugin, and how to check it's working. It also covers when it's a waste of effort. We build and maintain websites, apps and platforms for businesses across the UAE, so we've written this from the point of view of a team that has to make the technical decision, not just describe it.
TL;DR
- IndexNow is a ping protocol: you notify search engines when URLs are added, updated or removed, instead of waiting for them to re-crawl.
- Supported engines include Bing, Yandex, Naver, Seznam.cz, Yep and Amazon. Google does not appear on the official list, so keep your sitemap and Search Console routine.
- A submission is a notification, not a guarantee. It does not promise crawling, indexing or ranking.
- Setup needs a key of 8 to 128 characters and a matching .txt file on your domain. WordPress, Shopify, Wix and Drupal sites can usually skip the manual work.
- Submit only URLs that truly changed. Resubmitting unchanged pages wastes the goodwill of the system.
Table of Contents
- What IndexNow actually does
- Which search engines support IndexNow
- What IndexNow does not do
- How to set up IndexNow manually
- Setting it up with a plugin or platform
- When to submit URLs (and when not to)
- A worked example
- How to check that IndexNow is working
- Security and key hygiene
- Our perspective: treat it as plumbing, not a strategy
- Build it into your product from day one
- A short implementation checklist
- FAQ
- Sources
What IndexNow actually does
Traditional discovery is passive. A search engine crawls your site on its own schedule, finds that a page changed, and eventually updates its index. For a small site that can take days or weeks. IndexNow.org describes the protocol as a simple ping that lets site owners inform search engines instantly about content changes, so engines can prioritize crawling the changed URLs instead of relying only on exploratory crawling.
The protocol was created by Microsoft Bing and Yandex in 2021 with the stated aim of a more efficient and open internet. By August 2022, Bing reported more than 1.2 billion URL submissions per day, which tells you the protocol moved quickly from announcement to real infrastructure.
Three details matter in practice:
- It covers all change types. You notify the engines about new pages, edited pages and deleted pages. Removals are the underrated case: a discontinued product or an expired listing disappears from results faster when you tell engines it's gone.
- You only tell one engine. Participating engines must pass your submission to every other participant, except those that have unsubscribed, within 10 seconds of verifying the URLs. One ping reaches the whole network.
- It's a signal, not a command. The engine decides whether and when to crawl.
Which search engines support IndexNow
The official IndexNow FAQ lists Bing, Yandex, Naver, Seznam.cz, Yep and Amazon as participants. Google isn't among them. Google has no equivalent real-time submission feature for ordinary pages, so for Google you still rely on a clean XML sitemap, strong internal linking and the URL Inspection tool in Search Console for the occasional urgent page.
That shapes the business case. If most of your organic traffic comes from Google, IndexNow will not change that traffic. If you also care about Bing (which feeds several other products and search experiences), Yandex, or Naver, or you want your content discoverable by AI assistants that draw on Bing's index, it earns its place. Check your own analytics before deciding how much it matters to you. For many UAE sites, Bing is a minority source of visits but a very cheap one to improve.
| Question | Without IndexNow | With IndexNow |
|---|---|---|
| How do engines find a new page? | Crawl schedule, sitemap, links | You notify them directly, plus the usual methods |
| How do engines learn about a deletion? | Next crawl hits an error | You submit the removed URL |
| Effort | None | One-time key setup, then automatic |
| Effect on Google | None | None |
| Guarantee of indexing | No | No |
What IndexNow does not do
It's easy to oversell this protocol, and many guides do. Be clear about the limits:
- It doesn't guarantee indexing. Bing's own getting started page states that submitting a URL does not guarantee it will be crawled or indexed.
- It doesn't fix poor pages. Thin, duplicate or blocked pages stay thin, duplicate or blocked. A noindex tag still wins.
- It doesn't improve rankings by itself. Faster discovery is not better ranking. Quality, relevance and links still decide where you appear.
- It doesn't replace a sitemap. Keep your sitemap current. It's your complete inventory; IndexNow is your change feed.
If you want the wider picture of how engines decide what to store, this overview of how search engine indexation works explains why a page can be crawled and still not indexed, which is the most common confusion we see after teams enable IndexNow.
How to set up IndexNow manually
If your platform has no plugin, the manual route is short. It has three parts: a key, a key file and a submission.
Step 1: Generate a key
The IndexNow FAQ says the key must be 8 to 128 characters and may contain letters, numbers and hyphens. Use a random string, not a word. Bing Webmaster Tools also offers a key generator on its IndexNow page.
Step 2: Host the key file
Create a UTF-8 text file named after the key, with the key as its only content. If your key is a1b2c3d4e5f6g7h8, the file is a1b2c3d4e5f6g7h8.txt and it contains a1b2c3d4e5f6g7h8. Upload it to your site root, or another publicly accessible folder, and open its public URL in a browser to confirm it loads. The engine will fetch this file to prove you control the domain.
If you put the file anywhere other than the root, you must tell the engine where it is with a keyLocation parameter, and the submitted URLs must sit under that folder.
Step 3: Submit a URL
For a single page, the IndexNow documentation describes a plain HTTP request to the engine's /indexnow endpoint with your URL and key. It looks like this:
https://api.indexnow.org/indexnow?url=https://www.example.com/new-page&key=a1b2c3d4e5f6g7h8
For many pages at once, send a POST request with a JSON body containing your host, key, key location and a list of URLs. This is the right choice after a migration, a catalog update or a bulk deletion, because one request replaces hundreds of individual pings. The documentation sets the batch size limit, so check it before scripting large jobs.
Step 4: Read the response
Per the FAQ, HTTP 200 means the submission was received successfully. Your very first request may return HTTP 202 while the engine validates your key. That's normal, not an error. Anything else usually points to a key file that isn't reachable, a key that doesn't match the filename, or URLs that don't belong to the host you declared.
Setting it up with a plugin or platform
Most teams shouldn't touch the manual route. According to the FAQ, major platforms such as WordPress, Shopify, Wix and Drupal offer native IndexNow integration or supported plugins, which removes the key-file work. Common patterns:
- WordPress: SEO plugins such as SEOPress and All in One SEO include IndexNow settings. Enable them and the plugin generates the key, hosts the file and pings on publish and update.
- Shopify and Wix: check your store or site settings for the integration before adding anything custom.
- Custom stacks: add a small hook to your deploy pipeline or CMS "publish" event that posts the changed URLs. This is a few dozen lines in most languages.
If you're choosing a platform and care about how well it handles technical SEO, our comparison of WordPress vs Webflow for UAE projects covers the tradeoffs by project type.
When to submit URLs (and when not to)
The rule from the IndexNow FAQ is simple: notify when content is added, updated or removed, and don't resubmit URLs that haven't changed. Translate that into habits:
- Submit: new articles, product pages, edited prices or stock status, changed titles or major copy, redirected URLs, deleted pages.
- Don't submit: unchanged pages on a schedule, whole sitemaps every night, URLs you've blocked with robots.txt or noindex, parameter-heavy duplicates.
Over-submission is the most common mistake. It adds noise, and engines can learn to treat a noisy source as less reliable. An automated ping that fires only on a real publish or edit event is the cleanest design.
A worked example
Take an online store with 3,000 product pages. On Monday the team changes the price and availability on 120 products and removes 15 discontinued items.
Without IndexNow, engines notice the changes gradually as their crawlers revisit pages, and shoppers may see stale prices in results for a while. With IndexNow, the store's backend sends one POST request listing the 135 affected URLs. The engine verifies the key, passes the notification to its partners, and queues those URLs for recrawl. The other 2,865 pages aren't touched. Nothing is guaranteed, but you've given every participating engine the most accurate, targeted signal you can.
This is also where integration quality matters. A ping triggered from the product database is far more reliable than a person remembering to submit URLs. If your store or platform needs that kind of automation wired to its backend, it belongs in the same conversation as your third-party API integrations.
How to check that IndexNow is working
Verification takes three checks:
- Key file. Open the key file's public URL. It should load as plain text with only the key.
- Response codes. Log the HTTP response of each submission. 200 is success; a first-time 202 is expected while the key is validated.
- Bing Webmaster Tools. The IndexNow section shows the URLs you've submitted and how they were handled. Compare it with the URL Inspection report to see whether submitted pages were crawled.
If pages are submitted successfully but never appear, the problem is almost never IndexNow. Look at canonical tags, noindex directives, thin content, slow rendering and crawl blocks. Our guide to Core Web Vitals optimization covers the performance side, and our 90-day SEO plan covers the content and authority work that decides what actually ranks.
Security and key hygiene
The key is not a password, because it sits in a public file by design. Its job is to prove that whoever submits URLs for your host also controls the host. Two practical rules follow. Only submit URLs from the host the key file lives on, and rotate the key by uploading a new file if you suspect misuse. Between engines, the protocol adds its own safeguards: the documentation for search engines describes public and private key verification and signed digests so that engines can trust the URL lists they pass to each other.
If your submission code runs from a server, treat it like any other API client: keep credentials out of front-end code, log failures, and rate-limit your own calls. Our checklist of API security controls maps those habits to the API lifecycle.
Our perspective: treat it as plumbing, not a strategy
We'd put IndexNow in the same category as a sitemap or a clean robots.txt: invisible infrastructure that should be set up once, automated and then forgotten. It isn't a growth lever on its own. We see teams spend a week debating it while their pages load in five seconds, their templates duplicate content and their product data is out of date. Fix those first.
Once the fundamentals are sound, though, the case for IndexNow is strong, because the cost is close to zero. The best implementation is the one nobody has to remember. We wire the ping into the publish and update events of the CMS or backend we build, so a price change, a new listing or a deleted page notifies engines without anyone lifting a finger. For UAE businesses that run bilingual catalogs, frequently changing listings or fast-moving campaigns, that automation removes a whole class of stale-result problems.
We also think it belongs in a broader discovery strategy. Search is no longer only ten blue links, and being found by AI assistants depends on being indexed accurately and quickly by the engines behind them. Our notes on AI search optimization go deeper on that. Our UAE-based team builds these hooks into the products we deliver, from web platforms to mobile backends, because we'd rather ship a system that stays current by itself.
— Amal
Build it into your product from day one
If you're commissioning a new website, web application or platform in the UAE, automatic search notification should be part of the specification, next to sitemaps, structured data and performance budgets. Retrofitting it later means touching publishing logic that's already in production.
We design and build business websites and custom web applications with a fully UAE-based team, and our published starting prices are $8,000 for a professional business website and $25,000 for a custom web application with backend, database and admin panel. Tell us what your platform needs to publish, update and retire, and we'll scope the technical SEO plumbing with it. If search visibility is the larger goal, our AI SEO and GEO team in Dubai can help with the strategy around it.
A short implementation checklist
- Confirm that Bing, Yandex or Naver matter to your audience, using your analytics.
- Use your platform's native integration if it has one; otherwise generate a key and host the key file.
- Test the key file URL in a browser.
- Trigger submissions from real publish, edit and delete events, never on a timer.
- Batch large changes into a single POST request.
- Log response codes, expecting 200, and a 202 on the first call.
- Keep your XML sitemap current and keep using Search Console for Google.
- Review Bing Webmaster Tools monthly for errors.
FAQ
Does Google support IndexNow?
No. Google is not among the engines listed in the official IndexNow FAQ, which names Bing, Yandex, Naver, Seznam.cz, Yep and Amazon. For Google, keep a current XML sitemap, link new pages internally and use the URL Inspection tool in Search Console for urgent pages.
Does IndexNow guarantee my page will be indexed?
No. A submission is a notification that a URL changed, and the search engine decides whether to crawl and index it. Bing states this plainly on its IndexNow getting started page. Content quality, technical accessibility and site authority still determine the outcome.
Is IndexNow free, and do I need a developer?
The protocol is free to use. If you run WordPress, Shopify, Wix or Drupal, a native integration or plugin usually handles the key and submissions for you. A developer helps when you have a custom platform, because the submission should fire automatically from your publishing or database events.
What does an HTTP 202 response mean?
It usually means the engine received your request but is still validating your key, which can happen on the first submission. HTTP 200 means the submission was processed successfully. If you keep getting errors beyond the first request, check that the key file is reachable and its name matches the key.
Should I submit my whole site every day?
No. Submit only URLs that were added, updated or deleted. Resubmitting unchanged pages adds noise without benefit, and the official guidance is to avoid it.
Sources
- IndexNow.org home page
- IndexNow FAQ
- IndexNow documentation
- IndexNow documentation for search engines
- Bing Webmaster Blog: IndexNow announcement, 2021
- Bing Webmaster Blog: IndexNow adoption gains momentum, 2022
- Bing: How to add IndexNow to your website
- What Is Search Engine Indexation: 2026 SEO Guide