New slugs are dangerous

Graeme_Grant

Last night, when searching for my old articles, I hit "404 Page Not Found".

For example: https://www.codeproject.com/Articles/5365754/Blazing-Mvvm-Blazor-Server-WebAssembly-Hybrid-usin is now https://codeproject.com/articles/Blazing-Mvvm-Blazor-Server-WebAssembly-Hybrid-usin

I have to fix all of my own broken links, but also, which is far worse for CP, is, from a SEO perspective, this is suicide, breaking thousands of inbound links built up over the decades.

I can't recommend highly enough to quickly have 302 redirects for the old URLs!

Richard Deeming

Also from an SEO perspective, the article page title is simply "Code Project". It should at least have the article title in it!

Graeme_Grant

@Richard-Deeming said in New slugs are dangerous:

Also from an SEO perspective, the article page title is simply "Code Project". It should at least have the article title in it!

Agreed. Though killing all the original slugs with decades of backlinks and trust was thrown out with the bathwater... a bigger problem IMHO. A good way to kill CP.

Attributing articles to the wrong authors is also big, but the slugs are more important. Page titles are important too, but #3.

dlymand2

Our dev team has fixed this and will deploying it in the next hour or two. Sorry for the problems in the last 24 hours.

Graeme_Grant

@dlymand2 said in New slugs are dangerous:

Our dev team has fixed this and will deploying it in the next hour or two. Sorry for the problems in the last 24 hours.

Looking forward to seeing the update.

Graeme_Grant

@dlymand2 said in New slugs are dangerous:

Our dev team has fixed this and will deploying it in the next hour or two. Sorry for the problems in the last 24 hours.

I've done a quick check and the 302s appear to be working onw.