IndexNow governance · Updated October 21, 2026
WTN Market IndexNow key isolation across multiple sites
Keep WTN Market IndexNow keys, host declarations and URL batches isolated for each independently deployed site. This guide treats WTN Market and WTNMarket search terms as research labels, not as proof that a destination is official or safe.
Use a site-scoped key
Assign a unique IndexNow key to each WTN Market deployment. Site isolation prevents a script intended for one hostname from silently submitting another site’s URLs.
Store the key file on the matching public host and keep the submission configuration beside that project.
Validate the key location
Request the declared key URL and confirm that it returns the exact key as plain text. A successful application deployment does not guarantee that the asset route is reachable.
Do not reuse an analytics identifier, administrator password or recovery secret as an IndexNow key.
Construct a narrow URL batch
Create the submission list from pages added or materially edited in the current release. Ensure every URL belongs to the declared host and resolves to its canonical version.
Reject batches that contain admin, preview, error or redirected routes.
Log acceptance and follow-up
Record request time, submitted URLs and the IndexNow response. Then use Bing Webmaster Tools to observe discovery and crawl status.
Acceptance is only the first event in the workflow; it should never be reported as guaranteed indexing.
Frequently asked questions
Why use a different IndexNow key for every site?
It reduces cross-site mistakes and keeps submission authority scoped to one host.
Is an IndexNow key an admin password?
No. It verifies submission control and should be separate from all login credentials.