Termly Setup Blocker — Domain Redirect Issue

Overview

During a check-in between Mark and Karly, an attempt to configure Termly for ^[1] surfaced a technical blocker: the domain currently redirects, which prevents Termly from completing its required cookie-scanning process. Until the site is live at its final URL, Termly setup may not be possible.

Background

The goal was to configure Termly for finwellu.com in order to generate a privacy policy for the client. The domain exists in the server but is not yet set as the primary domain — it is still operating under a staging or predecessor configuration (referenced as "Next Level Planning"). When navigating to finwellu.com, the domain redirects rather than resolving to the live site.

The Blocker

Termly's setup process performs a crawl of the target domain to:
- Identify cookies in use
- Detect third-party scripts and tracking technologies
- Generate a privacy policy based on actual site content

When the domain redirects, Termly cannot complete this scan and the setup process fails or produces an incomplete result.

"I think it wants to look at the website when it's configuring, like to look at what's on there and what cookies are being used… if I try to fire it up and I give it the Finwell U domain, it may spaz when it gets redirected."
— Mark Hope

Status

Action Items

• [ ] Mark Hope — Attempt Termly setup for finwellu.com; report back to Karly on whether the redirect causes the scan to fail
• [ ] If scan fails, defer Termly configuration until the site is taken live at its final URL

Related

• ^[2]
• ^[3]