Enhance 404 page to facilitate broken link reporting

[Oluwatunmise-olat]

Current Behavior

The 404 page currently shows an error message and a Return to Layer5 button, but provides no way for visitors to report the broken link they landed on. As a result, unknown 404s from stale external links, cached search results, and old email campaigns go unnoticed and unresolved.

Desired Behavior

The 404 page should include a way for visitors to report the broken link they landed on, so the team can discover and fix unknown 404s that redirects and audits may not catch.

[GonuDvc]

Good catch. This is related to the RFC change in how trailing slashes are normalized. PR incoming.

[ananyaa0518]

@Oluwatunmise-olat @fitzergerald @leecalcote I’d like to work on this issue if it is still open and available.

[KatalKavya96]

@GonuDvc Are you working on this issue?

[ananyaa0518]

@saurabhraghuvanshii @leecalcote
Before implementing, I'd like to confirm the preferred reporting workflow. My initial thought is to add a "Report Broken Link" action that opens a pre-filled GitHub issue containing:

• the broken URL (window.location.href)
• the referrer (document.referrer)
• browser/user agent information

This would allow the team to capture unknown 404s without requiring additional backend infrastructure. Would a pre-filled GitHub issue be the preferred approach, or is there another reporting destination you'd prefer?

404 Page → "Report Broken Link" button → Open a pre-filled GitHub issue

[Oluwatunmise-olat]

@ananyaa0518 I think this approach is decent, can we implement to see what it feels like?

[ananyaa0518]

@Oluwatunmise-olat I've implemented the suggested approach. Could you please review it when you have a chance? Thanks!