How do I get feedback on a landing page without asking the client to sign up?

Use a proxy-based review tool or a shareable annotation link. The client opens the URL in any browser, clicks the element they want to flag, and types a note — no account needed. Figma and Framer both require a login to comment, which adds friction when a client isn't already on those platforms.

How do I ask a client for feedback on a landing page?

Send the link with two or three specific questions rather than an open 'what do you think?' Useful prompts: 'Does the headline make the offer clear in five seconds?' and 'Is anything confusing or missing before you'd click the CTA?' Specific questions get specific answers you can act on. Vague prompts get 'looks great!' or 'can we make it pop?'

What is the best tool for landing page feedback from a client?

A shareable annotation link the client can open without installing anything. Browser-extension tools (like BugHerd) require the client to install an extension. Figma requires a login to comment. Proxy-based review links (Markup.io, Drafty) let the client click directly on the page element they mean and leave a note — the feedback arrives pinned to the exact spot.

How do I collect feedback on a Webflow or Framer landing page before it goes live?

Paste your Webflow preview link or Framer share link into a proxy-based review tool. It wraps the page in an annotation layer and gives you a shareable feedback link. One caveat: some Webflow preview URLs redirect through an authentication step that breaks the proxy render. If the tool shows a Webflow login screen instead of your design, publish to a staging domain first before sharing for review.

How many rounds of feedback should I expect on a landing page?

One to two rounds is common when the client can annotate on the actual page — because element-pinned comments remove the back-and-forth needed to locate what they meant. Email-based feedback rounds typically run longer: each vague note ('the top section') requires at least one exchange to clarify before you can fix it.

Can I get feedback on a landing page on mobile?

Browser extensions don't work on iOS Safari or Android Chrome — so any tool requiring an extension won't work on a client's phone. A proxy-based review link works on mobile: the client opens it, taps the element, and types a note. This matters for landing page sign-off specifically because clients often check how the page renders on their phone before approving it.

drafty

How to get feedback on a landing page

Quick answer

To get feedback on a landing page, share a review link your client can open in any browser and click the exact element they mean — headline, CTA, hero image — and leave a pinned note. No account, no install. For a quick solo pass, export a screenshot and mark it up yourself. The review-link approach is the only method that consistently gets you specific, element-level feedback from a non-technical client before your deadline.

Step 1

Screenshot markup — for your own notes before the client call

Take a full-page screenshot of your staging build. On Mac, GoFullPage in Chrome captures the entire scroll in one shot; on Windows, the browser's built-in screenshot tool or Snipping Tool does the same. Open the image in Figma or Preview, add arrow callouts to the sections you want to discuss, and use it as your agenda for the review call. This works well for a solo pre-check but breaks down when you try to collect feedback from the client this way — they mark up their own copy, email it back, and you're reconciling two flat images against a live page. One revision round and the screenshots are already stale.

Step 2

Share your staging URL and ask for feedback by email

Most landing pages live on a staging URL before launch — a Webflow preview, a Framer share link, or a Vercel preview deploy. Send the client the URL with a short list of specific questions: 'Does the headline make the offer clear in under five seconds?' and 'Would you click this CTA?' are better prompts than 'What do you think?' Open-ended questions like that invite flattery; specific questions get you something you can act on. The downside is that email replies are disconnected from the page — 'the bit near the top' and 'the blue section' require a back-and-forth to place before you know what to fix. Expect one extra exchange per vague reply.

Step 3

Share a Figma prototype and collect comments

If you designed the landing page in Figma, click Share → 'Can view' → Copy link. The client can open the prototype in any browser. The catch: leaving a comment in Figma requires a Figma account. If the client already uses Figma, this is the most faithful view — live layers, exact type, correct spacing. If they don't have an account, they have to create one before they can type a single note. That's a real barrier on a deadline, and 'just create a free account' is a known friction point in freelance designer workflows. The same account gate applies to Framer's share link. Worth knowing before you send it.

Step 4

Share a review link they annotate directly on the page

The most reliable method for client sign-off: give them a link they open in any browser — desktop or phone — and click the element they mean. The CTA button, the hero headline, the pricing section. Their note lands pinned to that exact spot. You see it in a thread, reply, and fix it. No account, no install on their end. This is what purpose-built review tools are for. The practical advantage on a landing page: clients can annotate the same section from their laptop and then check it again on their phone, which matters when you need sign-off at both sizes. One pinned note on the actual CTA beats three email exchanges trying to locate which button they meant.

The faster way

If you're a designer waiting on client sign-off before launch, share a Drafty link instead of the staging URL directly. Paste the page URL, send the link, and your client clicks the headline, the hero image, or the CTA button and types a note pinned right there — no account, no extension required. Every comment lands in one thread, anchored to the element they meant. When you push a revised version, it lives on the same link — no re-sending files, no new URLs.

Open a live demo

Questions

How do I get feedback on a landing page without asking the client to sign up?: Use a proxy-based review tool or a shareable annotation link. The client opens the URL in any browser, clicks the element they want to flag, and types a note — no account needed. Figma and Framer both require a login to comment, which adds friction when a client isn't already on those platforms.
How do I ask a client for feedback on a landing page?: Send the link with two or three specific questions rather than an open 'what do you think?' Useful prompts: 'Does the headline make the offer clear in five seconds?' and 'Is anything confusing or missing before you'd click the CTA?' Specific questions get specific answers you can act on. Vague prompts get 'looks great!' or 'can we make it pop?'
What is the best tool for landing page feedback from a client?: A shareable annotation link the client can open without installing anything. Browser-extension tools (like BugHerd) require the client to install an extension. Figma requires a login to comment. Proxy-based review links (Markup.io, Drafty) let the client click directly on the page element they mean and leave a note — the feedback arrives pinned to the exact spot.
How do I collect feedback on a Webflow or Framer landing page before it goes live?: Paste your Webflow preview link or Framer share link into a proxy-based review tool. It wraps the page in an annotation layer and gives you a shareable feedback link. One caveat: some Webflow preview URLs redirect through an authentication step that breaks the proxy render. If the tool shows a Webflow login screen instead of your design, publish to a staging domain first before sharing for review.
How many rounds of feedback should I expect on a landing page?: One to two rounds is common when the client can annotate on the actual page — because element-pinned comments remove the back-and-forth needed to locate what they meant. Email-based feedback rounds typically run longer: each vague note ('the top section') requires at least one exchange to clarify before you can fix it.
Can I get feedback on a landing page on mobile?: Browser extensions don't work on iOS Safari or Android Chrome — so any tool requiring an extension won't work on a client's phone. A proxy-based review link works on mobile: the client opens it, taps the element, and types a note. This matters for landing page sign-off specifically because clients often check how the page renders on their phone before approving it.

Keep exploring

How to annotate a landing page How to annotate a website Review a website Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo