Troubleshooting

You made a change but it is not on the live site. Check in order:

1. 1Did you publish? Changes do not reach the site on their own. Blog posts, products, plugins and design edits all need a Publish.
2. 2Did publishing actually finish, did you see it complete successfully on screen?
3. 3Hard refresh the page: Ctrl + F5 on Windows, Cmd + Shift + R on Mac.
4. 4Open it in a private window. If it looks right there, it is your browser's stored copy.

For details, see Publishing and updating.

A failed publish does not break your live site; it stays exactly as it was.

1. 1Copy the error message.
2. 2Go back to the chat, say "I got this error while publishing" and paste it.
3. 3Publish again once the AI has fixed it.
4. 4If the same error repeats three times, undo the last big change, publish, then reintroduce it in smaller steps.

• Split the request. If you asked for several changes at once, ask for them one at a time.
• Say where. Point at a place: "the heading at the top", "the button in the contact section".
• Send a screenshot. Upload an image of the problem area and describe what you want.
• Switch models. If three attempts failed, move to a stronger model.
• It may not be possible. Payments, carts and admin panels are not written by chat; those use plugins.

• After adding the record, propagation usually takes 15 minutes to an hour, and up to 24 hours with some providers.
• Delete any old A or CNAME records still sitting in your provider's panel.
• Make sure the records for both the root address and www were added.
• If you never published the project, the domain will not open anything even when connected.

For details, see Connecting a domain.

You wrote and saved the post but it is not live. That is expected: posts do not reach the site until you publish.

1. 1Make sure the post is marked as published, not draft.
2. 2Publish the project.
3. 3Check your site in a private window a few minutes later.

• Your live site is unaffected and stays online.
• The weekly limit resets at the start of the next week.
• If you do not want to wait, upgrading applies immediately.
• You can track usage from the usage screen in Settings.

For details, see Plans and usage.

• If the code did not arrive, wait a few minutes and check your spam folder.
• The code may have expired; request a new one.
• If you signed up with Google or GitHub, sign in the same way.
• Check the address you typed; a different address creates a new account rather than opening yours.

When you write to support, include these for a much faster answer: your project name, the step you got stuck on, the error message on screen and a screenshot.