IndexNow for Small Businesses: Notify Bing After Publishing

Set up and verify an IndexNow publishing workflow, interpret response codes and distinguish submitted URLs from crawled and indexed pages.

Publisher checking a website release in an emerald studio

Key questions at a glance

What does IndexNow do?

It sends participating search engines a notification when a URL is added, updated or deleted.

Does a successful request mean Bing indexed the page?

A successful response confirms submission. Crawling and indexing are separate stages to check later.

Where should the key file live?

The protocol recommends placing it at the root of the same host as the submitted URLs. Alternate key locations have scope rules.

Notify the search engine after the change is live

IndexNow lets a publisher tell participating search engines about added, updated or deleted URLs. Start with one exact public host and one real release. Build the submission from the release's changes and check that the public site reflects those changes before notifying. Keep the sitemap and ordinary internal links current as part of the same workflow. IndexNow protocol documentation

A small site can use a supported CMS integration if it covers the actual publishing route. A repository-backed site can run a scoped task after production is ready. In either case, check whether an existing integration already submits the same release. Identify a single owner and keep an easily readable record of what was sent.

Verify the key and the host first

Use the protocol's key-file method. The recommended location is the root of the public host. The file must be reachable and contain the expected key. If a custom location is necessary, read how the key's path limits the URLs it can cover and use the documented key location field. Keep the host, the key location and the submitted URLs aligned. IndexNow key and request rules

Consider a business with its main website at a www address and an articles library at a separate insights subdomain. A release changes only the articles library. Confirm the key file is served for that host and the submission lists its canonical addresses. Enter the same host in the request. Check the public key URL directly for the body you expect. A platform may return a branded error document or rewrite a missing text file to a page even when the request appears successful.

Build the submission from the actual change list

For new articles, use the final public addresses after publication. For edits, include the public URLs whose content changed materially. For removals, verify the intended status before reporting the changed URL. Where the SEO plan calls for a redirect, test the old address and the destination separately. Where content was intentionally removed, verify the removal response. The notification reports a change the website already made.

Filter preview URLs, tracking variants, drafts and duplicates out of the batch. For a move across hosts, verify the requirements for each host separately. In simultaneous releases, use a record of the deployed state so a retry does not accidentally send a URL that was never published. A short log with a date, host, URL list and response is adequate for many small teams.

A concrete release sequence

Imagine a hypothetical studio publishes a service, revises one article and retires an expired event. Its publisher verifies that the service and article load on the canonical host and are discoverable from relevant pages. They verify the retired event's intended status and remove it from the current sitemap. The responsible integration submits the changed URLs after the release becomes publicly available.

The first run returns 202. Record that the server received the request and key validation is pending. Check the key's live address and the expected file content. Give the system time to process the request. Later, use Bing's inspection workflow to examine an important URL. Keep the request result and the inspection result in different columns. The two observations describe different stages.

Respond to the status you actually received

ResponseWhat the protocol reportsUseful next step
200Submitted successfullyLog the request and use inspection for crawl or index status
202Received with key validation pendingCheck the key file and allow processing time
400Invalid request formatCompare the data with the documented format
403Key validation problemCheck the public key address and contents
422Host or protocol mismatchVerify the URLs, declared host and key scope
429Too many requestsStop immediate retries and review duplicate emitters and release frequency

The response describes the notification. An engine may process a page later or choose not to include it. Verify any visible index status separately, using the relevant engine's tool and the exact canonical address. IndexNow response format

Plan for a failed submission without interrupting publishing

If pages are already live and the notification fails, preserve a small retry record. Repair the key, request format or host issue based on the response. Retry only the affected release after confirming its URLs still describe the current site. Where the engine reports throttling, check for a CMS plugin and a deployment task both submitting the same change. Keep the original timeline so the owner can tell an indexing delay from a release problem.

Check sitemap coverage and ordinary page links when a notified article persists as unknown. Open the public address in a browser and verify access, canonical and the content you expect a crawler to see. Search engines use their own processing decisions. For Google, follow its Search Console and sitemap guidance for the same public pages. Google's request recrawl guide

Before handing the workflow over, give the publisher a record of the host, key-file location, publishing signal, retry owner and inspection route. Include a sample acceptance check for a new article and a changed article. A business owner should be able to identify the last submitted release without being given broad deployment access.

Define exactly when a release should send notifications

Write down the publication signal used by your website. A scheduled article may already exist in a repository and still be unavailable on the public host. A failed production build may leave the previous version online. For both cases, the task should check the public release state before submitting. Limit the batch to URLs the change actually affected and keep the date used to create the list.

Consider a retry that overlaps with a newer release. The first release replaces a service page and the second corrects its address or status. Before retrying the old batch, have the workflow check that the submitted addresses still exist in the intended form. Rebuild the submission from the most recent published change record if necessary. Keep a trace of the original failure so the operator can diagnose it without submitting every historical URL again.

Finally, test the handover with a representative new publication and a deliberate correction. Ask the operator to find the live address, key file and submission log. Have them explain what they would do after a key error, a pending validation response or a throttling response. The acceptance check is that they can identify the correct next action from evidence and verify the public page independently.

Bring your publishing host, sitemap and release process to a discovery workflow review. Contact Brands Essential

Questions, answered

What does IndexNow do?

It sends participating search engines a notification when a URL is added, updated or deleted.

Does a successful request mean Bing indexed the page?

A successful response confirms submission. Crawling and indexing are separate stages to check later.

Where should the key file live?

The protocol recommends placing it at the root of the same host as the submitted URLs. Alternate key locations have scope rules.

Can I submit my subdomain with a key on another host?

Configure and verify the actual publishing host according to the protocol. Keep payload host and submitted URLs consistent.

What does a 202 response mean?

The URL was received and key validation is pending.

Should IndexNow replace my sitemap?

Keep the sitemap for the public catalogue and use IndexNow for changed URLs. Check individual status in the relevant search engine's tools.

Planning your next step?

Build a website around your customers and budget.

Tell Brands Essential what you need, what is already working and the budget you can sustain. Agree a useful first phase and the responsibilities before adding more.