How to change the primary domain

To change the primary domain on shared hosting, open a support ticket with us, because cPanel alone cannot rename it. The primary domain is your account’s main site name, default virtual host, and default document root. For many rebrands, an alias with a redirect—or a separate addon domain—is safer than moving the primary name.

What the primary domain actually controls

The primary domain sets the default document root and the name people type for your main site. It is also the mail domain many clients remember, and AutoSSL ties certificates to names you have configured. A half-finished change can leave old hostnames and certificates behind, so plan mail and SSL before you ask us to move it.

Safer options before you rename

If the business rebranded but the site is the same, add the new name as an alias and use a 301 redirect to the canonical HTTPS URL. That keeps the old name working while bookmarks and search results catch up. If you are launching a second property, create an addon domain so it has its own document root and does not disturb the main site.

• New brand, same site: alias plus a 301 redirect, then set WordPress to the canonical HTTPS name.
• Second website: addon domain with its own document root.
• Primary must change: support ticket, a mail plan for the old name, and AutoSSL on both names until the old one is retired.

Your cPanel username and two-factor settings do not change. The account is still the same user; only the main virtual host name on the door is different.

How to request a primary domain change

Shared hosting has no WHM and no root, so primary domain changes go through support. In your ticket, include the current primary domain, the new domain you want, and whether mailboxes should move or stay on the old name. Keep the old name live with redirects until inboxes, bookmarks, and search results have moved over.

Do not remove the old name before redirects and mail are ready, or those addresses will start returning errors. We can help you keep AutoSSL active for both names during the transition. After any of this work, set the WordPress site URL to the canonical HTTPS name so the admin and front end stay aligned.