I have a page in an MVC asp.net project that has gone away. We've renamed the URL to something entirely different.
The problem is other sites still link to that particular url.
We could blank out the html for the url in question and do a meta refresh or a javascript script call to take them to the new page, but that doesn't really fit our model.
I could add another route, and let asp.net take care of it, but hardcoding routes for urls to be forwarded seems like bad practice. I could also edit the asp.net page and use a response.redirect, but there's no real page in existence since this is a light CMS...
How SHOULD I redirect a user from a url landing page to a different landing page using best practice? We don't need the user to see a "this page has moved" or anything like that as part of the requirement.