Hi @Steve Goldberg, quick question regarding the new SCA re-hydration/performance improvement feature. We were testing it on a password-protected site and noticed that re-hydration does not seem to run when the user is logged in / the site is protected. In the SEO debug output we see flags like: •

bypassSeoGeneratorForRecognizedOrLoggedIn=true

•

bypassSeoGeneratorSwitchEnabled=false

and

SC.isRehydrating

ends up being

false

. From what we can tell, the feature appears to be tied to the SEO generator flow. Is that expected behavior by design? If so, could you help us understand the reasoning behind coupling the re-hydration/performance optimization with the SEO generator logic? From a performance perspective, it feels like there are valid use cases for enabling re-hydration even on authenticated or password-protected sites (for example B2B/customer portals), where SEO is not really relevant but frontend performance still is. Just wanted to better understand the intended architecture and whether this limitation is temporary, technical, or intentional.

Yes. SEO page generator does not run on private areas of the site. If you make your whole site private then it will never run.

Thanks Steve!

You asked other questions but I feel like my response covers them – or did you want more detail?

I understand that re-hydration is tied to the SEO generator, so if the page generator does not run, the re-hydration process will not run either. Thanks for your response.