I failed so far to return after I found a solution to our problem. Just in case anyone is still interested in a possible solution, I'll share my findings. There is an Angular interface called NavigationBehaviourOptions that has a property called skipLocationChange. If set to true, the navigation will not push the state to history, so there is no specification violation anymore. Documentation: https://angulardoc.com.br/api/router/NavigationBehaviorOptions So basically, we added this property as attribute in all the routerLink anchor elements. To tackle the routers initial navigation there is an ExtraOption to disable that: https://angular.io/api/router/InitialNavigation