Skip to main content

Add a Feedback Widget to Webflow

Published June 7, 2026

Install a feedback launcher on every Webflow page with one footer code block. Test on published URLs, not the Designer preview.

Webflow website with custom footer code for a feedback widget

Add a feedback widget to Webflow by pasting one script snippet in Project Settings > Custom Code > Footer Code. Every published page loads the launcher. FeedBlox uses a plain async embed with your site ID and token - no Webflow marketplace app required.

Webflow sites need a site-wide embed because pages export as static HTML. Do not duplicate an embed element on every page. Footer code runs once and covers the whole project after publish.

Webflow project settings with footer custom code for widget install

Install Steps

  1. Create a FeedBlox site using your Webflow primary domain (for example www.example.com)
  2. Complete domain verification from the FeedBlox dashboard
  3. Copy the widget snippet from Site > Widget settings
  4. In Webflow: Project Settings > Custom Code > paste before in Footer Code
  5. Publish to staging or production
  6. Open the live URL and submit a test report
Published Webflow site open in a browser for widget testing

Designer Preview vs Published Site

The widget may not behave correctly inside the Webflow Designer canvas. Always verify on a published URL with your verified domain.

If you use Webflow staging domains, add a separate FeedBlox site or update verification when you switch domains. FeedBlox Free includes three sites for staging, preview, and production.

Install on staging first. Submit a controlled error or broken flow. Confirm the inbox row before production.

Creative agency team managing multiple client Webflow sites

Marketing vs Client Portal

Agencies often run Webflow for marketing and a separate app for the product. Use one FeedBlox site per domain so feedback stays in the right inbox.

Client debug still helps on marketing sites when forms, analytics tags, or third-party scripts throw JS errors. A visitor reporting a broken demo form is more useful with console output than a vague contact page message.

  • Marketing site: sentiment plus bug path for broken forms and scripts
  • Client portal on another stack: separate FeedBlox site and embed token
  • Per-client inboxes when you manage multiple Webflow properties

Embed Snippet Reference

Footer Code block

<script
  src="https://feedblox.net/widget.js"
  data-site-id="YOUR_SITE_ID"
  data-token="YOUR_EMBED_TOKEN"
  data-position="bottom-right"
  async
></script>

Related Guides

Product: Website feedback widget.

Also read: User feedback collection use case.

Related Posts

Product Guides

Abstract geometric console structure behind the signup call to action

Ship bug reports with console logs on every plan

New accounts get Pro free for your first month: unlimited reports, screenshots, recordings, webhooks, and collaborators. No credit card. After the trial, Free forever: 3 sites, 150 reports/month, no credit card.

Start Free

No credit card required