How to share a landing page for feedback
To share a landing page for feedback, paste the page URL — or your staging preview link — into a proxy annotation tool. You get a review link your client opens in any browser, clicks the exact element they mean, and leaves a note pinned there. No account, no install. For a page that isn't live yet, a Webflow preview or Vercel preview deploy works the same way — the proxy wraps whatever URL you give it.
If the page is live: paste the URL and share the review link
Open a proxy annotation tool — Drafty, Pastel, or Ruttl — and paste in the live URL. The tool wraps the page in a comment layer and gives you a new shareable link. Send that link to your client; they open it in any browser, click the hero headline, the CTA button, or the pricing section, and leave a note pinned directly to it. No Figma account, no tool install, no 'how do I leave a comment?' message. Push an update to the page and the review link reflects it automatically.
If the page isn't live yet: turn your staging URL into a review link
Webflow, Framer, Vercel, and Netlify all generate a shareable URL before you publish. Most designers send this directly — which works if the client just needs to look, but gives them no way to leave anchored notes. The fix: paste the staging URL into the proxy tool the same way you'd paste a live domain. It wraps the page and generates a review link your client can annotate. One real caveat: some Webflow preview URLs redirect through an authentication step that breaks the proxy render. If the review link shows a Webflow login instead of your design, publish to a staging domain (e.g., preview.yoursite.com) and use that URL instead.
For a page that can't be linked at all: export and upload a screenshot
Some landing pages are local builds or behind a VPN with no shareable URL. Take a full-page screenshot — GoFullPage in Chrome captures the full scroll on Mac and Windows in one shot — and upload it to a review tool that accepts images. Your client clicks the element, pins a note, you see exactly what they meant. The image won't update in place when you push changes, so treat this as a pre-staging check, not the ongoing review loop.
Give the client one link and keep updating it
The most common landing page review mistake: sending a new link per revision round. By round three you have three separate threads and the client is replying to v1 feedback on v3 work. The cleaner approach is to update the landing page in place — same URL, same review link, updated content. Your client sees the current version; open notes are still visible; resolved ones are marked. If you're on a Webflow or Framer staging flow that generates a new URL per deploy, re-share the review link once per revision rather than starting a new thread.
Need client sign-off before launch? Paste the URL — staging or live — into Drafty. Your client opens the link, clicks the element they mean, and leaves a note pinned right there. No account, no install. Push a revision, the link still works. Reply, resolve — no new URL, no new email chain.
Open a live demoQuestions
- How do I share a Webflow landing page for client feedback before publishing?
- Webflow generates a preview link before you publish — you'll find it under the Share icon in the designer. Paste that URL into a proxy annotation tool to add a comment layer. One known issue: some Webflow preview links redirect through a Webflow login prompt, which breaks the proxy render. If you see a login screen instead of your design, publish to a custom staging domain first and use that URL.
- Can my client leave feedback on a landing page without creating an account?
- Not in Figma — Figma requires a login to comment even on a view-only link. A proxy annotation tool removes the barrier: your client opens the review link, clicks the element, types a note — no account. Markup.io, Drafty, and Pastel all support guest commenting.
- What is the difference between sharing a staging URL and a review link?
- A staging URL gives your client a live view of the page with no way to leave anchored feedback — their notes arrive as an email, a voice note, or a screenshot with red circles. A review link wraps the staging page in an annotation layer so they click the exact element and pin a note there. One email round of 'the bit near the top' usually converts designers to review links.
- How do I share a Framer landing page for feedback?
- Framer generates a share link from any project — click the Share button at the top right of the editor and copy the preview URL. Paste it into a proxy annotation tool to add guest commenting on top. Framer share links load cleanly in proxy tools; you shouldn't hit the authentication redirect issue that some Webflow preview links have.
- How do I collect landing page feedback from a client who isn't technical?
- Send one link that opens in any browser — no install, no account. Element-pinned commenting removes the need to describe visual things in prose: instead of 'the button near the logo' they click the button and type their note. That shift from description to selection is the biggest single friction-reducer for non-technical clients.
- How many revision rounds should a landing page take?
- Two rounds is common when feedback is element-pinned, because pinned notes remove the exchange needed to locate what the client meant before you can act. Email rounds typically run to three or four — each ambiguous note ('the top section') requires at least one clarification before a fix. The tool affects round count more than the number of changes does.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.