How to get feedback on a homepage
To get feedback on a homepage, share a review link your client opens in any browser and clicks directly on the element they mean — hero headline, nav, CTA — and leaves a pinned note. No account, no install. The homepage is the one page clients always check on their phone too, so make sure whatever method you use works on mobile without an extension.
Screenshot markup — good for pre-call prep, not sign-off
Take a full-page screenshot of the homepage on a staging URL. On Mac, GoFullPage in Chrome captures the full scroll; on Windows, the browser's built-in screenshot or Snipping Tool does the same. Open it in Figma or Preview, add labelled arrows to the sections you want to talk through — hero, nav, CTA, social proof — and use it as your agenda for the call. This is a clean way to prep your own review before you involve the client. It breaks down when you try to use it for client feedback: they mark up a JPEG, re-save it, email it back, and you're comparing a flat image against a live page that may have already changed. One revision round later, the screenshots are stale.
Send the staging URL with specific questions
Most homepages live on a staging URL before launch — a Webflow preview, a Framer share link, or a Vercel preview deploy. Send the client the URL alongside two or three targeted questions rather than an open 'what do you think?' Useful ones: 'Does the headline make the offer clear in five seconds?', 'Would you click this CTA?', and 'Is the nav missing anything?' Specific questions get specific answers. 'Looks great!' and 'can we make it pop?' are what you get from an open prompt. The unavoidable downside: their email replies are disconnected from the page. 'The bit near the top' and 'the blue section' each need a follow-up exchange before you know what to fix. Budget for at least one extra round per vague reply.
Share a Figma prototype or Webflow preview
If you designed the homepage in Figma, click Share → 'Can view' → Copy link. The client can open the prototype in a browser without Figma installed — but leaving a comment requires a Figma account. If your client already uses Figma internally, this is the most accurate view of the design. If they don't have an account, they hit an account-creation screen before they can type a single note. That's a real friction point, especially when the client is a small business owner reviewing their first homepage draft. Webflow's preview share link and Framer's share link have the same account gate on comments. Worth knowing before you send the link and then wonder why they called instead of commenting.
Share a review link they annotate directly on the page
The most reliable method for getting actionable homepage feedback: give the client a link they open in any browser — desktop or phone — and click the exact element they mean. The hero headline, the CTA button, the nav item, the testimonial section. Their note lands pinned to that spot. You see it in a thread, reply, and fix it. No account or extension on their side. Proxy-based review tools (Markup.io, Drafty, BugSmash) wrap your staging URL or live page in an annotation layer and give you a shareable feedback link. The practical edge on a homepage: the client can annotate the page on their laptop and then open the same link on their phone to check the mobile layout — both sets of notes land in the same thread. That matters for homepages specifically because 'it looks good on desktop' is the comment that always precedes 'it looks off on my phone.'
If you're a freelance designer waiting on client sign-off before a homepage launch, paste the staging URL into Drafty and share the link instead. Your client clicks the hero, the nav, or the CTA button and pins a note right there — no account, no extension. They can check it on their phone too and the notes all land in the same thread. When you push a revised version it lives on the same link, so there's no re-sending URLs.
Open a live demoQuestions
- How do I get homepage feedback from a client without asking them to sign up?
- Use a proxy-based review link. The client opens the URL in any browser, clicks the element they want to flag, and leaves a note — no account or extension needed. Figma and Framer require a login to comment. Browser extensions like BugHerd require the client to install something. A proxy link is the only method with zero friction on a client's end.
- What questions should I ask a client when reviewing a homepage?
- Specific questions beat open-ended ones: 'Does the headline make the offer clear in five seconds?', 'Is anything missing from the nav?', 'Would you click this CTA?', and 'Does this look right on your phone?' Vague prompts ('What do you think?') get vague answers ('Love it!' or 'Make it pop') that don't help you ship.
- How do I collect homepage feedback on both desktop and mobile?
- Browser extensions don't work on iOS Safari or Android Chrome, so they're ruled out for mobile review. A proxy-based review link works on any device: the client opens it on their laptop, then opens the same link on their phone. Both sets of pinned notes land in the same thread. This matters for homepages because clients almost always check mobile before they'll sign off.
- How many rounds of feedback should I expect on a homepage?
- One to three rounds is typical. Element-pinned review links tend to run shorter because you can fix the exact spot the client flagged without a back-and-forth to locate it. Email-based reviews typically run longer: each vague note ('the top section') requires at least one clarifying exchange before you can act on it.
- Can I get homepage feedback on a Webflow or Framer site before it goes live?
- Yes — paste your Webflow preview link or Framer share link into a proxy-based review tool. It wraps the page in an annotation layer. One caveat: some Webflow preview URLs redirect through an authentication screen that breaks the proxy render. If the tool shows a Webflow login page instead of your design, publish to a staging domain first.
- What's the difference between homepage feedback and landing page feedback?
- A homepage typically covers nav, hero, multiple sections, and footer — clients have more opinions and more surface area to cover. A landing page is focused on one CTA. Homepage reviews also almost always require a mobile check, since clients use their homepage as their business card and they know what it looks like on their own phone.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.