User blog comment:Kirkburn/Technical Update: January 27, 2015/@comment-3183960-20150128123305/@comment-11733175-20150201004448

The reason I feel listing redirects in search suggestions is because redirects can be used to account for spelling mistakes. A particularly annoying example we had on RuneScape Wiki was "KING BLACK DRAGOB" as a suggestion for "King" which looked ridiculous as a possible suggestion. Whilst it's not such an issue if redirects are limited to slang names or aliases, other uses, like translations, will only confuse users searching for something they've actually spelt correctly in the first place.

In the editor it's less of an issue, but I don't see the problem with using the direct link instead of the redirect especially as it cuts down on potential double redirects when moving pages.

As it happens it should be relatively simple to filter redirects based on if they contain an id, it's just a case of looking up the rd_fragment field in the redirect database table.

From my personal point of view and search usage, I think not converting redirects with ids to the target page is the better option. I hope it's reasonable to assume that redirects with ids are spelt correctly and thus avoid the original issue I outlined above. If that's true, then the redirect's title is much more helpful to the user as a suggestion than the redirects target page, irrespective of whether the id is displayed or not.