How to comment on a live website
To comment on a live website, paste the URL into a proxy annotation tool. You get back a shareable review link — click any element on the running page and pin a note right to it, no browser extension and no login for the reviewer. The comment stays anchored to that element even if the page re-renders around it.
Browser DevTools (for yourself, not shareable)
Right-click the element you want to note, choose Inspect, and add a comment attribute directly in the Elements panel — for example, `data-note='CTA button is too small on mobile'`. This is fast for self-review: your annotation sits on the live DOM without touching the source. The hard stop: DevTools notes vanish the moment you reload, and there is no way to share them. They're a scratch-pad, not a feedback channel. Use this only when you're working alone and just want to remember something before you push a fix.
Proxy review link (the practical method)
Paste the live URL into an annotation tool that wraps it in a proxy frame. The tool generates a review link — share that instead of the original URL. Anyone who opens the link sees the real running site with a comment layer on top: they click any element, type a note, and it pins right there. The review link persists even as the underlying site changes, so late-stage comments land on the actual production state, not a frozen screenshot. Tools that work this way include Drafty, Pastel, and Ruttl. The key difference between them is whether reviewers need an account and whether the conversation is threaded.
When the client is the one commenting
Asking a client to install a Chrome extension before they can leave a single comment is the fastest way to get a voice note instead. The proxy approach sidesteps this entirely: you set up the review link, they click it, they comment — on their phone or their laptop, in whatever browser they already have. One thing designers often miss: if the live site requires a login (a client portal, a gated dashboard), the proxy tool needs to handle authenticated pages too. Test the review link yourself before sending it. If it shows a login wall rather than the actual page, you'll need to use a tool that supports session-based proxies or share a local staging build instead.
Sending a live site for client sign-off? Drop the URL into Drafty and share the review link. Your client clicks the exact element — the nav, the hero copy, the footer — and leaves a note pinned right there. No account, no extension. Every comment lands in one thread anchored to the spot, and when you push a fix the link stays the same so they can check it off without a new email.
Open a live demoQuestions
- Can I comment on a live website without a browser extension?
- Yes. Proxy annotation tools let you paste the live URL, get a shareable review link, and click any element to pin a note — no extension installed on either side.
- Does my client need an account to comment on the live site?
- Not with tools that support guest commenting. They open the review link and leave a note without signing up. Pastel, Ruttl, and Drafty all work this way, though each handles guest identity slightly differently.
- Can I comment on a live website I don't own?
- Yes — proxy annotation tools work on any public URL. Paste the address, share the review link, and annotate the live page without access to the hosting or source code.
- What happens if the live site updates while people are still commenting?
- The review link stays live and comments remain anchored to their elements. If the developer ships a large layout change, some pins may shift — most proxy tools re-anchor them by element selector rather than pixel position, which helps. Check after a big deploy to confirm any mid-review comments still land where you expect.
- Can I comment on a live website on mobile?
- It depends on the tool. Proxy-based review links generally render the live site in a browser frame and accept touch input on iOS and Android. Check your tool's mobile support before you send the link to a client who you know reviews on their phone.
- How is commenting on a live site different from commenting on a Figma file?
- Figma comments sit on a static design. A live-site comment lands on the running build — the real fonts, the real media queries, the actual hover states. Reviewers can scroll, resize the window, and interact with the page before pinning a note, which tends to surface issues that a static mockup hides.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.