WWW vs Non-WWW: How to Pick One Website Address

Choose a canonical website hostname and set permanent redirects that keep paths, HTTPS and search signals consistent.

WWW vs Non-WWW: How to Pick One Website Address

Quick answer

Both www and the bare domain can work. Pick the hostname your website will use consistently, make both names reachable over HTTPS, and redirect the secondary hostname to the matching path on the preferred one.

Test the whole redirect map on one deep path

Imagine a site chooses https://example.com as primary. Pick one real guide, such as /guides/first-launch, and check the HTTP and HTTPS variants on both example.com and www.example.com. The secondary variants should converge on the matching preferred HTTPS route. A useful terminal inspection is `curl -sSI https://www.example.com/guides/first-launch`. Read the status and Location fields, then visit the final page and confirm its contents. For a permanent move, server-side 301 or 308 can express that intent. A successful response at the wrong path is broken navigation even if the status looks acceptable. Check the reply headers from the live service to see what it actually does.

After proving delivery, inspect the page’s canonical tag and the matching sitemap entry. Both should point to the preferred host directly. Edit templates and generated absolute URLs as needed. Keep old public links useful for readers and avoid unnecessary redirect chains when you can send visitors directly to their intended final URL. If the site has logins, review which cookie and callback settings depend on the hostname. Those flows deserve their own staging checks because a home page redirect test cannot establish that authentication will still work. A practical release record includes several starting URLs, their destinations and the layer that creates the rule. If the registrar makes the redirect, verify HTTPS support at that layer before treating the configuration as complete.

Choose the durable public hostname

An established site already has both addresses in use. Before putting time or money into this step, agree on a concrete criterion. Treat whatever is essential to complete the job as a mandatory requirement. Keep convenience, speed and ease of handoff in a separate part of your notes. This helps you avoid promoting something that looks easier in a trial but cannot complete a critical part of the task.

Start here. Review incoming links, current Search Console data where available, navigation, marketing materials and hosting constraints. Choose the hostname the team will preserve.

A redesign changes hostnames casually and leaves established paths without redirects. Think through how a customer or colleague would discover this error. A clear, visible failure is easier to resolve than a result that looks successful and leaves a problem for the next person. If it would be hard to notice, add one direct inspection that examines the outcome itself. Record evidence for the result instead of relying entirely on a successful status label.

Confirm the result. Record the intended final URL for both homepage and representative deep links. Work through this step before expanding the change. One realistic example is enough to reveal a category of failures that an ideal example misses. A trial is also a useful time to learn what to do when the result is ambiguous, especially if different people would have to resolve disagreement.

For a new site, verify the host supports the DNS and TLS setup before sharing the name widely. Capture the decision and the reason in a short note so it can be revisited if the workload, policy or software changes.

Resolve both names first

Example situation. A secondary domain alias must redirect immediately.

Set each name up in DNS and the hosting or redirect layer. HTTPS certificates need to cover names that receive HTTPS connections before they can redirect. Give the test enough room to show the original problem. Use the same entry point that someone with the issue would use. If several variables change between attempts, note which ones cannot be held constant and avoid assigning a cause yet. You can make a smaller experiment after getting that first picture.

HTTP users are redirected but HTTPS visitors to the old name see a certificate error. It helps to document the specific contrast as soon as you see it. Save an innocuous screenshot, a small sample or a short time record if appropriate, with identifying details removed when they are unnecessary. The next person will need a result that can be interpreted without guessing what happened immediately before you captured it.

Inspect the outcome. Test all supported HTTP and HTTPS entry aliases in a clean browser session. If you need to hand this to support or a maintainer, include the expected outcome, the first unexpected observation and the last known working state.

Retest after automatic certificate renewal or after moving the redirect between providers. Write down whether the follow-up confirms your original explanation or exposes another factor. Confirmed evidence supports a specific change. If the behavior still varies without a known reason, retain the last working settings and focus the next test on that variation.

Keep path and useful query parameters

A bookmarked article has a referral query parameter. Decide what should stay intact while you try the change. For a small trial this might be the original input, a visible result another person already depends on, or access from a second supported device. Keep an appropriate copy or note of the earlier state. Tests that are easy to reverse make it possible to learn even when the first idea is wrong.

Map each page to the equivalent preferred address. Preserve meaningful routes and parameters where product and privacy requirements allow.

Watch for this: Every old deep link redirects to the homepage and visitors lose the requested page. Consider the exact point where you would stop and revert. If the issue appears, reproduce it without repeating a consequential action unnecessarily. A disposable example or read-only observation can give you the needed evidence. In a shared environment, tell others handling the test what state you expect to see before the next step.

Use a browser network panel or simple header request to verify destination status and final path. Verify the ordinary case that should have remained intact as well as the intended improvement. If one passes and the other fails, keep both observations and examine the relationship between them.

Test an encoded path and a representative referral URL rather than only the bare homepage. Use the result to write a one-sentence acceptance condition. Make it specific enough that another person would know which setup to use and when to stop.

Align visible and technical signals

The chosen hostname is www but internal content sometimes links to the root.

Update internal navigation, absolute canonical URLs and sitemap entries to point directly at the preferred hostname. Align generated share URLs too. Start with conditions you can readily repeat. Ask if your normal day includes a meaningful variation, such as a busy period, a second account or input from a different source. Select the variation based on your real use instead of trying every theoretical case.

The redirect works but page metadata still advertises the other hostname. Record whether you found a recurring failure, a one-time event or an unresolved observation. The three have different implications. A repeating mismatch is easier to verify and to pass along for repair. A one-time interruption can still matter, but document the context and look for a separate observation before committing to an explanation.

Inspect the served HTML and sitemap rather than trusting the CMS settings screen alone. A simple check for the result usually beats a complicated proxy. If a reading looks surprising, return to the user-visible outcome and trace it back to the earliest relevant event you can observe. Comparing that observation to the expected rule may show exactly what additional information to collect.

Check data-driven pages and maintenance templates that render links through separate code. Use a representative size or repetition count when it affects the result. If a small test and a normal-sized workload behave differently, include both in the handoff so the earlier test can be understood in context.

Avoid loops across hosting layers

Use this case to review the plan. Both a reverse proxy and the origin have redirect rules.

Decide one layer responsible for host normalization and ensure it understands the public request scheme. Check any host-provided defaults. Write down who owns the setting, file, service or decision before considering the trial finished. In a personal setup that may simply mean keeping the needed information somewhere you can find it later. In a shared setup it may determine whether the next person is able to continue during an interruption. Give that person enough context to determine if the result still applies.

Failure that matters: Each layer sends the browser back to the other hostname or scheme.

Read the sequence of redirects and identify which layer produced each response. A successful check has a concrete observable result. Confirm it from the normal user path, then put the test input and the observation in your notes. If cleanup is needed, remove test artifacts carefully and retain the benign evidence needed to repeat the test later.

Prefer a short direct redirect path and test from an ordinary external connection. Check any agreement about when to rerun the trial. An annual review can miss changes that happen at a specific release or after access is revoked. Conversely, some checks make sense on a fixed calendar because no individual event will remind you to try them. Choose the trigger that fits the use case and record a known starting point.

Verify matched content

Try it when you need to: The new host normalization is deployed.

Compare titles, body content and assets from a shortlist of approved pages. Confirm the destination serves the expected route with a success response.

Establish the expected result before starting. A useful way to make this concrete is to describe the one thing you plan to observe and the condition under which it should hold. Save a baseline using the same input or conditions you will use after the change. If another person helps, have them record the expected result independently. That can surface a difference in interpretation before you spend time debugging an apparent failure.

An easy mistake to miss: A redirect reaches a generic parking page that returns a successful status.

Open the final page and check a known heading or other identifying content. Preserve the comparison in a form you can come back to: write down the input, what you expected and what you actually saw. In a decision with several options, keep one record per option rather than changing the definition of success for each trial.

Include a missing page to confirm it still behaves as intended. Think about whether this follow-up calls for revising the original rule or handling a separate case. If it is separate, keep the original test available and check that both cases still succeed. This is also useful when you need to explain why something that looked fine in a demonstration behaves differently in ordinary use.

Review search visibility after a change

The old hostname still appears in some search results. This is a good place to watch where the result starts to differ from what you expect. Note the entry conditions and any settings or data that you have assumed. Take an initial reading, then do the work with those same conditions recorded. Avoid resetting everything at the first sign of trouble. A change that accidentally hides the symptom gives you less information about what caused it.

Verify the new canonical signals and look at Search Console inspection and impressions over time. Keep redirects functioning for previous users and external links.

Inspect this failure: A team removes redirects because its own bookmarks have already changed. Make the first follow-up test small enough to repeat without changing unrelated parts of the setup. Start at the first boundary you can observe, then check the next one only if the initial result was right. Write down the observations in order. A later symptom can look like the root problem if you check the later step first and do not have an earlier reading.

Check previous linked URLs, new canonical metadata and sitemap processing independently. When the check is successful, repeat the ordinary action from its normal starting point. This catches results that only worked because the original test left a session, a temporary setting or a sample file in place. If somebody else follows the directions later, their starting conditions might be different.

Investigate examples if search continues selecting an unexpected canonical after recrawling.

Document ownership and rollback

Hosting and site code are maintained by different teams.

Begin with a simple case where you can tell if things went wrong even before looking at any reports. Keep a copy of the starting inputs and confirm the result that ought to follow from them. Ask what the user will see and what the underlying system ought to do. Those are worth checking separately when a screen, message or summary can still look correct even though a change did not reach the place you intended.

Record DNS owners, certificate coverage, primary address, redirect layer and verification routes. Keep a copy of previous rules for staged recovery.

A provider change introduces an undocumented redirect that conflicts with the app. Include this possibility when you define a failure. Try a known good case beside the suspected one. If both fail in the same way, examine what they share. If only the particular case fails, save the difference that makes it a useful test.

How to verify: Have a second person test both aliases and identify the correct setting for each.

Review the policy when adding new subdomains so special services retain their own expected URLs. On the next pass, use a second representative input or condition to make sure the first result still applies. A narrow test can be decisive if it measures the thing you need. A wider sample is useful when your real work includes several distinct patterns and one result cannot stand for all of them.

A short verification checklist

What to checkHow to tell
Choose the durable public hostnameRecord the intended final URL for both homepage and representative deep links.
Resolve both names firstTest all supported HTTP and HTTPS entry aliases in a clean browser session.
Keep path and useful query parametersUse a browser network panel or simple header request to verify destination status and final path.
Align visible and technical signalsInspect the served HTML and sitemap rather than trusting the CMS settings screen alone.

## Verify more than the root path
Build a short matrix for /, a long-established article, a dynamic page with a relevant query and a nonexistent page. Inspect each canonical request and its aliases. Confirm expected redirects for the first three and a useful missing-page response for the last. Save both the redirect destination and the public canonical declared by the document. Review sitemap, navigation and externally managed links where you can edit them. An additional domain or international hostname may have a separate policy. Apply rules to the names you control and record whether a product or localized page intentionally uses another host.

Related reading

Reference documentation explains the relevant standards or workflow. Try the related FixHubLab resource for a practical next step. Use the FixHubLab blog to find the rest of the guide series.