How to get feedback on a website
To get feedback on a website, share a direct link to the live or staging site with specific questions attached — don't just ask "what do you think?" For clients, a review tool that lets them click the exact element and leave a pinned note works better than screenshots or email, because the context travels with the comment.
Share a review link they can annotate directly
The most common reason client feedback is vague is that they're describing a spot instead of pointing at it. A shared review link — where they click an element on the live site and leave a note pinned right there — removes that translation step. Tools like Drafty, Markup.io, or BugHerd let you paste a URL and generate a review board. The client opens a link in any browser, no account required, and each comment is anchored to the exact heading, button, or image they mean. You get "make the CTA stand out" pinned to the actual button — not described in a three-paragraph email. This works on staging URLs and custom domains.
Record a Loom walkthrough and ask specific questions
If your client isn't technical enough to navigate a review tool, a short Loom video walking through the site gives them something concrete to react to. Record yourself clicking through each section and narrate what you want feedback on: "I'm not sure if this pricing table is reading clearly — does the value prop land here?" Then send the Loom link with two or three written questions at the bottom of the message. Specific questions unlock specific answers. "What do you think?" gets "looks great" back. "Does the headline on the hero tell you what the product does within five seconds?" gets a real response. Loom's comment feature lets them reply timestamped to specific moments in the recording.
Walk through it together on a screen share
A 30-minute screen share where you drive and they react out loud is worth hours of async email. Share your screen (Zoom, Google Meet, or a Tuple session if they're technical), click through the site section by section, and ask focused questions at each stop. The key discipline: don't explain what you were trying to do — let them form a first impression before you frame it. Ask "what's the first thing you'd do on this page?" before you tell them about the primary CTA. Take notes in a doc during the call and share it back with timestamped action items. Use Otter.ai or Zoom's transcript if you don't want to type while listening.
Send a structured feedback form
For stakeholders who won't open a tool or join a call, a short Google Form or Typeform with section-specific questions gets written feedback without chasing them over email. Structure it by page section: Hero, About, Services, Pricing, Contact — and for each section ask one concrete question. "Does the services page make it clear what's included in each package?" beats "feedback on the services page." Cap the form at eight questions; anything longer kills completion. Add a screenshot of each section as a header image so they can see what you're asking about. Route the responses into a sheet and copy-paste the raw answers into a doc you share with your client before the next call.
Use Figma comments if the site is still in design
If the site isn't built yet and lives as a Figma prototype, share a view-only link and turn on comments. Clients can click any frame and leave a note without a Figma account — they sign in with Google or create a free viewer account. Figma comments are pinned to coordinates in the frame (not to semantic elements the way a live-site tool works, so they can drift if you move things), but for wireframes and mockups it's the right level of fidelity. Export the comment list as a CSV at the end of the review phase so you have a record outside Figma. For the final built site, switch to a live-review tool that works on the rendered page.
If your client keeps leaving feedback that says "the thing near the top" — paste your site URL into Drafty and send the review link instead. They click the exact element on the live page and leave a note pinned right there, no account required. Every comment is threaded and anchored; you resolve each one when it's fixed. Works on staging URLs and on desktop or phone.
Open a live demoQuestions
- How do I get feedback on my website without asking clients to sign up?
- Use a shared review link from a tool that supports guest commenting — the client opens the URL in any browser and leaves notes without creating an account. Most visual feedback tools (Drafty, Markup.io, Ruttl) support this. Avoid sending them to a tool that requires them to join a workspace.
- How do I ask for specific website feedback?
- Replace open-ended questions with section-specific ones. Instead of "what do you think?", ask "does the pricing table make the difference between plans clear?" or "can you tell what the product does from the hero alone?" Attaching questions to specific page sections — either in a form or verbally on a call — gets you actionable answers instead of vague impressions.
- What's the best way to get website feedback from clients remotely?
- A shared review link that lets them annotate the live site is usually the lowest-friction option for async feedback. For complex projects, combine it with a 30-minute walkthrough call early in the review phase — the async comments come in more focused after they've seen the full picture once.
- How do I get feedback on a website that's not live yet?
- Share the staging URL through a review tool — most work on any publicly accessible URL, including staging environments. If the site is still in Figma, share a view-only prototype link with comments enabled.
- How do I collect website feedback from multiple stakeholders?
- Send everyone the same review link rather than separate email threads. A shared link means all comments land in one place, anchored to the same artifact — you see each person's notes without reconciling four different annotated screenshots or email chains.
- How do I get feedback on website copy specifically?
- Ask reviewers to comment on individual paragraphs or headings, not the page as a whole. A review tool that lets them click a text block and leave a note is better for copy feedback than a form. On a call, read the headline aloud and ask "does that land?" before showing the full page.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.