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

# Launch checklist

> Review your site, choose its URL, publish production, and keep a recovery path.

Use this checklist after your hosted Preview is ready. Publishing is a separate step that makes `main` public.

## 1. Check readiness in Preview

* Deploy the final Branch with `fimo deploy`.
* Open the Preview link as a signed-in project member.
* Check key pages, forms, links, mobile layouts, page titles, and descriptions.
* Run `fimo status` and merge the reviewed Branch into `main`.

## 2. Choose the public URL

Every project has a `*.fimo.site` URL. You can rename its slug before launch:

```bash theme={null}
fimo domains list
fimo domains rename-default <slug>
```

If your plan includes custom domains, attach a hostname you already own and add every DNS record that Fimo returns. Domain purchase through Fimo appears only when it is available for your organization. See [Custom domains](/docs/deploy/custom-domains).

<Note>The default URL and attached custom domains start serving the site after the first successful publish.</Note>

## 3. Publish production

Choose one procedure:

* In the CLI, check out `main` and run `fimo deploy --publish`.
* In Studio, open the Publish panel and select **Publish**.

Both procedures publish the project. Use the one that matches where you are working.

## 4. Verify the live site

* Open the production URL shown after publishing.
* Repeat the key page, form, link, mobile, and metadata checks on the live site.
* Confirm attached domains have reached their active state before sharing them.
* Use [Analytics](/docs/deploy/analytics) to review production traffic after launch.

## 5. Keep a recovery path

Create a named restore point before a risky launch if you need an easy reference:

```bash theme={null}
fimo history create "Before launch"
```

If you need to recover, restore the chosen version, review it in Preview, then publish it. Restoring alone does not update the public site.

## What's next

<Columns cols={3}>
  <Card title="Deploy & publish" icon="cloud-arrow-up" href="/docs/deploy/overview">
    Publish from the CLI.
  </Card>

  <Card title="Publish in Studio" icon="window-maximize" href="/docs/studio/publish">
    Publish from the dashboard.
  </Card>

  <Card title="Version history" icon="clock-rotate-left" href="/docs/environments/version-history">
    Restore code and content together.
  </Card>
</Columns>