How do I get specific feedback on a website redesign?

Break the review into sections and attach a concrete question to each one. Instead of 'let me know your thoughts', send: 'Does the homepage hero tell you what we do in five seconds? Does the nav feel intuitive?' Specific questions produce specific answers. Pair them with a review link that lets the client click the exact element they mean — that combination eliminates the back-and-forth needed to locate what someone is referring to.

How do I stop clients from comparing the new design to the old one?

Walk them through the redesign before the async review and explain the decisions behind each change. When clients understand why something moved or changed, they react to the reasoning rather than just the difference. Recording the walkthrough for stakeholders who review async is worth the extra ten minutes — 'I liked it better before' almost always comes from people who missed the walkthrough.

How do I get website redesign approval from multiple stakeholders?

Share one review link and direct all stakeholders there. Each person comments on the same page, and you can see who said what without reconciling four separate email threads. If stakeholders contradict each other (which they will), a threaded reply on the anchored comment is the right place to flag the conflict and ask for a decision — not a reply-all email.

How many rounds of feedback should I expect on a website redesign?

Two structured rounds is standard: one for visual layout and navigation, one for copy and content. If you combine both into a single round, clients mix concerns and the revision scope becomes hard to define. Running two clean rounds also helps you hold scope: anything introduced after round two is a new request, not a revision.

Can clients review a staging site without creating an account?

Not with all tools. Figma requires a free login to leave comments. Most proxy-based review tools — including Drafty — let clients comment as guests on a public link, no account needed. That matters during a redesign where the primary reviewer is often the client's own staff or a non-technical stakeholder who will bail out at a signup screen.

What should I include in a website redesign feedback request?

Send: the review link, a short context note (one paragraph on what changed and why), and two or three specific questions you want answered. Avoid sending an open prompt with no structure. Attach a deadline for the review round so the feedback doesn't drag into launch week.

drafty

How to get feedback on a website redesign

Quick answer

To get feedback on a website redesign, share a staging link alongside two or three specific questions tied to each section — don't ask for general impressions. The hard part isn't collecting feedback; it's stopping clients from comparing the new design to the old one in their head without telling you which part they mean. A review link that lets them click the exact element and leave a pinned note fixes that: you get 'the Services nav item feels buried' instead of 'it felt easier to find things before.'

Step 1

Run a structured stakeholder walkthrough before the async review

The biggest redesign feedback mistake is skipping to async review before anyone has seen the new site in context. Book a 30-minute screen-share before you share any links. Drive the walkthrough yourself — click through every section in order and narrate the reasoning: 'We moved the pricing higher because analytics showed visitors were scrolling past the services section before landing on it.' When you explain the decisions upfront, clients react to what changed and why, not just what looks different. This cuts a surprising amount of 'I liked it better before' feedback, because the 'before' was based on something you've since solved. Record the session with Zoom or Loom for stakeholders who can't attend — people who review async without having seen the walkthrough almost always surface concerns that the walkthrough would have pre-empted.

Step 2

Share a review link so clients pin comments on the exact spot

After the walkthrough, share the staging URL through a proxy-based review tool (Markup.io, Drafty, Ruttl) so clients can annotate on the actual rendered page — not a screenshot or a PDF. The workflow is: paste your staging URL, generate a review link, share it. The client opens the link in any browser, clicks the heading, nav item, or section block they want to flag, and leaves a note pinned right there. You see 'the hero headline is doing too much work — can we split this into two lines?' anchored to the actual element, not buried in a reply email thread. This matters especially for redesigns, where the feedback is almost always about specific visual decisions ('this section used to feel lighter') rather than bugs or typos. Without element anchoring, those impressions are nearly impossible to act on.

Step 3

Ask section-by-section questions, not a single open prompt

'What do you think of the redesign?' gets 'looks great!' or 'can we adjust the vibe?' — neither is usable. Break the review down to specific sections and ask one concrete question per section. For a homepage redesign, useful questions look like: 'Does the hero make the offer clear in five seconds?', 'Is anything missing from the main nav?', and 'Does the footer feel complete for your target clients?' For a service or product site, add: 'Does the pricing section show enough detail to prompt a decision?' You can attach these questions to a review link as a pinned note at the top of the page, or send them alongside the link in an email. The goal is to anchor the client's attention to decisions that still have room to change — not to reopen sections you've already locked.

Step 4

Separate visual sign-off from content sign-off — they're different reviews

Redesigns fail review when visual and copy feedback arrive in the same round. Clients who are looking at layout will notice a typo in the headline and that typo becomes the review. Run two separate passes: first visual (layout, hierarchy, color, navigation), then content (copy, links, contact details, team bios, pricing). Send both as the same review link but in sequence — mark the first round closed before you open the second. You can do this by resolving all threads from round one (or exporting a summary) before sharing the 'content review' message. That separation also helps you figure out who should be reviewing what: the marketing manager should see the copy round; the founder or MD should see the visual round first. Mixing both audiences into a single async review thread is how you get seven unresolved threads that contradict each other.

The faster way

If you are waiting on client sign-off before a redesign goes live, paste your staging URL into Drafty and share the review link instead of the raw staging URL. Your client clicks the exact section they mean — hero, nav, pricing block — and pins a note right there, no account required. When you push a revised version it stays on the same link. Works on desktop and their phone, so mobile feedback comes in without a second sharing round.

Open a live demo

Questions

How do I get specific feedback on a website redesign?: Break the review into sections and attach a concrete question to each one. Instead of 'let me know your thoughts', send: 'Does the homepage hero tell you what we do in five seconds? Does the nav feel intuitive?' Specific questions produce specific answers. Pair them with a review link that lets the client click the exact element they mean — that combination eliminates the back-and-forth needed to locate what someone is referring to.
How do I stop clients from comparing the new design to the old one?: Walk them through the redesign before the async review and explain the decisions behind each change. When clients understand why something moved or changed, they react to the reasoning rather than just the difference. Recording the walkthrough for stakeholders who review async is worth the extra ten minutes — 'I liked it better before' almost always comes from people who missed the walkthrough.
How do I get website redesign approval from multiple stakeholders?: Share one review link and direct all stakeholders there. Each person comments on the same page, and you can see who said what without reconciling four separate email threads. If stakeholders contradict each other (which they will), a threaded reply on the anchored comment is the right place to flag the conflict and ask for a decision — not a reply-all email.
How many rounds of feedback should I expect on a website redesign?: Two structured rounds is standard: one for visual layout and navigation, one for copy and content. If you combine both into a single round, clients mix concerns and the revision scope becomes hard to define. Running two clean rounds also helps you hold scope: anything introduced after round two is a new request, not a revision.
Can clients review a staging site without creating an account?: Not with all tools. Figma requires a free login to leave comments. Most proxy-based review tools — including Drafty — let clients comment as guests on a public link, no account needed. That matters during a redesign where the primary reviewer is often the client's own staff or a non-technical stakeholder who will bail out at a signup screen.
What should I include in a website redesign feedback request?: Send: the review link, a short context note (one paragraph on what changed and why), and two or three specific questions you want answered. Avoid sending an open prompt with no structure. Attach a deadline for the review round so the feedback doesn't drag into launch week.

Keep exploring

Get feedback on a website Get feedback on a web design Review a website Website 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