Hacker News new | ask | show | jobs
by moimikey 2212 days ago
Have to agree with all of the disagreements to this. The 404 is a 404 for a reason, just like 301 and 302 are different for a reason. It's not uncommon though for WordPress to do things like this, or blogs for that matter. If an author changes the title or date of their post, and the URL structure is reliant on those two pieces of data, then the URL will change. The old URL is preserved in a DB and if accessed again, 301s to the newly named resource. Others, will throw a 404 and give a cutesey Levenshtein message, "did you mean x?" at which the user can decide to go to the new resource. It's all circumstantial... It shouldn't be enforced.

Re: Google and PageRank, pretty certain they've addressed this and recognize 302 and 301s and treat them the same. Previously, this was an issue.

1 comments

Looks like the op is trying to solve a problem of broken links but has come up with a "brave choice" as they say on yes minister.

The actual solution is put in the work and redirect the old missing page to a relevant new one.

If I had a link from vogue the BBC etc back in 1996 point to a product page to want to redirect that now broken link with a 301.