Collect client feedback on WordPress sites: add the snippet to your theme or a code plugin, share the link, get notes pinned to elements. 30-day free trial.
In short
You do not need a dedicated plugin for WordPress: add the nootiz snippet once to your theme header (or through a code-snippet plugin) and you can leave notes on any element of any page. Clients need no WordPress login and no backend account.
Create a project in nootiz and copy the snippet.
Insert the snippet before </head> – via your child theme (header.php), the theme customizer's header field (the plain "additional CSS/JS" box will not work), or a code-snippet plugin such as WPCode, Insert Headers and Footers, or Header Footer Code Manager.
If you build with Elementor or Divi, use the builder's own "custom code" / "theme header code" setting instead of editing files directly.
Fully purge your caching plugin (WP Rocket, LiteSpeed, WP Super Cache), including any CDN cache in front of it such as Cloudflare or your host's CDN.
Reload the page, confirm the nootiz button appears, then share the link with your client and team.
The most robust option is a code-snippet plugin like WPCode: add a "header" snippet there and it survives theme switches. Editing the child theme's header.php directly (before </head>) also works, but never touch the parent theme file or the code disappears on the next update. functions.php works too via the wp_head hook, but is unnecessarily fiddly for a plain marketing snippet.
Nothing about the underlying logic – every page builder renders plain HTML in the end, which is what nootiz attaches notes to. For the install itself, Elementor Pro ("Theme Builder → Custom Code") and Divi ("Theme Options → Integration → Head") both offer dedicated header-code fields you can use instead of a plugin. The block editor (Gutenberg) behaves like a classic theme: use a header-snippet plugin or the child theme.
WP Rocket, LiteSpeed Cache, WP Super Cache and Autoptimize all serve a statically cached HTML file after the first visit. Add the snippet without purging the cache and the live page keeps showing the old version without nootiz. Also avoid settings like "delay JavaScript" or "combine JS" for the snippet, since that only starts nootiz after a user interaction and clients tend to miss the button.
Yes. Product pages, category pages, cart and checkout are regular WordPress pages sharing the same theme header, so the snippet loads there too. Clients can leave notes directly on product images, prices or checkout form fields – useful whenever they want a concrete layout or copy change in the store.
On a staging subdomain or behind a maintenance-mode plugin, add the snippet there separately, since staging environments often run a different theme configuration or caching setup. On WordPress Multisite, your header-snippet plugin needs to be active per subsite, unless you push the header code network-wide from an mu-plugin.
Every note carries the full page URL, the clicked element with its CSS selector, a screenshot crop and the comment text. That means you can jump straight to the right section in Elementor or the block editor instead of asking the client which "image top right" they meant.
nootiz does not replace WordPress logins or role management – anyone with the project link can leave notes, regardless of their WordPress user role. If you need fine-grained access per WordPress role, you would still add your own access rules at the WordPress level, such as password-protecting the whole site.
No. A snippet in the theme header is enough. If you would rather not edit a theme, use any code-snippet plugin such as WPCode.
No. Notes are only visible to project members, not to visitors of your WordPress site.
Yes. Product, category and checkout pages are regular pages – notes work there the same way.
The snippet loads asynchronously and does not block rendering. For live sites you can also serve it on the staging environment only.
Yes. Every note can be sent to Trello, Asana, Jira or GitHub as a task – including URL, element and screenshot context.
The note attaches to the rendered front-end element, so you see exactly the block the client means – no matter which builder created it.
It is usually the cache: a caching plugin is still serving the old, cached HTML. Purge the page cache and any CDN cache, then reload the page.
Yes. A code-snippet plugin or your page builder's own header field (Elementor Pro or Divi, for example) is enough, no direct theme file editing required.
Deeper pages on platforms, comparisons and hands-on workflows.
For password-protected staging and preview environments that need outside feedback.
→PlatformOn Squarespace you add the nootiz snippet under Settings → Advanced → Code Injection (header). After that anyone with your link can leave notes on the page without signing in to Squarespace.
→GuideBusiness teams, executives and clients without a technical background give feedback differently. Here's how to still make it usable.
→Use caseFor agencies that want shorter approval loops: client feedback lands on the page instead of in email, WhatsApp and spreadsheets.
→FeatureClick, type, done – feedback lands exactly where it belongs.
→PlatformIn 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.
→Add the snippet, share the link, collect feedback right on the page – live in under 5 minutes.
