4 ms·

Cloudflare hosts their own AMP Cache. It seems reasonable they'd adopt this as well.

AlexCoventry 7y ago
If you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? If AMP is federated, that's a lot less disturbing to me than my first impression.
- SquareWheel 7y ago
  I don't know the answer to those questions, but I'd be curious to know as well. Bing also hosts an AMP Cache if that's of interest to you.
- ocdtrekkie 7y ago
  Google can only serve data from Google's AMP cache. Bing can only serve data from Bing's AMP cache. So you can't, say, pick an AMP provider, your website gets hoovered up by each individual AMP cache and served to users coming from their respective networks. In short, only being in Google's AMP cache gets you good rankings on Google Search.
- lern_too_spel 7y ago
  > If AMP is federated, that's a lot less disturbing to me than my first impression. AMP is federated. Anybody who wants instant loading of AMP pages linked from their own pages can run their own AMP cache, as Bing and Baidu (among others) do. > If you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? Bing and Baidu running their own AMP caches doesn't affect their Google ranking. Why would it?
- gregable 7y ago
  Let me see if I can explain this a little better. Anyone can cache a signed exchange from anyone else. So, for example if you went and fetched a signed exchange from https://amppackageexample.com/ https://amppackageexample.com/ (or any other site that supports one, this is just an example), you could then serve that from your own server, more or less just like any other file (the less is that you need to set the right Content-Type header, but it otherwise works just like serving an image or a zip file). Then, if a user visited the URL on your site https://yoursite.com/cached-copy-of-amppackageexample.com/ https://yoursite.com/cached-copy-of-amppackageexample.com/ then the browser would display https://amppackageexample.com/ https://amppackageexample.com/ in the URL bar, as though that URL had 301 redirected, but without the extra network fetch. Google search does exactly this, just loading a cached copy of the Signed Exchange, and any other cache (or even any website) can do the same. So, if you publish a signed exchange, you are allowing all caches to do this, not just a selected cache. However, since the document is signed, absolutely no caches can modify the document or the browser will reject it and error handle (typically just making an actual redirect to your domain). I hope that helps to understand.
  - AlexCoventry 7y ago
    Yes, thanks for clarifying.
  - SquareWheel 7y ago
    Thanks for the explanation!

If you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? If AMP is federated, that's a lot less disturbing to me than my first impression.

SquareWheel 7y ago
I don't know the answer to those questions, but I'd be curious to know as well. Bing also hosts an AMP Cache if that's of interest to you.
ocdtrekkie 7y ago
Google can only serve data from Google's AMP cache. Bing can only serve data from Bing's AMP cache. So you can't, say, pick an AMP provider, your website gets hoovered up by each individual AMP cache and served to users coming from their respective networks. In short, only being in Google's AMP cache gets you good rankings on Google Search.
lern_too_spel 7y ago
> If AMP is federated, that's a lot less disturbing to me than my first impression. AMP is federated. Anybody who wants instant loading of AMP pages linked from their own pages can run their own AMP cache, as Bing and Baidu (among others) do. > If you use a different AMP cache than Google's, does it affect your search ranking/carousel positioning with them? Bing and Baidu running their own AMP caches doesn't affect their Google ranking. Why would it?
gregable 7y ago
Let me see if I can explain this a little better. Anyone can cache a signed exchange from anyone else. So, for example if you went and fetched a signed exchange from https://amppackageexample.com/ https://amppackageexample.com/ (or any other site that supports one, this is just an example), you could then serve that from your own server, more or less just like any other file (the less is that you need to set the right Content-Type header, but it otherwise works just like serving an image or a zip file). Then, if a user visited the URL on your site https://yoursite.com/cached-copy-of-amppackageexample.com/ https://yoursite.com/cached-copy-of-amppackageexample.com/ then the browser would display https://amppackageexample.com/ https://amppackageexample.com/ in the URL bar, as though that URL had 301 redirected, but without the extra network fetch. Google search does exactly this, just loading a cached copy of the Signed Exchange, and any other cache (or even any website) can do the same. So, if you publish a signed exchange, you are allowing all caches to do this, not just a selected cache. However, since the document is signed, absolutely no caches can modify the document or the browser will reject it and error handle (typically just making an actual redirect to your domain). I hope that helps to understand.
- AlexCoventry 7y ago
  Yes, thanks for clarifying.
- SquareWheel 7y ago
  Thanks for the explanation!