# FeedBlox (FeedBlox.net)

> FeedBlox is a lightweight feedback and bug-reporting widget for websites. Visitors submit ratings, comments, and (on paid plans) screenshots from any page. Reports land in one inbox per site with developer context: console logs, failed network calls, JS errors, optional metadata, and a click-trail repro summary.

Official product site: feedblox.net. Not feedstack.app. FeedBlox is operated under terms in Illinois, United States. General contact: hello@feedblox.net

## Product

- [Home](https://feedblox.net/): Website feedback and bug report widget with client debug on every plan.
- [About](https://feedblox.net/about): Built in Chicago; company overview.
- [Customers](https://feedblox.net/customers): Customer stories and published review outcomes.
- [Why FeedBlox](https://feedblox.net/why-feedblox): Official FeedBlox.net product; disambiguation from feedstack.app and directory listings.
- [Features](https://feedblox.net/features): Widget input modes, client debug, inbox, AI summaries, automations, webhooks.
- [Free feedback widget](https://feedblox.net/free-feedback-widget): Free embed for websites - install steps and plan limits.
- [Use cases](https://feedblox.net/use-cases): Bug reporting, user feedback, developer-friendly capture.
- [Bug reporting use case](https://feedblox.net/use-cases/bug-reporting): JavaScript bug reports with console logs.
- [User feedback use case](https://feedblox.net/use-cases/user-feedback): Website feedback tool and one inbox.
- [Developer feedback use case](https://feedblox.net/use-cases/developer-feedback): Client debug on every plan.
- [Feedback inbox](https://feedblox.net/docs/inbox): Read, filter, and export reports.
- [Feedback triage](https://feedblox.net/docs/triage): Open, in review, and done workflow per site.
- [Feedback automations](https://feedblox.net/docs/automations): Auto-tag by sentiment or comment text.
- [Webhook integrations](https://feedblox.net/docs/webhooks): Signed HTTPS payloads to Slack, Linear, custom tools.
- [Documentation](https://feedblox.net/docs): Getting started guide, install steps, FAQ, and help links.
- [Getting started guide](https://feedblox.net/docs/getting-started): Account setup through first inbox report.
- [Install guide](https://feedblox.net/docs/install): JavaScript feedback widget embed steps.
- [FAQ](https://feedblox.net/docs/faq): Widget install, plans, privacy, billing, and integrations.
- [Contact support](https://feedblox.net/docs/contact): hello@feedblox.net
- [Blog](https://feedblox.net/blog): Guides on feedback widgets and bug reporting.

## SEO landing pages

- [Bug Report Widget](https://feedblox.net/bug-report-widget): Lightweight bug report widget for SaaS and web apps. Collect reports with console logs, network errors, JS stack traces, and click-trail repro steps.
- [Website Feedback Widget](https://feedblox.net/website-feedback-widget): Website feedback widget for comments, feature ideas, and bug reports in one inbox. Ratings, sentiment trends, and optional dev context on every plan.
- [Console Log Bug Reports](https://feedblox.net/console-log-bug-reports): Capture console logs with user bug reports automatically. Bounded buffer, submit-time snapshot, and inbox view for console and network errors.
- [Feedback Widget for SaaS](https://feedblox.net/feedback-widget-for-saas): Feedback widget for SaaS. Capture trial feedback, onboarding friction, feature ideas, and production bugs with dev context in one inbox.
- [Bug Reporting Tool for Developers](https://feedblox.net/bug-reporting-tool-for-developers): Developer bug reporting tool with console logs, network errors, JS stack traces, and click trails on every report. Less back-and-forth, one lightweight embed.
- [Feedback Button](https://feedblox.net/feedback-button): What a website feedback button is, where to place it, which input mode to use, and how to add one to your site with a single script tag.
- [Bug Report Template](https://feedblox.net/bug-report-template): A copy-paste bug report template with the fields engineers actually need, plus format variants for Jira, GitHub, Word, and Sheets, and worked examples.
- [What Is a Bug Report](https://feedblox.net/what-is-a-bug-report): A bug report is a structured record of unexpected software behaviour. What it contains, how it differs from a feature request, and how to write one.
- [User Feedback Examples](https://feedblox.net/user-feedback-examples): Real user feedback questions grouped by what you are trying to learn, a reusable feedback report template, and how to turn responses into shipped changes.
- [Feedback Triage for a Small SaaS Team](https://feedblox.net/blog/setting-up-feedback-triage-for-a-small-saas-team): A small SaaS team needs a private inbox, three statuses, and a weekly ritual - not a public roadmap theater for every production bug.
- [Route Feedback Webhooks to Slack and Linear](https://feedblox.net/blog/routing-feedback-webhooks-to-slack-and-linear): Paste a Slack URL or middleware endpoint, verify signatures, and route by automation tags so engineering sees bugs without copy-paste.
- [Using AI to Summarize User Feedback](https://feedblox.net/blog/using-ai-to-summarize-user-feedback): AI can cluster themes across many reports. It should not replace console logs, failed network calls, or a clear triage owner on each bug.
- [Feedback Widget vs Bug Tracking Tool](https://feedblox.net/blog/feedback-widget-vs-bug-tracking-tool): A feedback widget captures user-initiated reports from the live site. Bug trackers and error monitors solve different layers. Here is how to pair them.
- [Add a Feedback Button in 5 Minutes](https://feedblox.net/blog/how-to-add-a-feedback-button-to-your-website-in-5-minutes): Five minutes of install beats five days of unreproducible Slack threads. Create a site, paste the embed, verify the domain, and test one report.
- [Visual Bug Reporting Alternatives Compared](https://feedblox.net/blog/visual-bug-reporting-alternatives): Visual bug tools differ by workflow: QA handoff, agency pins, and screenshot capture. This guide maps alternatives without pretending one tool wins every row.
- [Canny Alternatives for Bug Capture](https://feedblox.net/blog/canny-alternatives-when-you-need-bug-capture): Canny excels at public roadmaps. If your inbox is mostly production bugs, a capture-first widget is the better starting point.
- [Feedback Widget Reddit: Better Than Threads](https://feedblox.net/blog/feedback-widget-reddit): Founders on r/SaaS and r/SideProject keep asking Reddit to review their tools. A feedback widget on your live site gets sharper signal from people who actually use the product.
- [Userback Alternative for Website Feedback](https://feedblox.net/blog/userback-alternative-for-website-feedback): Userback and FeedBlox both collect visual website feedback. This guide compares install weight, dev context, sentiment modes, and honest tradeoffs.
- [Session Replay Alternatives for Bug Reports](https://feedblox.net/blog/session-replay-alternatives-for-user-feedback): Session replay tools investigate behavior at scale. Feedback widgets capture structured reports with dev context. Most teams need one first, not both on day one.
- [Lite Feedback Alternative With Bug Context](https://feedblox.net/blog/lite-feedback-alternative): Lite Feedback optimizes for reviews and social proof. FeedBlox optimizes for bug capture with client debug. Here is how to choose without overbuying.
- [Best Feedback Widget Tools Compared (2026)](https://feedblox.net/blog/best-feedback-widget-tools-compared-2026): Feedback widget tools solve different jobs. This comparison sorts capture, roadmap, replay, and survey products so you pick the right inbox workflow.
- [Read the Element Trail and Repro Summary](https://feedblox.net/blog/how-to-read-element-trail-repro-summary): Element trails look cryptic at first. This guide explains Repro Summary, timing offsets, fingerprint suffixes, and how to turn a trail into a repro path without DOM text.
- [Turn Negative Feedback Into Product Fixes](https://feedblox.net/blog/how-to-turn-negative-feedback-into-product-fixes): Negative feedback is only useful if it becomes a tracked fix. Workflow from inbox to engineering to follow-up without a public shame board.
- [Prioritize User Feedback Without a Roadmap](https://feedblox.net/blog/how-to-prioritize-user-feedback-without-a-public-roadmap): You do not need a public roadmap to prioritize feedback. Use inbox status, tags, and severity rules - then publish only what you are ready to commit.
- [Add a Feedback Widget to WordPress](https://feedblox.net/blog/how-to-add-a-feedback-widget-to-wordpress): 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.
- [Add a Feedback Widget to Webflow](https://feedblox.net/blog/how-to-add-a-feedback-widget-to-webflow): Install a feedback launcher on every Webflow page with one footer code block. Test on published URLs, not the Designer preview.
- [Add a Feedback Widget to a Next.js App](https://feedblox.net/blog/how-to-add-a-feedback-widget-to-a-nextjs-app): Add a site-wide feedback launcher to Next.js with one embed. Works with App Router and Pages Router without a client-side SDK.
- [Best Free Feedback Widgets (2026)](https://feedblox.net/blog/best-free-feedback-widgets-for-websites): Free tiers vary wildly. This checklist compares what actually matters for live-site feedback and bug reports before you pick a widget.
- [Collect Bug Reports From Website Visitors](https://feedblox.net/blog/how-to-collect-bug-reports-from-website-visitors): Visitors will not open DevTools. Here is a practical setup for collecting bug reports from live pages with enough context to reproduce.
- [Capture Console Logs From Bug Reports](https://feedblox.net/blog/how-to-capture-console-logs-from-user-bug-reports): Production bugs rarely arrive with useful console output. Here is how to capture log, warn, and error lines at submit time so every user bug report includes developer context.
- [Pricing](https://feedblox.net/pricing): Free for Solo Founders (3 sites, 150 reports/month), Pro for Shipping Teams, Max for Heavy Capture. Annual billing available (2 months free; contact for invoice until Polar annual SKUs ship).
- [Press kit](https://feedblox.net/press): Logos and boilerplate.
- [Changelog](https://feedblox.net/changelog): Dated product updates.

## Compare

- [Compare overview](https://feedblox.net/compare): How FeedBlox fits vs tools teams evaluate.
- [FeedBlox vs Marker.io](https://feedblox.net/compare/marker-io): Looking for a Marker.io alternative? FeedBlox is a free feedback widget with bug reports and developer context on every plan. Marker.io excels at visual QA handoff when that is the main loop.
- [FeedBlox vs Canny](https://feedblox.net/compare/canny): Looking for a Canny alternative? FeedBlox embeds a feedback widget on your live site with developer context on every report. Canny excels at public roadmaps and voting when that is the main loop.
- [FeedBlox vs UserJot](https://feedblox.net/compare/userjot): Looking for a UserJot alternative? FeedBlox captures feedback and bugs on your live product with console logs on every plan. UserJot packages boards, roadmap, and changelog in one public loop.
- [FeedBlox vs BugHerd](https://feedblox.net/compare/bugherd): Looking for a BugHerd alternative? FeedBlox is a website feedback widget with NPS, bug reports, and console logs on every plan. BugHerd excels at pin-based agency review when that workflow is fixed.
- [FeedBlox vs Hotjar](https://feedblox.net/compare/hotjar): Looking for a Hotjar alternative? FeedBlox is a lightweight feedback widget with bug reports and console logs - not heatmaps or session replay. Hotjar excels at behavioral analytics when that is the main job.
- [FeedBlox vs Userflow](https://feedblox.net/compare/userflow): Looking for a Userflow alternative for feedback? FeedBlox captures bugs and sentiment after onboarding with console logs on every report. Userflow excels at in-app guides and activation flows.
- [FeedBlox vs Pendo](https://feedblox.net/compare/pendo): Looking for a Pendo alternative? FeedBlox is a free feedback widget with bug reports and console logs without enterprise MAU contracts. Pendo excels at company-wide product adoption and analytics.
- [FeedBlox vs Usersnap](https://feedblox.net/compare/usersnap): Looking for a Usersnap alternative? FeedBlox collects live feedback and bugs with console logs on every plan. Usersnap excels at visual feedback and QA-style capture when that is your main loop.
- [FeedBlox vs Featurebase](https://feedblox.net/compare/featurebase): Looking for a Featurebase alternative? FeedBlox embeds on your live product with developer context on every report. Featurebase excels at public feedback hubs and roadmaps when that is the main loop.
- [FeedBlox vs Frill](https://feedblox.net/compare/frill): Looking for a Frill alternative? FeedBlox captures feedback and bugs on your site with console logs on every plan. Frill focuses on ideas boards and roadmaps for customer-facing loops.
- [FeedBlox vs Sleekplan](https://feedblox.net/compare/sleekplan): Looking for a Sleekplan alternative? FeedBlox collects live feedback and bugs with console logs on every plan. Sleekplan excels at feedback boards, roadmaps, and changelogs.
- [FeedBlox vs Upvoty](https://feedblox.net/compare/upvoty): Looking for an Upvoty alternative? FeedBlox embeds on your product for feedback and bugs with console logs on every plan. Upvoty packages boards, roadmaps, and changelogs.
- [FeedBlox vs Typeform](https://feedblox.net/compare/typeform): Looking for a Typeform alternative for website feedback? FeedBlox is an always-on launcher for ratings, comments, and bug reports with console logs. Typeform excels at polished surveys and research flows.
- [FeedBlox vs Tally](https://feedblox.net/compare/tally): Looking for a Tally alternative for website feedback? FeedBlox is a feedback widget with bug reports and console logs - not a general form builder. Tally excels at fast form creation.
- [FeedBlox vs Sentry](https://feedblox.net/compare/sentry): Sentry vs FeedBlox? Sentry monitors errors in your codebase. FeedBlox collects user-initiated feedback and bug reports with console logs. They are complementary, not interchangeable.
- [FeedBlox vs LogRocket](https://feedblox.net/compare/logrocket): LogRocket vs FeedBlox? LogRocket records sessions and monitors frontend issues. FeedBlox collects user-initiated feedback and bug reports with console logs without a full replay suite.
- [FeedBlox vs FullStory](https://feedblox.net/compare/fullstory): FullStory vs FeedBlox? FullStory is enterprise digital experience analytics with replay and funnels. FeedBlox is lightweight feedback and bug capture with console logs when users report.
- [FeedBlox vs Microsoft Clarity](https://feedblox.net/compare/microsoft-clarity): Microsoft Clarity vs FeedBlox? Clarity offers free heatmaps and recordings. FeedBlox collects user-initiated feedback and bug reports with console logs - a different job from behavioral analytics.

## Legal and Trust

- [About](https://feedblox.net/about)
- [Customers](https://feedblox.net/customers)
- [Privacy Policy](https://feedblox.net/privacy)
- [Terms of Service](https://feedblox.net/terms)
- [Widget Data and GDPR](https://feedblox.net/docs/widget-data): What the embed captures; site-owner duties.
- [Security](https://feedblox.net/security)
- [Legal overview](https://feedblox.net/legal)
- [Press kit](https://feedblox.net/press)

## Optional

- [Sitemap](https://feedblox.net/sitemap.xml)
- [Robots](https://feedblox.net/robots.txt)

Dashboard, authentication, and customer sites are not indexed. This file describes the public marketing site only.