Where exactly do you add custom code in Framer?
Under Site Settings → General → Custom Code there are separate fields for „Start of Head“, „End of Head“ and „End of Body“. The nootiz snippet belongs in „Start of Head“ so it loads as early as possible and is already active by the time the page first renders. The setting applies project-wide to every page on the site; unlike Squarespace or Webflow, Framer has no per-page toggle for custom code. If you still want to scope feedback to a single subpage, it helps to just share the link to that one URL instead of trying to restrict the code itself.
Canvas comments do not solve the client problem
Framer's built-in comments require a Framer seat and project access, and they refer to the design inside the editor, not to the actually built site with real font sizes, load times and responsive behaviour. nootiz notes, by contrast, live on the real, published page – including the client's browser, OS and screen size, with no Framer login required. For clients who get lost quickly inside the editor, that is the key difference: they see the page exactly as it will look live, and comment right there.
Custom code only applies after publishing
As with other no-code builders, custom code is only served on the published site, not in the Framer editor preview or a single frame's preview. Use the free Framer staging domain (site-name.framer.website) when the real live domain is not signed off yet – custom code works identically there compared to the final domain. After every republish, it's worth a quick reload to make sure the current version, snippet included, is actually being served.
How do notes map onto Framer pages and components?
Framer projects are often built from reused components (like a header, footer or CTA section) that look the same across several pages. Every nootiz note stores the exact subpage URL plus a screenshot, so it is always clear which page an identical-looking component was flagged on, even when it is reused across multiple routes. For developers, that means they never have to guess whether a comment about the header refers to the homepage or a subpage, because the URL settles it.
Do clients need a Framer seat to give feedback?
No. They just open the nootiz link to the published page and can leave notes there directly, without being invited as a member of the Framer project. That saves you extra, often paid, seats for people who never work in the editor anyway, such as marketing stakeholders or external clients. For agencies juggling many rotating client contacts, that quickly adds up to real savings compared with buying extra Framer seats per project.
Does it work with Framer animations, overlays and sticky elements?
Yes. Notes attach to the rendered element in the DOM, not to a fixed coordinate on screen. For overlays, modals or expandable menus, simply place the note while the element is visibly open – nootiz captures that state via the screenshot context, so it stays clear later which state was meant. Scroll animations and sticky headers behave the same way: the mapping stays stable as long as the note is placed while the element is actually visible.
Where are the honest limits in Framer?
On CMS collection pages generated dynamically from a Framer collection, the setup works exactly like on static pages, since each collection page gets its own regular URL. Password-protected pages (Framer's „Password Protection“) still serve custom code too, so feedback remains possible before the official launch. What isn't covered is purely editor-internal state, such as unsaved drafts or variants that were never published – there simply is no URL for a note to attach to there.
