Making FirstChildRedirect Work Cleanly with Breadcrumbs and Wayfinder

FirstChildRedirect is convenient because it lets a section container send the visitor straight to the first useful child page. But the redirect also changes the navigation story: breadcrumbs and menus may still think the container itself is the active location, while the visitor is really on the child.

That is why components such as Breadcrumbs and Wayfinder can start showing odd results once FirstChildRedirect enters the stack. The problem is not that any one component is wrong; it is that each component needs a consistent definition of the “current” page.

The fix is usually architectural rather than cosmetic. Decide whether the redirected child or the logical parent should own the active state and breadcrumb path, then make the involved components follow the same rule. Otherwise the navigation will feel unstable even if every piece works “correctly” on its own.