Bottom line: If the toolbar does not appear on staging, do not start the client round. Fix the embed first — it is cheaper than explaining a blank page on a call.
By Vetagiri Hrushikesh · Last updated: August 2026
Client review goes badly when staging is not actually reviewable: wrong Review ID, CSP blocking the embed, or a URL nobody bookmarked. Run this checklist before you send the link.
The problem
Teams paste a snippet, skip the browser check, and find out Friday that comments never saved. Or they send production instead of staging. Or two people created two reviews and the client is pinning into the empty one.
Why Tweak fits engineering and QA leads
One Review ID ties embed, hub, and MCP. Confirm it before anyone else is invited.
CSP mistakes are the #1 “toolbar missing” cause — 60 seconds in DevTools.
Clients should never need the Chrome extension. If they do, the embed is not on the page they opened.
Auth walls are expected; surprise 404s are not. Open the URL in a private window as the client would.
A written checklist survives handoff when the person who set up staging is out.
How it works
1. Confirm the URL. Open the exact staging URL you will send. Check HTTPS, environment, and that it is not a leftover preview deployment.
2. Confirm the snippet. View source: embed.js is present once, with the Review ID you created. Duplicate snippets create confusing double toolbars.
3. Confirm the toolbar. Load staging logged out if clients will be logged out. You should see the client toolbar. If not, open Network + Console and follow /docs/csp-troubleshooting.
4. Leave a test pin. File one throwaway comment, refresh, and confirm it is still there. Then resolve it so the client does not treat it as real feedback.
5. Send one artifact. Email or Slack the staging URL (and password if needed). Point to /docs/for-clients-and-qa if they want a one-pager. Do not attach a screenshot of the checklist.
Frequently asked questions
The snippet is there but the toolbar is missing. What next?
Almost always CSP or a wrong Review ID. See /docs/csp-troubleshooting. Confirm embed.js returns 200 and that script-src allows https://tweak.page.
Should QA use the extension or the embed?
Guests and clients use the embed on staging. Your engineering team uses the Chrome extension on the same Review ID so they can inspect, assign, and resolve.
Can we review production?
Yes if the embed is installed there, but most teams keep review on staging so pins do not land on live customers. The product works on any page the browser can load.
Where do developers see the issues?
Hosted hub at tweak.page, the Chrome extension on the staging tab, and optionally MCP in Cursor or Claude. Same issue list.
Tweak is a commercial website review platform with Free and Pro plans. Developers sign in with GitHub; clients open share links without installing anything.