AMP specifications allow for other cache servers, of which CloudFlare[0] has recently implemented one. You could implement your own if you like. AMP also speci

AMP specifications allow for other cache servers, of which CloudFlare[0] has recently implemented one. You could implement your own if you like. AMP also specifies that the canonical page URL should be used when sharing, though the cached URL is currently what's shown in the browser. Their last developer update[1] said they're working to address this, however for all relevant purposes Google's own systems already currently consider AMP traffic and results to be attributed to the original source. [0] http://www.businessinsider.com/cloudflare-adopts-google-amp-2017-1 http://www.businessinsider.com/cloudflare-adopts-google-amp-... [1] https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exist/ https://amphtml.wordpress.com/2017/01/13/why-amp-caches-exis... > Google amends its cached AMP search results with Schema.org and OpenGraph metadata, so posting the link to any platform that honors these should result in the canonical URL being shared.