# How To Redirect HTTP Visits to HTTPS With BetterShield?

Visitors who open an http:// link are sent to your https:// address.

With **[BetterShield](/)**, visitors who open an http:// link are sent to your https:// address.

## What it does

**HTTPS redirect** is under **BetterShield › Protection › Hardening**. Visitors who open an http:// link are sent to your https:// address. It is off by default.

<span id="set-it-up" aria-hidden="true"></span>

## Step 1: Open Protection › Hardening

Open **Protection › Hardening** and find **HTTPS redirect**.

<figure class="doc-shot">
  <img src="/docs/screenshots/redirect-http-to-https.png" alt="Redirect HTTP visits to HTTPS: saved state and available controls in BetterShield." width="980" height="168" loading="lazy" decoding="async">
  <figcaption>Review the state and choices shown on your own site before applying a change.</figcaption>
</figure>

## Step 2: Redirect HTTP visits to HTTPS

- Open its preview and read what will change. The preview changes nothing.
- There are no extra fields. Requests to HTTP are sent to the secure address.
- Turn on the fix. If the screen asks you to confirm recovery or your password, complete that before continuing.

## Recommended settings

Our advice is to test this on staging, then apply it when the behavior fits the site. Keep a working recovery method before changes affecting sign-in or the site address.

## What it can break and how to undo

Confirm the HTTPS site and proxy configuration work first. A proxy configured incorrectly can cause a redirect loop. Turn the fix off to use its undo, then check the original workflow. A change is recorded in the activity log; an undo does not erase that record.

<span id="check-it-is-working" aria-hidden="true"></span>

## Final Outcome

The row should show the fix is on. Test the affected operation with an appropriate account, then check the finding. The score and Findings update on their own after the change. If the finding stays open, press **Check Again** to see what the check still sees. A server or another plugin can enforce a setting independently, so switching BetterShield off does not necessarily remove that other protection.

<figure class="doc-shot">
  <img src="/docs/screenshots/redirect-http-to-https.png" alt="Redirect HTTP visits to HTTPS: saved state and available controls in BetterShield." width="980" height="168" loading="lazy" decoding="async">
  <figcaption>Example HTTPS redirect view. Check the saved values and status on your own site.</figcaption>
</figure>

## Related

- [Hardening overview](/docs/hardening/)
- [Set up recovery](/docs/set-up-recovery/)
- [Activity log](/docs/activity-log/)

This is how you can redirect HTTP visits to HTTPS with BetterShield.

Getting Stuck? Feel free to contact our [Dedicated Support Team](/support/).