Playbook · Shopify redirect loop after domain

Domain connected — browser loops.

Written for a Shopify owner who just connected a custom domain and now hits ERR_TOO_MANY_REDIRECTS — SSL still pending while HTTPS is forced, primary domain unset during cutover, www and apex both forwarding, Cloudflare Flexible SSL fighting Shopify, leftover registrar redirects — or you chased Markets geo-IP redirect, a stable www↔apex loop, SSL pending alone, or password page instead. DIY-first: prove SSL / primary / redirect chain → fix cutover owners → retest. Distinct from geo-IP redirect loop, www / non-www redirect loop, custom domain SSL not connecting, and password page stuck online. Soft-link password page customization missing when branding is the only gap after the loop is gone, and canonical URL wrong when SEO consolidation is the leftover issue. No earnings claims, no invented case studies.

Nico at Latch AI Ops · Sep 10, 2026 · ~12 minute read

Buy the 72-hour install — $997 www loop SSL pending Merchant FAQ

Redirect loop after domain — not geo-IP, not stable www↔apex, not SSL pending alone, not password page.

Several “store will not load” bugs look alike. They do not share a fix. This page is only when ERR_TOO_MANY_REDIRECTS started right after you connected or switched a custom domain — SSL pending racing HTTPS force, primary domain unset, www/apex both redirecting during cutover, Cloudflare Flexible SSL, leftover registrar forwarding. Markets / geo IP country redirect looping is shopify-geo-ip-redirect-loop. Stable www ↔ apex loop long after the domain was already live is www-redirect-loop-shopify. Custom domain SSL not connecting without a redirect loop is custom-domain-ssl-not-connecting. Password page stuck online is password-page-stuck-online.

Soft-check shopify-canonical-url-wrong when the loop is gone but Google still shows the wrong host, and shopify-password-page-customization-missing when the store loads but the coming-soon page cannot be branded.

Prove SSL status, primary domain, and the redirect chain during cutover.

Open Settings → Domains. Screenshot every connected hostname, which one is Primary, and SSL certificate status (pending vs issued). From a terminal: curl -I http://apex, https://apex, http://www, https://www — capture every Location header both ways. Soft-check Cloudflare SSL/TLS mode (Flexible vs Full / Full strict), Always Use HTTPS, Page Rules, and Bulk Redirects. Soft-check registrar domain forwarding still aimed at myshopify.com or an old host. Soft-check whether you flipped HTTPS-only while Shopify still shows SSL pending.

If the loop only happens when Markets geo-IP / country redirect apps fire, switch to shopify-geo-ip-redirect-loop. If SSL is pending and the page never loads (no redirect loop), switch to custom-domain-ssl-not-connecting. If the domain has been live for weeks and only www↔apex fights, switch to www-redirect-loop-shopify.

Fix cutover: one primary, settle SSL, one redirect owner, then retest.

Set one primary hostname in Shopify Domains. Wait until SSL shows issued before forcing Always Use HTTPS everywhere — or temporarily DNS-only / pause HTTPS redirects until the cert is green. Move Cloudflare off Flexible during cutover (Full or Full strict once origin TLS works). Remove competing registrar forwarding and Cloudflare Page Rules so only one owner redirects www↔apex. Keep A/CNAME pointed at Shopify targets only once.

Honest retest: apex and www each take a single hop to the primary and return 200 with no ERR_TOO_MANY_REDIRECTS. Hard refresh in a private window. If SSL stays pending with no loop, switch to custom-domain-ssl-not-connecting. If the loop returns weeks later as a stable www↔apex fight, switch to www-redirect-loop-shopify.

You tested geo-IP, stable www↔apex, SSL pending alone, or password page instead.

Markets / geo IP country redirect looping is shopify-geo-ip-redirect-loop. Stable www ↔ apex redirect loop is www-redirect-loop-shopify. Custom domain SSL not connecting alone is custom-domain-ssl-not-connecting. Password page stuck online is password-page-stuck-online.

The only honest test for this page: ERR_TOO_MANY_REDIRECTS started right after custom domain connect / cutover. Anything else is a different product.

When to stay DIY vs pay $997.

Stay DIY if you can spend one afternoon on the list above: set one primary, settle SSL, remove competing redirect owners, retest. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: www redirect loop, custom domain SSL not connecting, geo-IP redirect loop.

Pay for help when the work is not the DNS field itself — it is connecting the stack you already have so storefront / domain / SSL / redirect exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a theme rebuild retainer, not a conversion guarantee, not a brand or theme job.

Other shops' public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever domain / SSL guarantee, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.

Open Whop checkout — $997 www loop SSL pending Merchant FAQ