Publish the website
Use Bolt hosting to create the bolt.host site, or attach a custom domain on a paid plan. Confirm the release has the visibility intended for the review.
Paste the public bolt.host URL or custom domain, send one review link, and collect contextual comments on the website your visitors will actually open.












Loved by1,250+Agenciesand companies in 100+ countries
Bolt provides project collaboration and built-in hosting. The right review URL depends on whether stakeholders need the project workspace or the deployed website.
Four documented boundaries matter before you share a review:
Bolt publishes every Free-plan site as public. Paid plans can publish a site publicly or privately for the team and invited viewers.
After publishing, project changes aren't automatically applied to the live site. The owner or a Co-owner uses Publish for the first release and Update for later changes.
Bolt project collaboration uses Viewer, Editor and Co-owner roles. Collaborators must have a Bolt account and sign in; this link opens the project, preview and code rather than only the visitor-facing site.
Bolt says a site with a custom domain can only be published publicly. The domain must be disconnected before that site can be published privately.
How it works
Use Bolt hosting to create the bolt.host site, or attach a custom domain on a paid plan. Confirm the release has the visibility intended for the review.
Paste the public visitor-facing URL into BugSmash and share the resulting review link instead of granting access to the Bolt project.
Resolve the comments in Bolt, use Update to publish the changes, and review the same live URL again before approval.
Attach feedback to the rendered bolt.host site or custom domain visitors will use.
External reviewers do not need Viewer, Editor or Co-owner access when the published site is public.
Review desktop, tablet and mobile presentation from the same browser-accessible release.
Keep the page URL, browser, operating system, viewport and screenshot with each website comment.
Bolt leaves live content unchanged until an owner or Co-owner publishes or updates the site, so each round can target an intentional release.
Install the BugSmash Feedback Widget when feedback must be collected inside an authorized or stateful app experience.
Use the deployed visitor-facing site whenever possible. Project sharing controls access to the Bolt workspace, while publishing controls access to the website.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public site on a bolt.host address | Works | Paste the published URL and start the review. |
| Public site on a custom domain | Works | Paste the connected domain after the latest release is published. |
| Private Bolt-hosted site | Access-dependent | Only team members and invited viewers can open it. Verify the reviewer can complete Bolt access inside the review, or use a public review release or the widget. |
| Bolt project-share link | Use the published site | The project link exposes collaboration access, preview and code according to the assigned role. Use the visitor-facing deployment for website review. |
| Unpublished project preview | Not a public release | Publish an appropriate site before collecting external browser feedback. |
| App behind application login or SSO | Use the widget | A pasted URL does not bypass application login or SSO. Install the Feedback Widget inside the authorized app experience. |
Add the BugSmash script to the deployed app when reviewers must comment inside a logged-in, role-specific or stateful flow. Bolt project roles and private-site invitations remain separate from the frontend feedback workflow.
Keep building, project collaboration and release approval distinct while every comment stays attached to the published app.

Collect structured browser feedback on the release without inviting every tester into the project workspace.
See how
Share the client-facing site, preserve Bolt editing permissions, and keep approval tied to the deployed release.
See how
Review responsive screens and real flows, then send reproducible items to the tools used to complete the work.
See howRoute an actionable website comment to the delivery team with its page, selected location, screenshot, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the published app beside product PDFs, videos, images, presentations and other launch assets, with feedback and approval in one project.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Send the public bolt.host address or connected custom domain that opens the visitor-facing release. A Bolt project-share link opens a collaboration surface with role-based access.
Paste the public Bolt site URL and send a focused review link without opening the project workspace to every reviewer.
