How to get feedback on a product page
To get feedback on a product page, share a review link your client opens in any browser and clicks the exact element they mean — the hero image, the price, the buy button — and leaves a pinned note. No login, no install. Email and screenshots work for a first pass but break down fast: clients describe a spot instead of pointing at it, and you spend an extra round just locating what they meant before you can fix it.
Screenshot markup — good for your own pre-check, not client sign-off
Before sharing anything, run a full-page screenshot of your staging build and mark it up yourself. On Mac, GoFullPage in Chrome captures the full scroll in one shot. Open it in Figma, drop a few callout arrows on the hero, the price block, and the CTA, and you have a pre-flight checklist you can walk through before the client ever sees it. This is a solid first pass on a product page because you can catch obvious layout breaks — the buy button floating too close to the fold, the product image cropped awkwardly — before they become a client note. What it can't do: collecting feedback this way (emailing the annotated screenshot and asking the client to edit and return it) generates a second version you then have to reconcile against your live file. Even one round makes the screenshots stale.
Send the staging URL with specific questions attached
Every decent e-commerce or marketing stack gives you a staging URL before launch — Shopify's password-protected preview, a Webflow staging domain, or a Vercel preview deploy. Send the URL to the client, but don't just ask 'what do you think?' That's a prompt for 'looks great!' Write two or three pointed questions in the email body: 'Does the headline make the product's main benefit clear in under five seconds?' and 'Would you trust the price shown without seeing any more context?' are the questions that get you actionable answers on a product page. The persistent problem: replies arrive disconnected from the page. 'The photo on the right' and 'the call-to-action' need a back-and-forth to locate before you know which element they actually mean. Expect one extra clarification exchange per vague reply — budget for it when you're setting revision timelines.
Collect Figma comments if the page is still a design file
If the product page hasn't been built yet and still lives in Figma, share a view-only prototype link and enable comments. Clients can leave a note pinned to a frame element without a full Figma editor account — they sign in as a viewer for free. This is the right approach at the wireframe or high-fidelity mockup stage because every comment lands at a named Figma layer, not just a screen coordinate. The limit: Figma comments pin to coordinates, not to live HTML elements, so if you move a section in the layout between rounds, the pins drift. For the final built page — live pricing, real product images, actual typography rendering in a browser — switch to a live-page review tool. Figma at the design stage plus a live review tool at the build stage is the two-step pattern that covers both fidelity levels cleanly.
Share a review link they annotate directly on the live page
The method that consistently produces specific, usable feedback: give the client a link they open in any browser — desktop or phone — and click the exact element they mean. The hero image. The price. The 'Add to cart' button. Their note arrives pinned to that element in a thread. You reply, mark it resolved, push the fix. A product page has a small set of high-stakes elements — buy button, price, hero, trust signals — and every one of those elements is easy to point at when the client can tap it directly. The mobile view matters especially on a product page: clients often check how the page renders on their phone before approving it, and browser extension tools don't work on iOS Safari or Android Chrome. A proxy-based review link works on both. One pinned note on the actual buy button beats three email exchanges trying to figure out which button they meant.
If you're a designer waiting on client sign-off before a product page goes live, share a Drafty link instead of the staging URL directly. Paste the page URL, send the link, and the client clicks the hero, the price, or the buy button and leaves a pinned note right there — no account, no extension. Every comment lands in one thread, anchored to the element they meant. Push a revised version and it lives on the same link — no re-sending files, no new URLs, no hunting through three email chains to find out which CTA they meant.
Open a live demoQuestions
- How do I get client feedback on a product page 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 types a note, no account required. Figma requires a viewer login to comment. Browser extension tools (like BugHerd) require the client to install the extension first. Proxy tools (Markup.io, Drafty) don't require either.
- How do I ask a client to review a product page?
- Send the review link with two or three specific questions rather than an open 'what do you think?' Good prompts for a product page: 'Does the headline make the main benefit clear in five seconds?' and 'Does the price feel right given what's on the page?' Specific questions tied to specific page elements get you something you can act on. Vague prompts get vague answers.
- What is the best way to get feedback on a product page CTA?
- Let the client click the actual CTA button and leave a note pinned to it — not describe it in an email. On a product page the buy button is usually the element with the highest revision risk: clients often want to change the label, colour, or placement late in the process. Getting that feedback anchored to the actual element removes the 'which button?' back-and-forth.
- How do I collect product page feedback from mobile?
- Browser extensions don't work on iOS Safari or Android Chrome, so any extension-based tool won't work when a client checks the page on their phone. Proxy-based review links work on mobile: the client opens the link, taps the element, and types a note. This matters for product pages in particular — most clients will open the page on their phone at least once before sign-off.
- How many feedback rounds should I expect on a product page?
- One to two rounds is common when the client can annotate directly on the page, because element-pinned comments remove the back-and-forth needed to locate what they meant. Email-based feedback tends to run longer — each vague reference ('the top bit', 'the image section') needs at least one exchange to clarify before you can make the change.
- Can I get feedback on a product page that isn't live yet?
- Yes — most proxy-based review tools work on any publicly accessible URL, including Shopify password-protected previews, Webflow staging domains, and Vercel preview deploys. If the page is still in Figma, use prototype view-only comments for the design stage, then switch to a live-page review link once it's built.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.