Plain http Address Does Not Redirect to https
Typing the site with http:// opens a page on the insecure address instead of sending visitors to the secure one. Browsers may warn visitors, and search engines see two copies of every page.
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Typing the site with http:// opens a page on the insecure address instead of sending visitors to the secure one. Browsers may warn visitors, and search engines see two copies of every page.
Why it matters
Typing the site with http:// opens a page on the insecure address instead of sending visitors to the secure one. Browsers may warn visitors, and search engines see two copies of every page. This affects crawlability, rendering, and whether the site can be interpreted correctly by search engines.
How we detect it
- FreeSiteAudit flags this issue when the rule for TECH-HTTP-REDIRECT-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
How to fix it
- 1Redirect every http:// address to its https:// version with a permanent (301) redirect
- 2Most hosts have a "Force HTTPS" switch in their dashboard
- 3Check the result with a browser: http://yourdomain should land on https://yourdomain in one step
How to re-check it
- Open the http:// version of the address and confirm it ends on https:// after one redirect
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.