3 ms·
> All content is easily indexed by Google and ready to serve from its AMP cache If the content is encrypted and can only be decrypted by the user with the righ
by diggan 7y ago
> All content is easily indexed by Google and ready to serve from its AMP cache
If the content is encrypted and can only be decrypted by the user with the right keys, how does Google get to decrypt it? They have a master-key everyone needs to use in order for this to work?
Took a look at https://amp.dev/documentation/guides-and-tutorials/develop/monetization/content_encryption https://amp.dev/documentation/guides-and-tutorials/develop/m... which is linked as well, but got no answer.
I seem to remember something around that Google penalized websites who showed different content between Googlebot (the indexer) and a normal website visitor. Does this move go directly against that, when the premium content would be indexed but not be able to be viewed by the visitor?
- marcus_holmes 7y agofrom the link you shared: "You are required to encrypt the document key with the local environment and Google’s public key. Including Google’s public key allows Google AMP cache to serve your document." So you have to encrypt the document key with their public key so they can decrypt at will. No master key required.
- diggan 7y agoThanks! I somehow missed that. So there is indeed a master key that Google holds, the private key that the public key matches with is that master key. So does that mean that Google will no longer penalize websites that show different content for Googlebot vs normal visitors, or is this "AMP client side encryption" a exception to this rule?
- fastball 7y agoThe same content is being served to Googlebot and users with this solution... unlike before.