Visual Feedback for Webflow Sites

Webflow is genuinely magic for building websites fast. Client feedback on Webflow sites is, historically, the opposite of magic.

You share the staging URL. The client opens it. Something looks off. They take a screenshot, crop it badly, and send it in an email with the subject line “Few things.”

You squint at the screenshot, try to figure out which breakpoint they're on, and realise you have to schedule a call just to understand the feedback well enough to act on it.

This page is about fixing that — specifically, how to add visual feedback to your Webflow site without touching Webflow's CMS or writing custom JavaScript.

Why Webflow feedback is uniquely tricky

Webflow's visual editor is powerful, but it creates some feedback-specific complications that generic feedback tools don't handle well.

Staging URLs are temporary and access-controlled

Webflow's staging URLs change with each publish. Tools that work by parsing a URL or bookmarking a specific link break when the staging URL updates. You need a feedback widget that lives on the page itself — not one that references the URL from the outside.

Responsive breakpoints make “it looks wrong” ambiguous

Webflow sites are built across desktop, tablet, and mobile breakpoints. When a client says “the header looks off,” they might mean desktop, tablet, mobile, or some combination. Without viewport dimensions in the report, you're guessing.

No-code clients are particularly hard to brief on feedback tools

Clients who chose Webflow because they liked the no-code promise are often the same clients who won't install a browser extension or create an account for a feedback platform. Your tool needs to work without asking them to do either.

The Feedzap + Webflow setup

Adding Feedzap to a Webflow site takes about two minutes. No code, no Webflow integrations required.

Step 1 — Copy the Feedzap script tag

From your Feedzap dashboard, copy the one-line script tag for your project.

Step 2 — Paste it into Webflow's custom code

In Webflow Designer: Project Settings → Custom Code → Before </body> tag. Paste the script. Done.

Step 3 — Publish to staging

Publish your Webflow site to the staging URL. The Feedzap button appears in the corner of the page automatically.

Step 4 — Send the staging link to your client

No instructions needed. The button is there. Clients click it, point at what they want to flag, add a note, and send. Feedzap captures: screenshot, CSS selector, viewport dimensions (so you know which breakpoint they're on), browser, OS, and URL.

Step 5 — Receive reports in your workflow

Connect Feedzap to Slack, Notion, Linear, or wherever you track tasks. Reports arrive as structured items — not emails, not screenshots, not voice notes.

What Feedzap captures on every Webflow report

Real-world example: from vague feedback to first-try fixes

The situation

A Webflow freelancer building a portfolio site for a creative agency client had been through four feedback rounds. Most of the client's comments were about mobile layout — but the client never specified they were on mobile. The freelancer kept making desktop changes that didn't address the actual issues.

What they did

Added Feedzap to the staging site before round five. Sent the client the staging link with one message: “If you see anything, use the button in the corner to show me.”

The result

• The client's first Feedzap report came with viewport: 390×844 — immediately identifiable as iPhone
• Every piece of feedback was actioned on first pass
• No more ambiguous desktop/mobile confusion
• Round five became the final round