A user reports the problem
They click the launcher on your live app and describe what went wrong. No account needed.
Feedback Widget for v0 Apps
Your v0 app is a Next.js app, so FeedBlox goes in the root layout. Users report problems, and each report carries the console errors and failed requests from their session.
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 v0
Founders, designers and developers who build with v0 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 v0 except their words.
Reports that carry what the browser logged
FeedBlox adds a feedback launcher to your v0 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 v0 when you ask it to fix the bug.
What each report brings
One script tag, added by v0 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 v0 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 v0 to fix it
Paste the error and the failing request into your next prompt instead of guessing.
Paste This Into v0
Replace the placeholders with the values from your FeedBlox Widget page.
Prompt
Add FeedBlox to this Next.js app in app/layout.tsx:
1. Add "feedblox-site-verification": "YOUR_VERIFICATION_TOKEN" to metadata.other, keeping the existing metadata.
2. Inside <body>, after {children}, render next/script with src="https://app.feedblox.net/widget.js", strategy="afterInteractive", data-site-id="YOUR_SITE_ID", data-token="YOUR_EMBED_TOKEN", data-api-url="https://api.feedblox.net" and data-position="middle-right".
Do not change any other file.Yes. v0 generates Next.js apps, so the meta tag goes in metadata and the widget in next/script in app/layout.tsx. Verify against your production address.
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>v0 Feedback Widget FAQ
Does it work with v0 apps?
Yes. v0 generates Next.js apps, so the meta tag goes in metadata and the widget in next/script in app/layout.tsx. Verify against your production address.
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.
Does it work on Vercel preview deployments?
Previews use their own addresses. Add the ones you test on under Additional Embed Origins in FeedBlox site settings.