Skip to main content

Optional IndexNow root-file setup

You do not need this to use connected Bing Webmaster. Use it only when an operator already controls the edge serving your public storefront. Clione never installs a CDN, changes DNS or asks for your CDN account token. Shopify app proxies, theme assets and BigCommerce content directories do not prove root coverage for the catalogue.

Prepare the file for one store​

  1. Open Settings → Integrations → Indexing → Optional root-file hosting.
  2. Confirm that your agency controls the existing edge. Choose its provider and enter the exact public HTTPS storefront origin, with no path or query. This is the storefront shoppers use, not Clione's API or Shopify admin.
  3. Select Prepare and download root-file setup. This does not enable submissions. Give the generated file to the operator for this store only. Its IndexNow key is a public ownership proof, not a login/API credential.
  4. Ask the operator to apply the matching instructions below. No change to DNS, a hosted-platform vendor domain, checkout, admin or other routes is needed.
  5. Select Verify root file and opt in after the exact HTTPS file is reachable. Verification requires HTTP 200, plain text containing the generated key, no sign-in and no redirects. A missing, HTML, redirected or stale file fails.
  6. Separately enable Bing and publication notifications in Notification settings. Administrator enablement is also required. Preparing or verifying an edge file never turns on the global worker or your publication notifications.

Clione keeps the connector's permanent store identity. It uses your explicit public origin for indexing only after the root proof succeeds. Changes to the connector invalidate that binding. The submitted URL still comes from the current catalogue and all four entity types keep their existing paths.

Cloudflare: an existing proxied storefront​

Give indexnow-root.mjs to the operator of the existing compatible zone. Create a dedicated Worker using that module and bind only the exact HTTPS hostname and root-file path shown by Clione. Do not use a wildcard route or Custom Domain, enable proxying, add DNS or intercept the rest of the store. The module serves GET/HEAD for that file only. Other requests return 404; it never forwards to the origin. Therefore it must never own a broad storefront route. Preserve the existing platform/CDN/TLS setup and check provider terms.

CloudFront: the existing distribution​

Give indexnow-root-cloudfront.js to its operator. Merge the exact guard into its current viewer-request function; do not overwrite existing routing logic. Select a supported JavaScript runtime, test the exact host/path and activate it only through the operator's existing distribution process. Other paths return the original request unchanged, so the store continues to use its existing origin. The generated response is text; GET has the key and HEAD has no body.

Fastly: the existing service​

Give indexnow-root-fastly.txt to its operator. Put the first guarded fragment in the existing vcl_recv snippet and the second in vcl_error. Preserve existing conditions and error handling. Only the exact host/path and GET/HEAD use the marked synthetic response. Validate the complete VCL and publish only through the operator's normal service-version process. This file is a pair of snippets, not a replacement service configuration.

Other providers or an existing root host​

Download the static file option. Configure one exact HTTPS root-file response on the current public storefront; the body must be the unchanged UTF-8 key and Content-Type text/plain. Preserve every other route. If the provider cannot serve this directly, leave IndexNow disabled and use connected Bing Webmaster. A redirect or browser script cannot substitute for the root file.

Disable or rotate​

Disable IndexNow edge route in Clione stops its use for subsequent jobs; the operator removes the route separately. A file on the CDN is not removed by Clione. Connected Bing stays independent and the already-proven public storefront origin is retained. Rotate key prepares a new file and invalidates the old proof. Update the exact edge route, remove the old file and verify again before submissions resume. Never use a different store's proof or API key.

A successful notification is received, not proof that a URL is indexed. See search discovery for Bing connections and how to interpret observed/not-measured results.

Provider references: IndexNow, Cloudflare routes, CloudFront function events, Fastly synthetic responses.