Why it matters
Visitors should not see security warnings or split between www, non-www, HTTP, and HTTPS copies.
Do it step by step
- 1
Open HTTP and HTTPS versions of your domain, with and without www.
- 2
Choose one HTTPS hostname as the preferred address.
- 3
Redirect other public variants to it and fix mixed-content warnings.
- 4
Use the preferred origin in canonicals, internal links, and sitemap.
Example
http://www.example.com/about redirects to https://example.com/about.
Check your work
All public variants land on the preferred secure URL without browser warnings.
Complete when
The live domain is secure and public variants resolve consistently.
Prompt for an AI coding agent
Use this with an agent that can inspect your project. Account and external actions remain yours to complete.
Inspect my existing website project before editing. Use HTTPS and one preferred domain. Open HTTP and HTTPS versions of your domain, with and without www. Choose one HTTPS hostname as the preferred address. Redirect other public variants to it and fix mixed-content warnings. Use the preferred origin in canonicals, internal links, and sitemap. Keep the existing framework and design conventions. Verify the result with the project's checks and by inspecting the rendered page or response. Explain any manual account, hosting, or Search Console steps I must do myself.
Tools and references
Reviewed 2026-11-04