> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skarmy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update a published site

> Ship changes to a site that is already live, and understand why your public address does not update on its own.

Your published site is a snapshot. It stays exactly as it was until you publish again — even as you keep building.

## Before you start

A workspace you have already published once, and at least one change you want to ship.

## Publish an update

<Steps>
  <Step title="Make your change">
    Ask the Builder for it in the conversation and wait for the preview to show it.

    **Expected result:** the change is visible in the preview pane and the Builder has reported the milestone done.
  </Step>

  <Step title="Publish again">
    Select **Publish**. There is no naming dialog this time — your address is already claimed — but the **Review before publishing** dialog still shows you the version going out. Select **Approve and publish**.

    **Expected result:** the button reads **Deploying…**.
  </Step>

  <Step title="Wait, then check">
    Deployment takes a few minutes. When it finishes, open your **Live at …** link.

    **Expected result:** your public site now shows the change.
  </Step>
</Steps>

<Tip>
  Hard-refresh the tab, or open the site in a private window, if your browser is showing you a cached copy.
</Tip>

## Why it works this way

Two useful consequences:

* **You can build in the open without breaking what people see.** Experiment freely; the live site is unaffected until you decide.
* **Publishing is a decision.** Nothing reaches your audience by accident.

Publishing always ships **your last completed milestone**. If the Builder is mid-change when you publish, the last finished state goes out — not the half-finished one.

## If a publish fails

A failed publish leaves your existing live site untouched. Visitors keep seeing the last good version.

Your claimed address is also safe — a failed publish never releases the name.

Select **Publish** to try again. If it keeps failing, ask the Builder what went wrong; it reports failures honestly rather than claiming success.

## Verify

* Your **Live at …** link shows the change in a private window.
* The change is the one you asked for and nothing else obviously moved.

## Troubleshooting

| Problem                                        | Fix                                                                                      |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------- |
| The live site still shows the old version      | Hard-refresh, or open it in a private window.                                            |
| `Nothing to publish yet. Finish a build first` | The current change has not finished. Wait for the Builder's summary.                     |
| `Publish failed. Try again`                    | Select **Publish** again. Your live site and address are unaffected.                     |
| You published something you did not mean to    | Ask the Builder to change it back, then publish again.                                   |
| Out of credits                                 | Each publish costs a small fee. See [Billing and top-ups](/credits/billing-and-top-ups). |

## Next

<Columns cols={2}>
  <Card title="Work with the Builder" icon="hammer" href="/build/work-with-the-builder">
    Make the next change.
  </Card>

  <Card title="How credits work" icon="coins" href="/credits/how-credits-work">
    What publishing costs.
  </Card>
</Columns>