Choose the source and destination
Decide whether visitors should move from `www.example.com` to `example.com` or in the opposite direction, then use that choice consistently in links and public materials. Confirm the exact destination scheme and path behavior you want, including whether a trailing path should be preserved. A vague rule can send visitors to an unexpected page or create a loop.
Check that the source hostname exists and that the traffic can reach the redirect service. A rule cannot act on requests that never arrive at the service handling it. If the source already has DNS records or another service attached, review those settings before changing them so you do not interrupt unrelated traffic.
Test the redirect without creating a loop
After saving the rule, test the source address in a private browser window and follow the destination. Try both the root page and a path with a query string if those are used on your site. Confirm the final URL is the preferred one and that it does not alternate between the two hostnames.
If the redirect does not run, separate the checks: confirm the rule target, verify that the source host is active, and check the DNS or traffic settings needed for the rule to see requests. Change one item at a time. Keeping a clear canonical hostname also helps prevent duplicate links and makes the intended address easier for visitors to recognize.