Skip to main content

Add a Feedback Widget to WordPress

Published June 9, 2026

Add a feedback launcher to WordPress with one footer snippet. Works with popular cache plugins when you exclude the script from over-aggressive minify rules.

WordPress site with feedback widget installed via footer script

Add a feedback widget to WordPress with one footer script snippet. Plugins such as Insert Headers and Footers or WPCode paste the embed once site-wide. No custom post type or heavy admin UI required.

WordPress feedback plugins often bundle upsells or lock exports. A script embed behaves like analytics: one snippet, site-wide coverage, triage in a separate inbox with client debug on every report.

WordPress admin with header and footer script plugin settings

Option A: Header/Footer Script Plugin

Plugins such as "Insert Headers and Footers" or WPCode let you paste the FeedBlox snippet once. Put it in the footer section so it loads after page content.

Clear page cache (WP Rocket, LiteSpeed, etc.) after saving. Submit a test report from the live URL to confirm the launcher appears.

  1. Install a header/footer injection plugin if you do not already use one
  2. Paste the FeedBlox snippet in the footer field
  3. Save and purge all page caches
  4. Open the site front end and submit a test report
WordPress child theme footer.php with script embed

Option B: Theme footer.php

In a child theme, paste the script tag before in footer.php. Updates survive theme changes only if you use a child theme.

Do not edit parent theme files directly - they will be overwritten on theme update.

Child theme footer.php (before closing body)

<script
  src="https://feedblox.net/widget.js"
  data-site-id="YOUR_SITE_ID"
  data-token="YOUR_EMBED_TOKEN"
  data-position="bottom-right"
  async
></script>
<?php wp_footer(); ?>
</body>
WooCommerce checkout page with feedback widget for payment bugs

Multisite, Cache, and WooCommerce

WooCommerce checkout bugs benefit from console and network capture on failed payment XHR calls. A report with a 402 on /wc-ajax/checkout is faster to fix than "payment did not work."

Disclose client debug in your privacy notice. Console and network capture is powerful. Say so to visitors.

  • Multisite: each domain may need its own FeedBlox site and verification
  • WooCommerce: place launcher on checkout, cart, and my-account routes
  • Exclude widget.js from combine/minify if your optimizer breaks data attributes
  • Object cache plugins: purge after snippet changes
  • CDN: ensure widget.js is not cached with stale tokens after rotation

Related Guides

Product: Free feedback widget page.

Also read: FeedBlox vs Typeform comparison.

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