Sometimes a generated site is almost right, with one thing that isn't: a button that goes nowhere, a carousel whose arrows do nothing, an empty box that shouldn't be there. Regenerating would fix it, but it would also replace the design you liked. Repair is the narrower tool — describe the single problem, and the AI fixes just that and republishes your site.
How to describe the problem
Repair works far better with a specific description than a vague one. Name the exact element and which section it's in. Good examples:
- “The testimonial carousel arrows don't do anything when clicked.”
- “The ‘Contact us' button in the hero doesn't link anywhere.”
- “Remove the empty statistics box under the About section.”
- “The mobile menu won't close after I tap a link.”
Compare those with “the site is broken”, which gives the AI nothing to aim at. The more precisely you point, the better the fix.
What happens when you run it
- The AI analyses your site and applies a fix for the problem you described.
- Your site is rebuilt and republished automatically.
- You get a confirmation once the repaired site is live.
This usually takes a couple of minutes. If it's taking longer than expected, check Site History → Releases shortly afterwards to confirm what happened — see release history and restoring a previous version.
If the repair doesn't build
Repair is safe by design. If the repaired version fails to build, your previous version stays live — visitors never see a broken site. You'll be told that it failed, so you can rephrase the request and try again.
Repair, regenerate, or edit?
- Repair when the design is right and one specific thing is wrong.
- Regenerate when you want a different look altogether, or your source content has changed substantially. See regenerating your website.
- Edit when it's the wording or an image that needs changing rather than the behaviour. See editing your website content.
One problem at a time
Describe a single issue per repair. A list of five unrelated problems in one request gives a much less reliable result than five focused requests — and if something goes wrong, you'll know exactly which change caused it.
If two or three attempts don't land the fix, open a ticket from support and describe what you're seeing. That's a better use of your time than a fourth attempt.