PublishedVerifiedEvery 6 weeksSources5 namedAuthored bySquareRank Team
Bing Copilot · § 1.5.2 · How-to
IndexNow on Squarespace
Squarespace does not natively integrate IndexNow1 — there is no toggle, no plugin, no built-in submission hook. Two manual paths work in 2026. The URL submission tool inside Bing Webmaster Tools4 handles the no-code case on every plan. The hosted key + direct GET pattern handles the automation case for owners willing to use the URL Mappings workaround the llms.txt cluster already documents.
This leaf is the operational walkthrough. What IndexNow is, why Copilot owners care about freshness, the two manual paths Squarespace owners can actually run, and the scope/limit notes that come up after the first 100 submissions.
§01TL;DR
TL;DR
On Squarespace the no-code path is the right default. Open Bing Webmaster Tools, go to URL Submission, paste the URLs you changed today, click Submit. Bing accepts up to 10,000 URLs per day per host. The hosted-key + direct GET path is only worth setting up if you publish enough new content to need automation — at that point the URL Mappings workaround that hosts llms.txt also hosts the IndexNow key file. Either path keeps the Bing index fresh enough that Copilot can ground answers on your recent content within hours instead of days.
The whole leaf assumes Bing Webmaster Tools is already verified and the sitemap is submitted. If that is not done yet, the bing-webmaster leaf is the floor; come back to IndexNow once verification is complete.
§02What it is
What IndexNow is, and why Copilot owners care
IndexNow is a free, open-source protocol that lets a website notify participating search engines whenever a URL is added, updated, or deleted. The point: instant re-crawl instead of waiting for the next scheduled pass. Participating engines (Bing, Yandex, Naver, Seznam) share submitted URLs automatically, so one submission reaches all of them. For Bing Copilot work specifically, IndexNow is the lever that keeps the Bing index fresh enough to ground answers on content you published this morning rather than content from last week's crawl.
The protocol is straightforward1. The publisher generates an 8-128 character hex key, hosts it on their site, and then either pings a single URL via an HTTP GET to https://<engine>/indexnow?url=...&key=... or submits up to 10,000 URLs in a single POST request. Microsoft's framing3 is that the protocol "saves crawl resources" for the engine and "speeds up indexing" for the publisher — the second part is the part that matters for Copilot citation, because grounding accuracy on time-sensitive queries depends on the index being current.
The reason this matters for Squarespace owners is the cadence mismatch. Bingbot's default crawl cadence on small sites is measured in days, not minutes. New content can sit unindexed for two to five days while Copilot continues to ground its answers on stale pages. IndexNow collapses that window: a submitted URL is typically picked up by Bingbot within minutes. The AI Performance dashboard5 Microsoft launched in February 2026 makes the feedback loop visible — submit a URL via IndexNow, watch the URL appear in the per-URL citation activity table within 24-48 hours if Copilot grounds against it.
§03The gap
Why IndexNow does not natively work on Squarespace
Two platform constraints close the easy path. Squarespace does not allow you to upload a file at the root of your domain, so the canonical hosted-key flow that WordPress sites set up with a single plugin install does not work as written. And Squarespace's CMS lifecycle hooks do not expose URL change events to a third-party submission service, so the automatic-ping pattern that Cloudflare and similar CDNs offer is also closed. The protocol still works on Squarespace; the publisher just has to drive the submission flow manually.
The root-upload constraint is the same one the llms.txt cluster works around. Squarespace's editor lets you create pages, blog posts, and collection items at any URL it owns, but the literal root of the domain (anything matching /file.ext) is reserved for platform infrastructure. The workaround for both llms.txt and the IndexNow key is identical: create a Squarespace page at slug /your-key, then add a URL Mapping rule that 301-redirects /your-key.txt to /your-key. IndexNow accepts the redirect chain when validating the hosted key file because the redirect destination serves the same content.
The lifecycle-hook constraint is harder to fix. Even after the key is hosted, Squarespace will not automatically notify Bing when you update a page — you do it yourself, either through the Webmaster Tools UI or via a one-line curl call you run after publishing. For most Squarespace sites this is fine because publishing cadence is measured in weekly or monthly, not hourly. For high-cadence publishers (news sites, marketplaces), Squarespace is not the right platform; the analysis here assumes you publish under 100 URLs per week.
§04Path A
Option A: the URL submission tool (easiest, no code)
Bing Webmaster Tools ships a URL submission tool that handles the IndexNow protocol behind the scenes. You paste URLs into the form, Bing forwards them to its IndexNow infrastructure, and the protocol's URL-sharing contract distributes them to the other participating engines. No API key needed, no file hosting needed, no code injection needed. Daily limit is 10,000 URLs per host. This is the right default for every Squarespace owner on every plan.
The flow is literally three clicks once Webmaster Tools is verified. Open the tool, click URL Submission in the left navigation, paste the URLs (one per line for bulk, or single field for single-URL), click Submit. Microsoft's URL submission API documentation4 covers the programmatic version of the same endpoint, but for a small Squarespace site there is no reason to use it — the UI is faster than wiring an API call would be.
§05Path B
Option B: hosted key + direct GET (technical, automation-friendly)
If you publish enough new content to want automation — or you want to ping multiple participating engines without going through Bing's UI — the hosted-key path is the way. Host an IndexNow API key on your Squarespace site via the URL Mappings + page-slug workaround. Then hit the GET endpoint with curl, a Zapier webhook, or any HTTP client that can fire on your publish event. The protocol is open and the keys are non-revocable, so once set up the submission is one line.
The hosted-key setup is the part that needs the workaround. The protocol spec1 requires the key file to be reachable at https://yoursite.com/<key>.txt (or at a documented alternative location your submission references). On Squarespace, the path that ships this is:
Create a Squarespace page with slug /your-key (the key value, lowercase, no extension).
Inside the page body, paste the key as the only visible content. Remove any wrapping divs or auto-emitted tags that the page template adds — use the simplest template available.
In Settings > Advanced > URL Mappings, add a 301 redirect: /your-key.txt -> /your-key 301.
Test by visiting https://yoursite.com/your-key.txt directly. The page should render and the URL bar should show the redirect target. The content should be the bare key string.
Once the key is hosted, the submission is a single GET request. Microsoft's getting-started page2 gives the canonical pattern:
bashSubmit a single URL to Bing IndexNow
# Single-URL GET — the easiest automation patterncurl"https://www.bing.com/indexnow?url=https://yoursite.com/blog/your-new-post&key=YOUR-KEY"# Response codes you will see:# 200 success# 400 invalid request format# 403 key not reachable or invalid# 422 key/URL host mismatch# 429 rate-limited
The bulk POST flow that the protocol supports (up to 10,000 URLs per request) needs a server you control to assemble the JSON body, which most Squarespace setups do not have. Stick with the single-URL GET pattern and run it from a Zapier or Make webhook on every Squarespace publish event — or just paste the curl line into a terminal after each publish.
§06Scope
Scope, rate limits, and what IndexNow does not do
IndexNow tells the engine your URL has changed. It does not guarantee a re-crawl, does not guarantee indexing, and does not affect ranking. Bing accepts up to 10,000 submitted URLs per day per host before rate-limiting kicks in (HTTP 429). The participating-engine list is Bing, Yandex, Naver, and Seznam — Google does not participate, so AI Overviews and Gemini citations are unaffected. The protocol is signal, not magic.
The honest framing matters because IndexNow is often described as if it bypasses indexing decisions. It does not. Bing still applies its standard ranking and quality filters; IndexNow only collapses the crawl latency. A page that Bing would not have indexed without IndexNow will not get indexed with it either — the protocol speeds up the engines, it does not change what they will accept.
What IndexNow does and does not affect
10,000
URLs per day per host before Bing rate-limits IndexNow submissions (HTTP 429).
