Primary domains, aliases, HTTPS, and redirects

Documentation / Site administration and domains

A website's primary domain identifies its intended public address. Aliases are additional hostnames configured for that site. DNS resolution, hosting attachment, HTTPS validation, and Beeboo's canonical routing are separate checks; success at one stage does not prove the others are ready.

Confirm the configured hostnames

Review Settings > Domain for the active domain and its apex and www verification results. An authorized super administrator can also review the site's domain aliases in the Super Admin site editor. An alias in site settings still needs appropriate DNS and hosting configuration.

Use Check DNS Status and wait for verification. A certificate-pending state can remain even when a DNS record appears correct. Use only the DNS targets displayed for this website, not values copied from another deployment.

Test canonical routing

For public production page requests, the engine can redirect a noncanonical hostname to the primary domain with a permanent 308 response. Development, private sites, preview requests, and non-page requests have different handling, so do not judge canonical behavior solely from an authenticated preview.

Test each intended hostname over HTTPS in a visitor session. Confirm that it serves the correct site or reaches the intended primary address without a loop. Check a nested page and a translated route as well as /.

Separate page redirects

A moved page can use page-level redirect settings, while site settings also support redirect rules. Domain attachment does not automatically supply every old page redirect. Review legacy paths before launch and verify their final destinations.

If a redirect loops, check the primary domain, alias configuration, and page or site rules together. Do not work around a certificate error by sharing an insecure address. Ask the administrator to resolve hosting or DNS validation. See pages and navigation and search visibility and sharing.