Welcome to the Q&A Forum

Our site had a huge drop in bounce rate in one day (went from 10% to 3%) and it has stayed that way.

What could cause this?

P4bYpNF.png

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 Oleg.

Couldn't it help (even if a little) with ranking if the term that is in the meta description (the long one) wouldn't have been there otherwise?

I've seen all the length recommendations and understand the reasoning is that they will be cut off when you search the time but I've also noticed that Google will "move" the meta description if the search term that the user is using is in the cached version of the page. S

I have a case where Google is indexing the pages but not caching the content (at least not yet). So we see the meta description just fine on the Google results but we can't see the content cache when checking the Google cached version.

**My question is: **In this case, why would it be a bad idea to make a slightly lengthier (but still relevant) meta description with the intent that one of the terms in that description could match the user's search terms and the description would "move" to highlight that term in the results.

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?

Thanks Ryan. Is there a place where this is actually confirmed by Google (it having no effect)?

Google has been sending emails out about usability errors. Do they have an effect on the rankings for desktop search results?