I realize this is pretty late for your question, but I encountered this today and finally realize where Metacritic screwed up. It looks like they have an apache configuration to provide 404 errors whenever an *ico file (or most images) is requested. They likely have something like this set up:
RewriteRule (js|ico|gif|jpg|png|css|xml)$ - [R=404,L,NC]]
And they're missing a period before those extensions. Thus, anything that ends in those words, even if they're part of the game name, are returning 404s with content. Proof:
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/foojpg'
HTTP/1.1 404 Not Found
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/foojpgz'
HTTP/1.1 200 OK
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/fooxml'
HTTP/1.1 404 Not Found
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/foocss'
HTTP/1.1 404 Not Found
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/foojs'
HTTP/1.1 404 Not Found
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/fooico'
HTTP/1.1 404 Not Found
$ curl -I -H 'User-Agent: Mozilla...' 'http://www.metacritic.com/game/pc/fooicoo'
HTTP/1.1 200 OK
Which I find kind of amusing :) Anyway, mystery solved.