How to annotate a landing page
To annotate a landing page, share a review link the client can open in any browser, click the exact element they mean — headline, hero image, CTA button — and leave a pinned note. No account, no install. For a one-off pass you control yourself, export a screenshot and mark it up in Preview or Figma. The review-link approach is the only one that gets you unambiguous client feedback before a deadline.
Screenshot and mark up (fast, one person)
Take a full-page screenshot of the staging page — on Mac, GoFullPage in Chrome grabs the whole scroll in one shot; on Windows, the Snipping Tool with the scrolling-window mode does the same. Open it in Figma, Preview, or Canva and draw arrows, add text callouts, and circle problem areas. Good for a solo pass before you send anything to the client. The limit: the screenshot is already stale the moment the page changes, and if the client marks up their own copy and emails it back, you're reconciling two flat images against a live page. This method breaks down after round one.
Share the staging URL via a proxy-based annotation tool
Most landing pages sit on a staging URL (Webflow preview, Framer share link, Vercel preview deploy) before launch — which means the client can open it in a browser, but they have no obvious way to leave anchored feedback. Paste the staging URL into a proxy-based annotation tool: the tool wraps the page in a review layer, gives you a new shareable link, and your client clicks any element to pin a note directly to it. No code to add, no extension to install. One real gotcha: some Webflow and Framer preview links require authentication or send a redirect that breaks the proxy render — test your specific staging URL before sharing it with the client, because a broken preview link is a bad first impression.
Share a Figma or Framer prototype and ask for comments
If you built the landing page in Figma, click Share → 'Can view' → Copy link. Anyone can open the prototype in a browser. To leave a comment, they tap the speech bubble icon — but they have to log in or create a Figma account first. This has been an open complaint from designers since at least 2021. If your client already uses Figma, this is the most faithful view: live layers, toggleable variants, exact dimensions. If they don't, the account gate is friction on a deadline. Framer's share link has the same trade-off: rich interaction preview but a Framer login to comment.
Share a review link they annotate without signing up
The cleaner path for client sign-off: share a link they open in any browser — desktop or phone — and click the element they mean. The headline, the CTA, the hero image. Their note lands pinned to that exact spot in a thread you can see and reply to. They don't create an account, they don't download anything. This is what tools like Markup.io and Drafty are built for. The practical upside on a landing page specifically: clients can annotate the same element from both their desktop and their phone, which matters when the page needs to look right at both sizes. One round of vague email notes ('can we make the button more prominent?') can cost 2–3 hours of back-and-forth; a pinned note on the exact button removes the ambiguity immediately.
If the point is getting the client's sign-off — not annotating it yourself — share a Drafty link instead of a staging URL. Paste the page URL, send the link, and your client clicks the headline, the hero image, or the CTA and pins a note right there. No account, no extension. Their feedback arrives in one thread, each comment anchored to the element they meant. You reply, fix it, and the updated page lives on the same link.
Open a live demoQuestions
- How do I annotate a landing page before it goes live?
- Paste your staging URL (Webflow preview, Framer share link, Vercel preview deploy) into a proxy-based review tool. It wraps the page in an annotation layer and gives you a shareable link. Your client opens it, clicks the element they want to flag, and types a note — all without installing anything. The page doesn't need to be public; it just needs to be accessible via a URL.
- Can my client annotate a landing page without creating an account?
- Not in Figma — Figma requires a login to comment. Emailed screenshots also require the client to have markup software of their own. Proxy-based review tools (Markup.io, Drafty) are the exception: your client opens the link in any browser and clicks to leave a note — no account, no install, no email back-and-forth.
- What is the best way to collect client feedback on a landing page?
- A shared review link they can annotate in any browser. The alternatives — email threads, screenshots, PDF markups — lose their connection to the actual page the moment it changes, and each revision cycle means emailing a new file. A link-based approach keeps every note pinned to the exact element, in one place, across all revision rounds.
- How do I annotate a Webflow or Framer landing page for review?
- Paste the Webflow preview link or the Framer share link into a proxy-based annotation tool to add a comment layer. One caveat: some Webflow preview URLs redirect through an authentication step that breaks the proxy render — if the tool shows a login screen instead of your design, you may need to publish to a staging domain first. Framer share links generally load cleanly in proxy tools.
- Can I annotate a landing page on mobile?
- Browser extensions don't work on iOS Safari or Chrome for iOS. A proxy-based review link does work on mobile — your client opens it, taps the element they mean, and types a note. This is especially useful for landing page reviews because clients often check how the page looks on their phone before sign-off.
- How is annotating a landing page different from annotating a general website?
- Landing pages are usually reviewed against a deadline and need explicit sign-off on specific elements — headline, CTA copy, hero image. The feedback cycle is typically one or two rounds, often with a non-technical client. That makes the low-friction review link (no account, no install) a better fit than an embedded widget that requires code access to a site you may not own.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.