Collect feedback on Wix websites: embed the snippet through Custom Code, share the link, get notes on the element. Free for 30 days.
In short
In Wix you add the nootiz snippet under Settings → Custom Code in the head section and publish the site.
Create a project in nootiz and copy the snippet.
Open the Wix dashboard → Settings → Custom Code (under „Advanced“) → „Add Code“.
Paste the snippet into the head section and set the scope to „All pages“.
Optionally exclude specific subpages if feedback is only needed on certain sections.
Save your changes and publish the site (the „Publish“ button top right).
Share the published link with client and team and collect notes right on the live page.
Custom code is only available from a paid Premium plan with a connected domain, not on the free Wix account. Without that plan, there is technically no way to add the nootiz snippet to the head – an upgrade is a requirement here, not an option. Check this before you start a project so you don't have to switch mid-review.
Wix serves custom code exclusively on the published site, never in the editor preview. So after pasting the snippet, you need to click „Publish“ once before nootiz becomes visible. The upside is that feedback always happens on the version visitors actually see, including the mobile Wix view, which often has its own layout.
Yes. The classic Wix Editor, Wix Studio and Editor X all publish regular web pages with the same custom-code settings underneath. It does not matter which editor built the page – nootiz always attaches to the rendered element in the front end, independent of internal Wix component names.
Wix pages are usually assembled from reusable sections (strips) that can look identical across several subpages. Every nootiz note stores the full URL of the exact subpage plus a screenshot crop, so even on lookalike sections you immediately know which page the comment actually refers to.
Anyone with your nootiz link can leave notes directly on the published page, with no Wix login or team role required. That is especially useful for clients who should give feedback but never touch the Wix backend – you also don't need to grant them any extra Wix collaborator roles.
Every note includes the exact URL of the Wix subpage, the marked element, a screenshot crop, and the reviewer's browser and screen size. Because Wix pages are often built from reused sections, that screenshot context makes it much easier to tell apart identical-looking sections repeated across different subpages, without needing to ask what was meant every time.
As long as the site is published – even with a site password enabled or in „Coming soon“ mode – custom code is still served. So anyone with the password and the nootiz link can give feedback before the official launch, without the site needing to be publicly discoverable. That works well for sign-off shortly before go-live.
Without a Premium plan with a connected domain, this setup simply does not work, since Wix blocks custom code otherwise. Inside embedded widgets from the Wix App Market that run in their own iframe, pinpointing the exact element is less reliable – a note on the surrounding area with a short description usually covers it. The Wix blog editor itself is also out of scope; only the published blog page can be commented on.
No, custom code is only available from a Premium plan with a connected domain. It cannot be added on the free Wix account.
No. The nootiz snippet runs through the custom-code settings, so there is no extra app to install or pay for separately.
Yes. Every note stores the screen size, so mobile layout issues in Wix are clearly distinguishable from desktop ones.
Use the Wix custom-code settings to add the nootiz code to the head once and apply it to all pages – no template changes needed.
No. Clients open the published page through the nootiz link and comment directly, without a Wix login or team role.
Yes. Wix Studio publishes normal web pages with the same custom-code settings, so notes attach per element there too.
As long as the site is published, the code is still served even with a site password enabled. Anyone with the password and the link can leave notes normally.
Notes can be pushed to Trello, Asana, Jira or GitHub as tasks, including URL, element and screenshot.
Deeper pages on platforms, comparisons and hands-on workflows.
In Framer you add the nootiz snippet under Site Settings → General → Custom Code (head) and publish. Clients then give feedback on the published site instead of commenting on the Framer canvas they cannot access without a seat.
→PlatformIn Webflow you paste the nootiz snippet into Project Settings → Custom Code (head) and publish the project. Clients then comment on the published page – no Webflow seat, no Designer licence, and no translating comments back into the Designer.
→Use caseFor password-protected staging and preview environments that need outside feedback.
→GuideWebsite markup means feedback gets placed directly on the element on the live page. Here is how that works, technically and in practice.
→Comparisonnootiz is a Ruttl alternative for teams that want to collect and resolve feedback without editing designs inside the tool itself.
→Use caseFor project managers who want to know a site's approval status without calling a status meeting.
→Add the snippet, share the link, collect feedback right on the page – live in under 5 minutes.
