Thanks Carson but that wasn't the question.

The question was how to check the cache.

I think google has stopped responding to cache requests on hashbang pages all together.

See here... **I'm just playing with random urls and don't see google cache 404'ing as it should **http://recordit.co/XBlo3U2A73

You can really put anything there it won't work.

Thanks a lot, Matt.

I'm curious.. how did you exactly find the version with the utm codes that are being cached?

What you're saying make sense and our urls are setup like this but we still don't see just the homepage come up when looking up the google cache with the esc fragment version

http://webcache.googleusercontent.com/search?q=cache:https://placeit.net/?escaped_fragment=/stages/samsung-galaxy-note-friends-park

https://placeit.net/?escaped_fragment=/stages/samsung-galaxy-note-friends-park

homepage - http://webcache.googleusercontent.com/search?q=cache:https://placeit.net/?escaped_fragment=

So we use http://webcache.googleusercontent.com/search?q=cache:x.com/#!/hashbangpage to check what googlebot has cached but when we try to use this method for hashbang pages, we get the x.com's cache... not x.com/#!/hashbangpage

That actually makes sense because the hashbang is part of the homepage in that case so I get why the cache returns back the homepage.

My question is - how can you actually look up the cache for hashbang page?