From the Blog

Add a Feedback Button in 5 Minutes

By the FeedBlox Team Jul 19, 2026 Updated Aug 26, 2026

Five minutes of install beats five days of unreproducible Slack threads. Create a site, paste the embed, verify the domain, and test one report.

Developer adding a website feedback button with a laptop and timer nearby

The five-minute install is always five minutes until someone opens the theme editor.

Adding a feedback button to your website is still a short path when you treat it like a one-script embed: create a site, paste the snippet before the closing body tag, verify the domain, and send one test report. This guide is the checklist without the CMS folklore.

Minute 1-2: Create the Site

Sign in to FeedBlox and create a site for the production domain you will embed on. Use a separate site for staging if you want clean inboxes.

Copy the embed token and site id from the widget settings. Keep them out of public git history the same way you treat other client keys that are meant for your domains only.

Create a site for your production hostname
Optional: create a second site for staging
Copy the script snippet from Widget settings

Minute 3: Paste the Script

Drop one async script tag into the shared footer, root layout, or CMS custom code block so every route gets the launcher.

If a chat widget already owns the bottom-right corner, set data-position or offset in the dashboard so the feedback button stays clickable.

Site-wide embed

HTML

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

Minute 4: Verify the Domain

Complete domain verification so only your hostname can send reports. Unverified embeds reduce spam risk for everyone else and keep your inbox honest.

Publish or hard-refresh the page after verification. Cached HTML without the new script is the usual reason the button "does not appear" in the first five minutes.

Minute 5: Send a Test Report

Open the live page, click the launcher, submit a short comment, and open the FeedBlox inbox. Confirm URL, console buffer, and failed network entries when you triggered an error.

Optional next step for SaaS apps: call FeedBlox.setMetadata after login with opaque user and plan ids so triage does not ask visitors to type account details.

Launcher visible on mobile and desktop
Test report lands with the expected site
Client debug present on Free, Pro, and Max
Chat and cookie banners do not cover the button

Related Guides

Product: Install guide.

FAQ

How long does it take to add a feedback button to a website?

Most teams finish in under ten minutes: create a site in the dashboard, paste one async script tag, verify the domain, and submit a test report. Theme editors and CMS footers are usually the slow part, not the snippet.

Do I need a package install to add a feedback widget?

No. A site-wide script tag is enough for marketing sites, Webflow, WordPress, and most SaaS shells. Use your root layout or shared footer so every route gets the launcher.

What should I verify after install?

Open a staging page, trigger a known error if you can, submit one report, and confirm the inbox shows the comment plus URL, console lines, and failed network entries.

Where should the feedback button appear?

Bottom-right is the default for LTR apps. Offset it above chat or cookie banners. Keep the same corner on marketing and app routes so visitors learn one place to report issues.

Is FeedBlox free to try for a first install?

Yes. FeedBlox Free includes multiple sites, a monthly report cap, and client debug on every submission so you can prove the workflow before upgrading.