Disable Redirect to Home Page After Email Verification OR Redirect New User to NOT the Home Page

Hello,
I have two versions of a home page. One is for non-logged-in users, and the other is for logged-in users.
My problem is that when a user signs up for an account with my website (i.e., becomes a “member” of my website), they receive a verification link in their email which they click and then are redirected to my home page. Given that they are now “logged in” I want to redirect them instead to the second version of my home page.
OR, I could just disable that redirect, so that the user - after verifying their email - just has to open up the site and hit Login. (Though they may still be detected as Logged in. In which case, I would want to log them out so that they can log in.)
How would I go about either of the above two routes?

I have figured out how to redirect new user to alternative home page. I referred to this article: Redirect Users to a Specific Page after Registration | Webflow User Accounts ( Memberships ) | Sygnal-U. The code I used was:

script tag

// Check if the referrer is the signup page
if (document.referrer.includes(“/sign-up”)) {
// Redirect to the members-only page for logged-in users
window.location.href = “/logged-in-home”; // Change this to the actual URL of the logged-in home page
}

closing script tag

I put this custom code in header of first version of home page.

1 Like

Hi Jacqueline, I’m glad you found my article-
Typically this is the easiest way in Webflow, you have a standard homepage and then a special user-specific homepage.

If you’re trying to combine them at / then the best way is to use a single page design with conditional visibility to hide and show your sections depending on login state.

That can be extended further with SA5 to support conditional visibility by access group, but it typically involves a bit of custom code to build that.

If you wanted to take it to a whole other level, the direction I use is to reverse proxy the site, and the transform pages for the user. Then you can actually have completely different pages at / returned depending on the user’s access group. However this is a complex build, so typically you’d only do this when you’re delivering sensitive content.