Best practices for /[slug] and /hard-coded routes

In my application I have /[slug] for all of our articles. However, I also have some hardcoded routes that live basically on the same path. For example, /privacy-policy, /contact, /about, /onboarding, /sign-up, /sign-in. I have noticed in Sentry that I am getting errors when folks visit some of those URLs that /:slug failed to load.

Is there anything that I can change/update to avoid something like this? I honestly don’t know if it’s impacting the user at all.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.