# Go live

Going live means visitors get the static copy instead of WordPress®. You'll do it in this order, so the site never goes down:

1. **Publish** the latest build in WranglePress. Nothing changes yet: your domain still points at your host.
2. **Point your domain** at WranglePress. As DNS updates, visitors start getting the copy.
3. **Keep WordPress private, or retire it** afterwards: see [Make WordPress private](https://wranglepress.com/docs/private-wordpress) or [Retire WordPress](https://wranglepress.com/docs/retire-wordpress).

## Before you start

- Your domain is [verified](https://wranglepress.com/docs/connect-domain), and the build that started after verifying has finished.
- You've checked that build on the [preview](https://wranglepress.com/docs/builds-and-preview).
- **Lower your DNS record's TTL** (time to live) to 5 minutes a day ahead, if your DNS provider allows it. Then a change, or a change back, spreads quickly.

## 1. Publish

In card **3. Go live**, click **Publish build …**. The site's status becomes **live**. The copy is ready for your domain.

## 2. Point your domain at WranglePress

Change the domain's website record to:

| Type | Name | Target |
|---|---|---|
| `CNAME` | `www` (or your subdomain) | `edge.wranglepress.io` |

- **Replace** the existing record for that name (usually an `A` record with your host's IP address, or a `CNAME` to your host). Delete the old one; a name can't have both.
- **Leave everything else alone,** especially `MX` records (your email) and other `TXT` records.
- **On Cloudflare DNS,** set the record to **DNS only** (grey cloud).

**A bare domain** like `example.com` (no `www`) can't normally have a CNAME. Use your DNS provider's *CNAME flattening* (Cloudflare does this automatically), *ALIAS* or *ANAME* record instead. If your provider has none of these, use `www.example.com` as the main address and redirect the bare domain to it at your registrar.

## 3. Check it

Within a few minutes (sometimes longer), the site page shows the certificate status as **active**. Then open your domain in a private browser window:

- Pages load and look right.
- A test form arrives.
- Your browser shows a valid padlock.

## If something's wrong

- **Roll back to an earlier build:** click **Roll back to this** next to it in the Builds list. It's immediate.
- **Go back to WordPress completely:** change the DNS record back to what it was, then click **Take offline**.

## After going live

Every time you publish in WordPress, the copy rebuilds and goes live automatically, as long as the site is live. Now decide what happens to WordPress: [make it private](https://wranglepress.com/docs/private-wordpress) if you'll keep editing, so strangers can't skip the copy and reach WordPress directly, or [retire it](https://wranglepress.com/docs/retire-wordpress) if the site rarely changes.

---

Canonical page: https://wranglepress.com/docs/go-live · Last updated 2026-10-24