4 ms·

I mean that when you click a search result in Google you should go to the publisher's site, not to Google's cache of the content. It may have changed since, but

I mean that when you click a search result in Google you should go to the publisher's site, not to Google's cache of the content. It may have changed since, but that's how it was implemented originally by Google: https://www.wired.com/2016/02/googles-amp-speeding-web-changing-works/ https://www.wired.com/2016/02/googles-amp-speeding-web-chang... "…but there’s a big catch: if readers decide to share a link to an AMP page they’ve clicked on through a Google search, the link points to Google.com (for example, google.com/amp/yoursite.com/yourpage/amp), not to your site. A Google spokesperson confirms that there isn’t a way to both have your AMP-optimized appear in Google’s prioritized search listings without having that content hosted on Google’s AMP Cache servers."

bitmapbrother 9y ago
I was under the impression that the publisher could elect to use their own servers for their AMP content. Is this not possible anymore?
- callahad 9y ago
  There's a lot of doublespeak around this. 1. You can (and must) host AMP content on servers of your own choosing. 2. Google's crawlers ingest your AMP content, validate it, and re-host it in Google's AMP Cache. Bing and other folks run similar crawlers and caches. 3. Google search results will only link to AMP content on Google's own cache. So yes, you can host your content on your own servers. And you can give people direct URLs to that content. But Google users will only ever see links to the copy of your content that Google hosts; your servers never see that traffic. There is no way to opt-out and still be considered a valid AMP page.