Fix WordPress redirect loop behind Cloudflare on SiteGround: when this repair path applies
Use compatible HTTPS settings at Cloudflare and SiteGround, then keep only one canonical redirect sequence. Use these steps when edge and WordPress/origin HTTPS rules disagree, but first run the embedded diagnostic so the TLS, certificate and HTTPS evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
SiteGround Site Tools for Domain/DNS, Security/SSL and Email configuration. For Fix WordPress redirect loop behind Cloudflare on SiteGround, confirm the active nameservers and exact service owner before changing confirm origin supports HTTPS. A DNS-looking screen at siteground has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix WordPress redirect loop behind Cloudflare on SiteGround
Record the current public state for confirm origin supports HTTPS, use Full/Strict where valid, remove duplicate redirect plugins/rules. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Confirm origin supports HTTPS — Record the public status, final URL and relevant response headers. A working DNS answer does not prove that the application is serving a genuine website response.
- Use Full/Strict where valid — Verify use Full/Strict where valid from the public Internet and compare it with the value the responsible provider says should be live.
- Remove duplicate redirect plugins/rules — Follow every hop rather than checking only the final page. The conflicting rule is usually visible where the chain changes scheme, hostname or destination repeatedly.
- Test chain — Verify test chain from the public Internet and compare it with the value the responsible provider says should be live.
Repair steps in siteground
Use compatible HTTPS settings at Cloudflare and SiteGround, then keep only one canonical redirect sequence.
- 1. Confirm origin supports HTTPS. After this step, check the public value tied to confirm origin supports https before changing another unrelated setting.
- 2. Use Full/Strict where valid. After this step, check the public value tied to use full/strict where valid before changing another unrelated setting.
- 3. Remove duplicate redirect plugins/rules. After this step, check the public value tied to remove duplicate redirect plugins/rules before changing another unrelated setting.
- 4. Test chain. After this step, check the public value tied to test chain before changing another unrelated setting.
Why this order matters for siteground
The sequence begins with the provider/authority decision, then moves through confirm origin supports HTTPS, use Full/Strict where valid, remove duplicate redirect plugins/rules. That keeps the change scoped to the failed TLS, certificate and HTTPS path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix WordPress redirect loop behind Cloudflare on SiteGround
HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. Compare the same confirm origin supports HTTPS and use Full/Strict where valid evidence used before the change; a repair is complete when the public result agrees, not merely when the siteground interface reports that a save succeeded.
If siteground and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting confirm origin supports HTTPS value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix WordPress redirect loop behind Cloudflare on SiteGround should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.