Bolt · AI tool

Get feedback on sites built with Bolt

Publish your Bolt project, paste the link, and get comments pinned to the running site from people who do not have a Bolt account. Then hand the whole list back to Bolt in one paste.

Free for 3 projects. Reviewers never need an account. Or upload an HTML file.

Why Bolt users use HTMLAnnotate

Bolt makes it easy to go from an idea to a published site at a bolt.host address in an afternoon. Getting useful feedback on it is harder. Clients and teammates open the link, then reply with screenshots, scattered chat messages or a call where half the notes are lost. You end up translating vague comments like the button at the top looks off into prompts, guessing at which page and which screen size they were on.

Bolt has comments of its own, pinned to elements in the project preview, and editors can send them straight to Bolt. They work well for your team. But collaborators must have a Bolt account and accept an invite, even Viewers can see your code, and comments appear only in the project preview, not on the published site. That is a lot to ask of a client who just wants to say the headline is too long.

HTMLAnnotate puts the comments on the published site instead. Reviewers open one link, give a name and email, browse the real site, then switch to Comment mode and click what they mean. Every note records the page, the view, and their browser, OS and screen size. When the round is done, Copy for AI turns all open comments into a brief with CSS selectors that you paste into Bolt's chat.

How it works with Bolt

Three steps, about a minute.

Publish from Bolt

Click Publish in the top right and publish to your free bolt.host address, your custom domain, or Netlify if you connected it. Keep the site set to Public for the review.

Paste the link

Copy the published address and paste it into HTMLAnnotate. It loads the live site, scripts and all, and gives you a review link to share.

Send the brief back to Bolt

Once comments are in, press Copy for AI and paste the brief into Bolt's chat. Each change comes with its element, CSS selector, view and page path.

A full review round, start to finish

What a typical round looks like on Bolt.

Publish the latest version
Bolt does not push changes live automatically. Open the Publish menu and click Update so your bolt.host address matches what you see in the editor. If you want a friendlier address, use the pencil icon next to the domain to rename it, and tick Republish after updating.
Keep the site public for the round
Paid plans can set a site to Private, which limits it to your team and people you invite by email. Reviewers coming through HTMLAnnotate cannot sign in, so switch visibility back to Public in the Publish menu while the review is running.
Create the review link
Paste the published address into HTMLAnnotate. The site runs live with its own scripts, so menus, sliders and animations behave as they do for visitors. Reviewers can move between pages, and each page keeps its own comments. Forms on the reviewed copy cannot be submitted.
Collect comments from anyone
Send the link to clients or testers. No Bolt account, no invite to accept, no access to your code. They browse in Browse mode, switch to Comment mode, and click an element to leave a note. Ask them to tag each note Bug, Copy, Design, Question or Idea.
Triage in one list
Reply in threads, set priority from low to urgent, and resolve what is agreed. For wording changes, reviewers can type suggested text that previews live on the page. Press Accept on the ones you want, and they stay open as a to-do until Bolt has made the change.
Send fixes to Bolt and sign off
Press Copy for AI, paste the brief into Bolt's chat, and ask it to work through the list in one go. Then click Update in the Publish menu, send the same review link again, and ask the client to press Approve. Export a CSV if you need a record of the round.

Bolt's own tools and HTMLAnnotate

Use both. Here is what each is good at.

What you need	Bolt	HTMLAnnotate
Comments pinned to elements	Yes, in the project preview	Yes, on the published site
Reviewers without a Bolt account	No, collaborators must sign in to Bolt	Yes, name and email once
Keep your code private from reviewers	Viewers can see the preview and code	Reviewers only see the site
Send feedback to the AI	Editors send comments to Bolt directly, using tokens	Copy for AI brief for Bolt or any tool
Restrict who sees the site	Private sites with email invites, paid plans	Comments on/off switch per link
Triage and sign-off	Threads, mentions, resolve	Labels, priority, suggested text, Approve button, CSV export

What works

Comments on the published bolt.host or Netlify site, not only the editor preview
Clients review without a Bolt account or access to your code
CSS selectors and page paths in every brief you paste into Bolt
Separate Desktop, Tablet and Mobile comments
Labels and priority so you prompt the urgent fixes first
Free to start: 3 active projects with unlimited reviewers

Good to know

Bolt's Private sites limit viewers to invited emails, so reviewers cannot open them through HTMLAnnotate. Set the site to Public for the round.
Share the published link, not the project code. A multi-file Bolt project cannot be uploaded as files.
Bolt's own comments can be sent to Bolt with one click. With HTMLAnnotate you paste the Copy for AI brief into the chat yourself.
Pages behind your app's own sign-in screen cannot be reached by reviewers yet.

Tips for better Bolt reviews

Click Update, not a prompt

Bolt's docs recommend the Publish and Update buttons over asking Bolt to publish, because prompting uses tokens. Click Update before you send the review link so reviewers see your latest version.

Rename the bolt.host address

The first publish gets a random bolt.host name. Use the pencil icon in the Publish menu to give it a clear name before the round, so the link your client sees looks intentional.

Send one brief, not ten prompts

Bolt's own docs note that sending several comments together usually uses fewer tokens than one at a time. The same holds for HTMLAnnotate: paste a single Copy for AI brief after the round closes.

Fill in sample content

Reviewers cannot submit forms on the reviewed copy, so empty lists stay empty. Add realistic sample data to your Bolt project before publishing, so there is something real to comment on.

Questions about Bolt

Do reviewers need a Bolt account?

No. With HTMLAnnotate they open the review link and enter a name and email the first time. Bolt's own comments need collaborators to have a Bolt account and accept a project invite.

Does it work with bolt.host and Netlify?

Yes. Paste whichever public address your Bolt project is published to: a bolt.host address, a netlify.app address, or your own custom domain. Visitors must not need to sign in to see it.

Can reviewers see my code?

No. Reviewers only see the running site. In Bolt's own sharing, even the Viewer role can open the preview and the code, which may not suit a client review.

Can I review a Private Bolt site?

Not yet. Private sites ask visitors to sign in with an invited email, and HTMLAnnotate cannot import pages behind a sign-in form. Switch the site to Public in the Publish menu for the review.

How do I get the comments into Bolt?

Press Copy for AI. It copies every open comment as one brief with the element, CSS selector, view, page path, suggested text and replies. Paste it into Bolt's chat and ask it to make the changes.

Can I turn comments off after the round?

Yes. Each review link has a comments on/off switch, so you can close a round without deleting the link or the comments already left. Turn it back on for the next round.

Other AI tools

HTMLAnnotate works with any page anyone can open in a browser.

Claude ChatGPT Gemini v0 Lovable Cursor Replit +See all