Domain switchover safely on SGEN

How to switch your domain to SGEN safely and without losing search signals

Acme Coffee Roasters has spent six weeks building on their SGEN staging subdomain. The site looks right, the blog is migrated, the pre-launch SEO audit is complete, and the team is ready to switch the public domain from the staging URL to the real one. Done carefully, the domain switchover takes under an hour and visitors and search engines follow without disruption. Done without a plan, it can strand traffic, produce mixed TLS warnings, and reset the search engine signals the business spent months accumulating.

This guide covers the domain switchover from start to finish: adding the custom domain in the SGEN admin, updating DNS at your registrar, confirming TLS, verifying the redirect chain from staging to production, and sending the right signals to search engines so they update their index quickly.

What is this for?

This guide is for SGEN admins who have finished building and reviewing a site on a staging subdomain and are ready to point their real business domain at the SGEN site. It covers the full technical switchover procedure — the settings to change in SGEN, the DNS records to update at your registrar, what to verify before and after the switch, and how to help search engines find the new domain quickly.

This guide does not cover purchasing a domain, setting up a domain registrar account, or configuring email hosting. Those are handled by your domain registrar separately from SGEN.

Good use cases

Example 1: New business launching for the first time. Acme Coffee Roasters registered their domain six weeks ago but had not used it for anything yet. They pointed it at the SGEN site with no prior site to redirect from. The switchover was straightforward — add the domain in SGEN, update the DNS A record at the registrar, wait for propagation, confirm TLS, then submit the sitemap to search consoles. The site was live and indexed within 48 hours.

Example 2: Switching from an existing site. Acme Wine Co. had a website on a different platform. Before switching the domain to SGEN, they confirmed all pages had redirects configured in SGEN's Redirects panel, the pre-launch SEO audit was complete, and the previous site was still live so there was no gap in availability. They updated the DNS A record, waited for propagation, confirmed the new site was loading, then took the old site offline. At no point during the switchover were visitors unable to reach the business.

Example 3: Staging subdomain redirect. After the domain switchover for Acme Studio, the staging subdomain was still accessible — visitors who had bookmarked it, or search engines that had crawled it, could still reach the staging URL. The team added a 301 redirect in SGEN's Redirects panel from the staging subdomain to the production domain, so any traffic arriving at the staging URL was forwarded to the live site immediately.

Example 4: www vs non-www decision. Acme Coffee Roasters decided to use the non-www form (yourdomain.com) as the canonical domain and redirect www.yourdomain.com to it. The SGEN domain settings have a toggle for this — enabling Include www redirect sets up the redirect automatically once TLS is provisioned for both variants. The canonical URL in site settings and on each page was set to the non-www form before the domain switch so search engines indexed the correct canonical from the start.

Example 5: Preserving accumulated search signals. Acme Coffee Roasters had been operating on a previous domain for two years and wanted to move their accumulated authority to the new domain. Before switching, they confirmed every page on the old domain had a 301 redirect pointing to the correct equivalent page on SGEN. After the switch, they used Google Search Console to submit a change-of-address notification. Within three weeks the new domain had inherited most of the signal from the old one.

What NOT to use this for

How this connects to other features

Before you start

Before beginning the domain switchover, confirm all of the following are true:

Plan the switchover for a low-traffic period — early morning on a weekday is typical. This minimises the number of visitors who encounter any brief transitional state during propagation.

• The pre-launch SEO audit is complete and all items on the checklist are marked done.
• All redirects from old URLs are configured in Admin → Redirects and have been tested.
• The site content is reviewed, approved, and ready for public visitors.
• You have login access to your domain registrar — you will need to update DNS records there.
• You know the current DNS TTL (Time to Live) for the domain's A record. A shorter TTL means faster propagation when you make the change. If the TTL is currently set to 24 hours (86400 seconds), consider lowering it to 300 seconds (5 minutes) a day before the switchover — this reduces the propagation window from up to 24 hours to under 10 minutes.

Where to go

The switchover touches two systems:

• SGEN admin — Admin → Settings → Domains
• Your domain registrar — the control panel where your domain's DNS records are managed (this is specific to your registrar: Namecheap, GoDaddy, Cloudflare, Google Domains, etc.)

After the switch, you will also need access to your search console accounts (Google Search Console, Bing Webmaster Tools) to submit the sitemap and, if applicable, a change-of-address notification.

Steps — domain switchover

1. Add the custom domain in SGEN

Before updating your DNS records, add the production domain to your SGEN site. This tells SGEN to expect traffic for that domain and begins the TLS certificate provisioning process.

1. Go to Admin → Settings → Domains.
2. Click Add Domain.
3. Enter your production domain — use the form without www if you plan to use the apex domain as your canonical (e.g., yourdomain.com rather than www.yourdomain.com).
4. Enable Include www redirect if you want www.yourdomain.com to automatically redirect to yourdomain.com. This is recommended for most sites.
5. Leave TLS certificate set to Auto-provision — SGEN will request and install a certificate automatically once DNS is pointing at the platform.
6. Click Add Domain.

After adding the domain, SGEN shows the DNS records you need to set at your registrar. Keep this screen open — you will copy the values from it in the next step.

2. Update DNS records at your registrar

Log in to your domain registrar and update the DNS records for your domain to point to SGEN. The exact steps vary by registrar, but the records to set are the same:

1. Find the DNS management section for your domain (labels vary: DNS Settings, Zone Editor, DNS Records, Name Servers).
2. Update or create the A record for the apex domain (@): - Set the Value to the SGEN IP address shown in Admin → Settings → Domains. - Set the TTL to 300 if possible.
3. Update or create the CNAME record for www: - Set the Value to the SGEN hostname shown in Admin → Settings → Domains.
4. Save the DNS changes at your registrar.

DNS propagation can take anywhere from a few minutes (if TTL was pre-lowered to 300) to several hours (if TTL was at the default 24-hour value). During propagation, different visitors may be directed to the old site or the new SGEN site depending on which DNS servers they query. This is normal — it is not an error.

To monitor propagation, use a public DNS lookup tool and check whether the A record for your domain is returning the SGEN IP address. Once it is, propagation is complete for that DNS server.

3. Confirm TLS certificate is active

SGEN auto-provisions a TLS certificate for your domain once DNS is pointing at the platform. The certificate provisioning starts after SGEN can verify that the DNS records are in place — this typically happens within a few minutes of propagation completing.

To confirm TLS is active:

1. Go back to Admin → Settings → Domains.
2. Find your domain in the list.
3. Check the TLS column — it should show Active once the certificate is provisioned. While provisioning is in progress it shows Pending.
4. Open your domain in a browser — yourdomain.com — and confirm the padlock icon appears in the address bar, indicating the connection is secure.

If TLS is still showing Pending after 30 minutes post-propagation, confirm the DNS A record is correctly set by running a DNS lookup. If DNS looks correct but TLS is still pending after one hour, contact SGEN support with your domain name and the time DNS was updated.

4. Verify the redirect chain from staging to production

After the production domain is live and TLS is active, confirm that the staging subdomain redirects correctly to the production domain. This is important for two reasons: visitors who bookmarked the staging URL during the review period will land on the live site, and any search engine that crawled the staging subdomain will follow the redirect to the production domain.

To set up and verify the staging redirect:

1. Go to Admin → Redirects.
2. Click Add New.
3. Set Source to the staging subdomain path (e.g., yourstagingsubdomain.sgen.com).
4. Set Destination to your production domain (e.g., yourdomain.com).
5. Set Type to 301 Permanent.
6. Click Save.
7. Open the staging URL in a browser and confirm it redirects to the production domain.

Also verify the www redirect if you enabled it in Step 1: open www.yourdomain.com and confirm it redirects to yourdomain.com (or vice versa, depending on which form you chose as canonical).

5. Update site canonical URL and sitemap domain

Now that the production domain is live, confirm that the site-level canonical URL and sitemap settings reference the production domain — not the staging domain.

1. Go to Admin → Settings → SEO.
2. Check the Site canonical base URL. Update it to the production domain if it still shows the staging URL.
3. Click Save Settings.
4. Go to Admin → Settings → Sitemap.
5. Confirm the Domain field shows the production domain.
6. Click Save Settings.
7. Open the sitemap URL in a browser — yourdomain.com/sitemap.xml — and confirm it lists production domain URLs, not staging URLs.

6. Submit sitemap to search consoles and send change-of-address signal

With the production domain live and the sitemap confirmed, signal to search engines that the site is ready to be indexed:

1. Google Search Console — add the production domain as a property, verify ownership, and submit the sitemap URL (yourdomain.com/sitemap.xml) under Sitemaps in the left navigation. If you are moving from a previous domain, use the Change of Address tool under Settings to notify Google of the domain move.
2. Bing Webmaster Tools — add the site and submit the sitemap. Bing also accepts change-of-address notifications if you are moving from a prior domain.

Search engine re-indexing after a domain switch typically takes two to four weeks for full propagation. During this period, monitor search console for crawl errors, indexing status, and any warnings about the new domain.

What success looks like

What to do if it does not work

TLS not provisioning after propagation. Confirm DNS is correctly set by using a public DNS lookup tool. If the A record returns the SGEN IP, DNS is correct — contact SGEN support with the domain name and propagation confirmation. If the A record still returns the old host's IP, wait longer or confirm the change was saved at the registrar.

Site loading at staging URL but not production domain. This means DNS has not yet propagated to your network. Use a DNS lookup tool to check whether other networks see the new A record. If they do and you do not, it is a local DNS cache issue — flush your local DNS cache or test from a mobile network.

Search engines indexing staging URL instead of production. Add the staging-to-production 301 redirect (Step 4) and submit the production sitemap to search consoles. If the staging domain was crawlable before the switch, use the change-of-address tool in Google Search Console to accelerate the transition.

Domain switchover checklist