How to share a web page for feedback
Paste the URL into a review tool and share the link it generates. Your client clicks the exact element — headline, pricing row, mobile nav — and leaves a note pinned to it. No account needed. Sending the raw URL works, but feedback arrives as descriptions rather than references, and every revision starts with a guessing step.
Wrap the page URL in a review layer
Paste the URL into a review tool — Drafty, Pastel, Ruttl — and you get a second URL: the review link. Your client opens it, sees the same page, but can now click any element — the hero, the CTA, the footer copy — and pin a note right to it. What you're avoiding: 'the headline near the top looks off' arriving in your inbox with no element reference. One caveat: if the page is behind a login, the tool can't render it. Use public or staging URLs; authenticated pages need a full-page screenshot instead.
Send the review link, not the raw page URL
The common mistake: sending the live URL with 'let me know what you think.' Your client opens the page, has nothing to click, and defaults to iMessage, a voice note, or a paragraph email you have to decode before opening a file. Send the review link with one line: 'Click anything you'd like changed and leave a note on it — no account needed.' That sentence turns 'can you change the thing at the top?' into a pinned note on the exact element. One link works for multiple reviewers — notes land in the same thread, not split across two email chains.
Collect all notes before acting on any of them
Wait for the client to finish before making the first change. The expensive pattern: three notes appear on the pricing section, you start revising, and four more arrive ten minutes later — two contradicting the first three. On a shared board, all notes are visible before you touch the file. Flag conflicts in a reply ('you and Sarah disagree on the CTA — which wins?'), then open the file once the thread is stable. One complete pass beats three half-passes.
Push the revision to the same link
Update the page at the same URL. The review link reflects the current version, and the previous round's notes stay visible in the thread. Your client doesn't need a new URL and can see which notes are resolved and which are still open. Designers who share a new link per round discover by round three that the resolved notes from round one are gone — and the client can't tell if their earlier feedback was heard. Same link, every round.
Need a client to review a specific page? Paste the URL into Drafty and share the link. They click the headline, the pricing table, the mobile nav — wherever they'd change something — and leave a note pinned right there. No account, no screenshot, no voice note to transcribe. Every comment lands in one thread on the exact spot they meant. When you've revised the page, the same link reflects the update — you don't send a new URL, and the old notes stay in the thread.
Open a live demoQuestions
- How do I share a web page for feedback without the client needing an account?
- Paste the page URL into a review tool (Drafty, Pastel, Ruttl) and share the review link it generates. The client opens it in any browser, clicks the element they mean, and leaves a note — no signup, no extension. The tool renders the live page with a commenting layer on top.
- What is the best way to get feedback on a specific web page from a client?
- Send a review link that lets them click the exact element and pin a note to it. Email-based feedback produces descriptions ('the section near the top') that you have to map to actual elements before a revision can start. A pinned note removes that step.
- Can I share a web page for feedback on mobile?
- Yes — review links open in any mobile browser and support touch-to-comment. Worth checking first on your own phone: layout issues at narrow widths are better caught by you than reported by the client.
- How do I share a web page that's still behind a login for feedback?
- Review tools can't render pages that require authentication — the tool sees a login screen, not the page. Options: take a full-page screenshot and share it as a reviewable image, or temporarily publish the page on a staging URL, wrap that in a review link, and share that instead.
- How do I collect feedback from multiple clients on the same web page?
- Share one review link with everyone. Notes from different reviewers land in the same thread — you catch conflicting feedback before the revision starts, not after. Separate email chains to two stakeholders guarantee you won't see the conflict until round two.
- Why does sending a raw URL lead to more revision rounds?
- Because your client has no mechanism to point at the element they mean, so feedback arrives as verbal descriptions. 'The button near the top' might map to the nav CTA, the hero button, or a sticky bar. You guess, revise, and send it back — they say it was the other button. A pinned comment on the exact element removes that guessing step.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.