# How To Go Live From Staging Domain?

> We can easily go live from staging site with a single click with the help of xCloud.

Testing changes before making them live is crucial for your website’s stability. It avoids errors and saves time and effort in resolving issues that may arise otherwise.

<iframe loading="lazy" title="How to Go Live from Staging Websites on xCloud?" width="500" height="281" src="https://www.youtube.com/embed/_4lHCav-5Xk?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen=""></iframe>

First, click on the **Staging** option. Here you will get a brief overview of your entire **Staging Management** system.

From the **[xCloud](/)** dashboard, you can easily go live from staging domain with a single click. 

![Go Live From Staging](/_landing/docs/how-to-go-live-from-staging-domain-staging-to-live-domain.png)

Now, simply click on the **Go Live** option. After clicking, you need to add your necessary information like **Domain Name, Additional Domain.** You can also, enable HTTPS for more security. 

## What Go Live already does for you

For WordPress sites, Go Live already runs a database search-and-replace to swap the staging domain for the live one — you don't need to do this yourself in the normal case. The Go Live dialog lets you choose the **Search & Replace Mode** and **Table Mode**; the defaults cover the standard WordPress tables.

## Why old URLs can remain after Go Live

If images or links still point at the old staging domain afterward, it's usually one of these:

- The domain was changed a different way (for example, only at DNS) instead of through the Go Live wizard's search-and-replace.
- Some URLs aren't plain database values — they're hard-coded in theme or plugin code, or stored in page-builder data that the standard search-and-replace doesn't reach.
- The page cache or a CDN cache is still serving the old, pre-Go-Live version of a page.

## Fixing leftover old-domain URLs

1. **Purge caches first.** Clear the site's page cache and any CDN cache (Cloudflare or similar) — a stale cache is the simplest explanation and the quickest to rule out.
2. **Run WP-CLI search-replace if URLs are still wrong.** Take a backup first, then run:
   ```
   wp search-replace 'old-domain.com' 'new-domain.com' --all-tables --precise
   ```
   Use WP-CLI rather than raw SQL — it safely handles WordPress's serialized PHP data, which a plain SQL replace can corrupt. Check links and media on the site afterward.
3. **Check `home` and `siteurl`.** If either still points at the old domain, that's very likely the direct cause and worth confirming before you look further.

## Multisite

Multisite networks need extra care beyond the single-site steps above — the network's domain configuration and any per-site URL caching can each hold onto the old domain independently. If old URLs persist on a multisite install after the steps above, [contact support](/docs/access-built-in-support-portal-in-xcloud/) rather than editing multisite configuration blind.

Still stuck? Contact our **[support team](https://support.xcloud.host/)** for any of your queries.