Which Squarespace plan do you need for code injection?
Squarespace only unlocks code injection from the Business plan upwards; the cheaper Personal and Commerce Basic plans keep it locked entirely. Without that plan, the „Code Injection“ item under Settings → Advanced is either missing entirely or greyed out, and clicking into „Advanced“ only reveals a limited set of options. An upgrade is therefore a prerequisite before you can add the nootiz snippet at all, so check this first before promising a client a sign-off date. Agencies running several Squarespace projects usually set up the Business upgrade at project start anyway, since code injection is also needed for tracking pixels and chat widgets.
Site-wide or single page: where do you add the code?
Under Settings → Advanced → Code Injection, the „Header“ field applies the code across the entire site, including every blog post and product page. If you only want feedback on one specific landing page, add the code instead in that page's own settings under „Advanced“ → „Page Header Code Injection“ – handy when clients should only review a new campaign page and the rest of the site should stay untouched. Both approaches can be combined: a site-wide snippet for the ongoing sign-off plus an extra page-level snippet for an isolated campaign, without the two interfering with each other.
Why do you need to reload or work around caching after adding it?
Squarespace serves pages through a CDN and can cache HTML responses for several minutes, especially on high-traffic landing pages. After saving the snippet, an already-open page may only show the script after a hard reload (Ctrl/Cmd+Shift+R). If in doubt, wait a moment and open the page in a private browser window to rule out your local cache too. If the snippet still doesn't show up after several minutes and a hard reload, first check that it was actually saved in the correct field – header, not footer – before chasing a caching problem.
Does code injection work across all Squarespace templates and versions?
Yes, code injection is a Squarespace-wide feature independent of the chosen template or of Squarespace 7.0 versus 7.1. Because the underlying page structure differs between versions, individual elements' CSS selectors can be named differently – but the nootiz snippet itself needs no adjustment for that, since it targets the rendered DOM element rather than fixed selectors. Switching templates within the same version also leaves the snippet untouched, because it lives centrally in the header rather than inside the template code.
What about password-protected pages before launch?
Many Squarespace projects sit behind a site-wide password before launch, turned on under Page Settings → „Password Protection“. That is fine: anyone with the password and the nootiz link can still leave notes normally, because the code injection header is served regardless of password protection. That makes sign-off possible before the official go-live, without exposing the password publicly ahead of time. Share the page password separately from the nootiz link, for example by email, so clients aren't caught off guard on first visit and understand the two belong together.
Do clients need a Squarespace account to give feedback?
No. Clients simply open the nootiz link to the published page and can leave notes right there, with no Squarespace login or contributor membership required. That matters especially for external clients you don't want to give backend access to for good reason, for instance because they could accidentally change content. Developers and editors, meanwhile, see the exact URL, the clicked element, a screenshot, and browser and device details attached to every note, so any piece of feedback can be triaged without a follow-up question.
Where are the limits on Squarespace stores and member areas?
On regular pages, blog posts, and product or category pages the setup works reliably, since these are technically normal URLs where the header is served as usual. In Squarespace checkout steps, which partly run on a separate, secured subdomain, the code injection header is not served – checkout feedback is best captured with a note on the last regular cart page instead. In pure membership areas with their own login flow, some intermediate steps may also fail to load the header; it's worth testing that once before the actual sign-off round.
