Framer

Add CommentKit

1. In CommentKit, open Project → Setup, copy your project key and add every address people will review on: your Framer address (for example https://your-site.framer.website) and your own domain. Use the exact address: a wildcard such as *.webflow.io is refused, because anyone can host a site there.
2. In Framer, open Site Settings and go to General → Custom Code. In newer versions of Framer this is Project Settings → Custom Code → Add Script. Custom code may need a paid site plan.
3. Paste the tag into End of <body> tag. If Framer asks how often to run it, choose Once: Framer changes pages without reloading, and CommentKit follows those page changes by itself.
4. Publish the site. Custom code does not run on the canvas or in the preview.
5. Open the published site and press Ctrl/Cmd + Shift + K.

<script src="https://commentkit.dev/cdn/v1/loader.js" data-project="pk_live_your_key" defer></script>

Show it to clients

Open Project → Client links, create a link (for example “Anna – homepage review”) and send it by email, Slack or WhatsApp. It opens your Framer site with the feedback button ready. Your client confirms their email once; no account or password.

Teammates open the site and press Ctrl/Cmd + Shift + K, or follow any CommentKit email. After they sign in once, the widget shows for them on that device.

Keep it off the live site

You do not need to do anything for regular visitors. On every address except localhost, the widget stays hidden until someone opens a client link, follows a CommentKit email, presses Ctrl/Cmd + Shift + K or is already signed in. Visitors only download a tiny loader and see nothing. Do not add data-hide-on-production="false" on a live site: it shows the button to everyone.

To load CommentKit only on the Framer address and never on your own domain, use this instead of the tag:

<script>
  if (/\.framer\.(website|app)$/.test(location.hostname)) {
    var s = document.createElement("script");
    s.src = "https://commentkit.dev/cdn/v1/loader.js";
    s.setAttribute("data-project", "pk_live_your_key");
    document.head.appendChild(s);
  }
</script>

Troubleshooting

• Nothing appears: publish again, and open the published site rather than the preview.
• Comments from the previous page still show for a moment after you move to another page: CommentKit checks the address twice a second and then loads that page’s comments.
• Still nothing? Open the browser console: CommentKit writes one message starting with [CommentKit] that says what went wrong (for example a website address missing from Project → Setup, or a Content Security Policy; see the CSP guide). The troubleshooting page covers the rest.