@Subashree seems like something outside AEM scope, but one last try would be show us whats present in anchor href attribute by inspecting the hyperlink? so that we can check if it is rendering what author inputs in the dialog?

@Subashree @ you need to use HTL context for href attribute to display link correctly.       <a href="${yourlinkedurl @ context='uri'}">Linkedin</a>   Refer to below url for more examples:   https://github.com/adobe/htl-spec/blob/master/SPECIFICATION.md#121-display-context    

@Subashree Welcome to Experience League communities and post your concern, this is a great collaboration forum to learn.   Coming to your ask, is the component a custom component or OOTB core component? If it is OOTB core component, its right now deprecated in latest versions, but below are some ref...

Thanks @lukasz-m 

Hi Team,   How to use "Subscribing to Notifications" in AEM Touch UI or cloud?   Below is the link for classic UI:- https://experienceleague.adobe.com/docs/experience-manager-65/content/sites/classic-ui/introduction/author-env-inbox.html?lang=en#subscribing-to-notifications

@armichedi so you are able to generate urls correctly as baseurl+#click me.. bit when you generate this your anchor tags are getting removed? Did you turn off your OOTB link checker? Please do.. of not it will validate link existence and remove hyperlink for invalid urls..

@emilux if all your locale pages also managed in AEM via MSM... then in your page model json.. you should pass hreflang and it's related locale urls.. and then you should read these values in your react/next js app.

@jeremylanssiers it will be hard to debug from this way.. I would like to suggest another method if you are tech savvy..  package this template and policies from your current instance via package manager, download package and unzip it.. compare policies xml and template xml with what you have in cod...

@Preston you can't do that with one single Query, you have to go with nested queries powered by api to fetch nested cf objects in between.

@adityaj which version of aem you are using? Does your page has any dependent content on any other content artifacts such as images, content fragments,  exp fragments, data pages etc..? API replication doesn't ootb replicate references while you replicate references.. Also how many pages you are try...