I have an email that is sent to the user's email address when they sign up to my site, but certain threat protection services like outlook's safelinks breaks the functionality because it calls the link before the user's client does, so in the case of email verification, the user clicks the "safe link" and that is making a GET request to my nextjs app where it's then being executed and verifying the user's email address, but by the time safe links redirects the user, the user is seeing "invalid email verification" which is proving to be a bit of a pain, I did it redirect to a page with a button that said "verify email" - but I hate this approach so much, it's so unintuitive, I've googled a lot about this issue, but have been unsuccessful in finding a work around. Does anyone have any ideas on how to solve this issue without adding an extra step?

(I've read that it's the initial HEAD request that's the problem, but not sure how to prevent a page.ts from calling code based on a HEAD request).