How to get feedback on a marketing site
To get useful feedback on a marketing site, give your client a specific spot to react to — not an email asking 'what do you think?' Share a link they can annotate directly on the live page, or a short Loom walkthrough with a structured question list. The fastest method when the site is built: a shared annotation link where they click the exact element and leave a note pinned to it — no login, no 'the bit under the hero.'
Share an annotation link on the live page
If the site is deployed to a staging URL — Vercel preview, Netlify draft, a subdomain — wrap it in a review tool and send that link. Your client opens it in any browser, hovers the element they mean (the hero headline, the pricing card, the CTA button), clicks, and leaves a note pinned right there. You see every comment anchored to the exact spot, reply in a thread, and mark it done as you ship each fix. No install on their end, no account. The common mistake designers make is sending the raw staging URL and asking for feedback in a follow-up email. The client visits the page, forms an opinion, then switches to their inbox to type it — and by the time they're writing, half the specificity is gone. 'The hero feels off' is genuinely what they remember; what they actually noticed was that the H1 doesn't match the ad copy they approved. An annotation link collapses the gap between noticing and noting.
Walk through it on a screen share
For a marketing site that involves real strategic decisions — the positioning, who the hero speaks to, whether the pricing anchors correctly — a 30-minute Zoom is faster than three email rounds. Share your screen on the live page, scroll through it without explaining your choices first, and let the client react in real time. Ask one focused question per section: 'Does this headline make sense for the person you're trying to sign up?' and 'Is the pricing clear at first glance?' beat an open 'what do you think of the page?' every time. One thing to watch: clients on a screen share tend to co-design in real time — 'what if the CTA said X?' for five minutes on a button copy decision. Keep the call diagnostic, not editorial. Take notes during, send a bulleted action list after, and make the changes yourself. The call is for signal-gathering, not collaborative copy editing.
Send a short structured question list
When you need written, asynchronous feedback — the client is in a different time zone, or there are multiple stakeholders who shouldn't influence each other — send a short form with three to five pointed questions alongside the staging URL. Focus on the decisions that are actually still open: 'Does the hero describe the problem your customers come in with?' and 'Is anything missing from the features section?' Open-ended questions like 'Is there anything you'd change?' produce long lists of personal preferences and almost no signal about whether the page will convert. Most freelancers send too many questions. Three focused ones get answered; ten get a 'looks good' and a follow-up call. Ask about the reader's experience ('would someone landing here from a Google ad know immediately what to do?'), not about the design ('do you like the colors?').
Record a Loom walkthrough and ask for a reaction
When the client can't be on a call and the site has enough moving parts that a static link doesn't show it well — scrolling animations, hover states, a complex nav — record a 3–5 minute Loom walking through each section. Narrate what you were trying to achieve and what you're still unsure about. End with one question you actually need answered. Share it alongside the live staging link so they can poke around after watching. Loom lets clients leave timestamped comments on the video, which is useful for quick reactions, but it doesn't replace direct annotation on the page — the comments are on your narration of the page, not on the page itself. Use it as an intro, not as the review mechanism. The one place Loom genuinely wins: clients who won't open or explore a staging URL on their own will watch a 4-minute video.
If your client keeps emailing notes like 'the hero doesn't pop' or 'the copy feels off in the middle section' — without pointing at anything specific — paste the staging URL into Drafty and send that link instead. They open it in any browser, click the exact element they mean, and pin a note right there. No account, nothing to install. Every comment lands in one thread, anchored to the spot, and stays on the same link through every revision round. When you push a new version, they see it at the same URL — no re-sending, no 'which link is current?'
Open a live demoQuestions
- How do I share a marketing site for client review before it goes live?
- Deploy to a staging URL — Vercel generates a preview link on every push, Netlify has draft deploys, and most hosts let you password-protect a subdomain. Send that URL. If you need the client to comment on specific elements rather than reply by email, wrap it in an annotation tool first: they open the link, click the element they mean, and leave a note pinned to it without logging in.
- How do I get specific feedback on a marketing site instead of vague comments?
- Specificity comes from the method, not the client. When they open a staging URL and then reply by email, they've already lost the exact element they were reacting to. An annotation link forces them to click the element before they type — so 'the hero feels flat' becomes 'this headline doesn't match what we said in the brief.' Alongside the right tool, ask pointed questions: 'Does the CTA make the next step obvious?' instead of 'what do you think?'
- How many rounds of revisions should a marketing site take?
- One or two rounds when the brief is tight and the client can comment inline on the actual page. Three or more usually means the positioning wasn't aligned before design started — the page is answering a question the client wasn't asking. A 20-minute call to lock the hero message, ICP, and one main CTA before you build cuts rounds more than any review tool. Email-based feedback runs longer because each vague note needs at least one clarifying exchange before you know what to fix.
- How do I collect marketing site feedback from multiple stakeholders?
- Send everyone the same annotation link. When four stakeholders comment on the same page, all notes are in one place with no version collisions. Sending separate copies — or a staging URL and asking each person to email you — produces conflicting priorities with no way to see which feedback came first or whether two people reacted to the same element. Resolve each thread yourself and leave the history there as the record of what changed and why.
- What questions should I ask when getting feedback on a marketing site?
- Ask about the reader, not the design. 'Would someone landing here from a Google ad know what to do next?' and 'Does the hero describe the problem you're actually solving?' give you actionable signal. 'Do you like the layout?' and 'what would you change?' give you opinions. Limit it to three questions — ten questions get a 'looks good' and a follow-up call that covers the same ground you asked about.
- Should I use a Loom video or a live link for marketing site feedback?
- Use both, in order. A short Loom walkthrough gets a client who won't explore a staging URL to actually see the page. Then send the live staging link (or an annotation version of it) for the real review — timestamped video comments sit on your narration of the page, not on the page itself, so they don't replace direct annotation.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.