SEOSTUDIO™

How do I fix a WordPress redirect loop after enabling HTTPS?

Capture each HTTP response for one affected page. Compare your intended public origin with the two WordPress address settings and any proxy redirects. Correct the rule that sends the request backward, then repeat the original visitor and sign-in journeys.

What does the problem look like?

The browser stops with too many redirects, or switches repeatedly between host names. Public pages can work while a login path still loops.

Before you make changes

Keep a copy of the original rules and address values. Confirm access to the server or managed hosting dashboard. Reproduce the routing in an access-controlled environment when possible.

Step-by-step troubleshooting

  1. Make a small request matrix

    Test the original path over HTTP and HTTPS on each configured host. Record every response status and Location target from a fresh session.

  2. Locate the return hop

    Find the first repeated URL. Match it with the web server, edge service or WordPress rule that produced its preceding response.

  3. Check HTTPS detection at the origin

    Ask the hosting team how the application receives the original protocol. Verify the supported setup if the TLS connection terminates at a proxy.

  4. Compare WordPress address settings

    Preserve the distinction between where application files live and the public site address, particularly with a subdirectory install.

  5. Release the smallest fix

    Apply the proven setting or rule. Test the home page, another public route, sign-in and a URL with an allowed query string.

Worked example

A publisher moves its public site from www.example.com to example.com. The edge implements the new convention, but WordPress still selects the old host. The team traces the opposite redirects on a test hostname, aligns the responsible rule and verifies a category and an archive path.

Common mistakes

  • Assuming the browser’s last URL identifies the rule responsible.
  • Removing every redirect rule to resolve one conflict.
  • Changing both WordPress URLs before checking how the installation is laid out.

Verify the fix and plan a rollback

How to verify the fix

Every intended entry variant reaches the preferred content without revisiting a prior URL. The public page and the sign-in journey return the expected content.

If the change fails

Restore the previous value or redirect rule if a second path breaks. Preserve the recorded chain so the correct service owner can inspect its own layer.

Practical follow-up questions

How can I tell which redirect starts the loop?

List destinations in order and mark the first repeated address. The response immediately before that return hop gives you the next rule or service to inspect.

What should I record for an HTTPS-only loop?

Capture the original scheme, the URL sent in Location and the responding service when known. Check how the origin recognizes requests forwarded from the public HTTPS edge.

Why can my login loop when the homepage looks fine?

Login may use additional access rules and session cookies. Reproduce the affected action with an authorized test account on the corresponding environment and inspect that response.

Can two www rules contradict each other?

Yes. One layer can redirect from www to the bare domain while another reverses it. Align them with the approved hostname and retest both variants.

How do I preserve a WordPress installation in a folder?

Confirm the application file address separately from the public website address. Retain the intentional subdirectory and validate the path to sign-in and existing content.

What if reports disagree about the active redirect?

Test with a fresh browser and a public trace on the exact same path. Check edge cache behavior and compare timestamps before changing a second layer.

When does a permanent redirect make sense after a migration?

Use it after confirming the move is durable and destinations are right. Check the old production URL, exact final path and expected status before finalizing.

How should I test deep links and query values?

Choose a nested path and an approved query used by your site. Verify the route and required parameter reach the destination. Check path mappings separately from host redirects.

Can a redirect repair alter a different subdomain?

A broad host rule can affect other routes. Review its scope and retest the subdomains covered by that rule before release.

What evidence is safest to share with support?

Send the exact public URL, sequence of status codes and destinations, and timestamp. Leave session headers and sensitive parameters out of the ticket.

Free tools and website checks

Frequently asked questions

Does a canonical tag cause the redirect in my browser?

Inspect the actual network responses and scripts. Canonical markup communicates a preferred URL to search engines.

Can the public checker trace a signed-in request?

Use its public trace for the entry URL, and capture the private request separately with your own browser.

What if the chain ends normally on a 404?

Investigate the destination path or WordPress permalink handling after establishing the routing chain ends at the intended URL.

Official references and scope

Sources checked

Related guides