More importantly, Google might consider this cloaking, and come round your house in the middle of the night with a baseball bat.
No, they won't. Google's definition of cloaking is serving different results to Googlebot versus end-users.
For one thing, neither nor GoogleBot nor the remote quality raters will be sending Safari-specific headers for discovery/evaluation tasks, so they won't see the preview at all. For another, this falls into the (sort of) nebulous category of "cloaking designed to enhance the user experience", which is almost always kosher.
Similar examples: you can auto-detect someone's region/language/browser/etc and customize the page to fit their needs, and Google is pretty much OK with that as long as you treat Googlebot the same way.
Comments
More importantly, Google might consider this cloaking, and come round your house in the middle of the night with a baseball bat.
No, they won't. Google's definition of cloaking is serving different results to Googlebot versus end-users.
For one thing, neither nor GoogleBot nor the remote quality raters will be sending Safari-specific headers for discovery/evaluation tasks, so they won't see the preview at all. For another, this falls into the (sort of) nebulous category of "cloaking designed to enhance the user experience", which is almost always kosher.
Similar examples: you can auto-detect someone's region/language/browser/etc and customize the page to fit their needs, and Google is pretty much OK with that as long as you treat Googlebot the same way.