A user reports the problem
They click the launcher on your live app and describe what went wrong. No account needed.
Feedback Widget for Lovable Apps
Find out what broke in your Lovable app from the user who hit it, with the console errors and failed requests attached, then hand that context to Lovable to fix.
Console logs and network errors on every report, including the free plan. Start with 30 days of Pro free, no credit card. Then Free forever: 3 sites, 150 reports/month.
For people shipping with Lovable
Founders, designers and developers who build with Lovable and put the result in front of real users, often before there is a test suite or a QA step.
Fast builds break in ways you cannot see
Generated code ships quickly, and the first person to hit a broken form or a failed request is usually a user. They tell you "it does not work", and you have nothing to paste back into Lovable except their words.
Reports that carry what the browser logged
FeedBlox adds a feedback launcher to your Lovable app. When a user reports a problem, the report includes the console errors, failed network requests and JavaScript errors from their session, which is exactly the context to give Lovable when you ask it to fix the bug.
What each report brings
One script tag, added by Lovable or by you. Debug context is on every plan, including Free.
-
Console errors
Recent log, warn and error lines from the session where the user hit the problem.
-
Failed requests
Network calls that failed, with status codes, so you can tell a backend error from a UI bug.
-
JavaScript errors
Uncaught errors and rejected promises, with the message you can paste straight into a fix prompt.
-
Ratings and comments
Users can also say what they like, so you hear about more than bugs.
From user report to Lovable fix
The report is written for the next prompt you send.
You read the context
The inbox shows the console error, the failed request and the page it happened on.
You ask Lovable to fix it
Paste the error and the failing request into your next prompt instead of guessing.
Paste This Into Lovable
Replace the placeholders with the values from your FeedBlox Widget page.
Prompt
Add FeedBlox to this app. Edit index.html directly, not a React component:
1. Inside <head>, add exactly:
<meta name="feedblox-site-verification" content="YOUR_VERIFICATION_TOKEN" />
2. Just before </body>, add exactly:
<script src="https://app.feedblox.net/widget.js" async
data-site-id="YOUR_SITE_ID"
data-token="YOUR_EMBED_TOKEN"
data-api-url="https://api.feedblox.net"
data-position="middle-right"
></script>
Do not change any other file.Yes. Lovable apps are React and Vite projects, so both tags go in index.html. Verify against your published lovable.app address or custom domain.
Install in Minutes
One async script tag before the closing body tag. See the full install guide or the free widget page for Webflow, WordPress, Shopify, and Next.js steps.
Embed Snippet
<script src="https://app.feedblox.net/widget.js" async
data-site-id="YOUR_SITE_ID"
data-token="YOUR_EMBED_TOKEN"
data-api-url="https://api.feedblox.net"
data-position="middle-right"
></script>Lovable Feedback Widget FAQ
Does it work with Lovable apps?
Yes. Lovable apps are React and Vite projects, so both tags go in index.html. Verify against your published lovable.app address or custom domain.
Are console logs included on the free plan?
Yes. Console errors, failed requests and JavaScript errors come with reports on Free, which covers 3 sites and 150 reports a month. New accounts also get 30 days of Pro without a card.
Why does verification need the meta tag in the HTML?
FeedBlox checks your live URL from its server and reads the raw HTML. A tag added later by JavaScript is not there yet, so it has to be in the page source.
Will the widget show in the Lovable editor preview?
The preview runs on a different address. Add it under Additional Embed Origins in FeedBlox site settings if you want the widget there too.