At the beginning of this year, Google announced a solution for the AMP cache URL problem where Google would show and let you share the Google AMP URL instead of the publisher URL. The solution was demonstrated at I/O as an early beta of how this would look like for a publisher.
So, as an example, rather than showing the URL http://google.com/amp, Google will display the publisher’s real URL, which, in this case, foodnetwork.com. The following GIF shows us what this will look like:
As you can see above, a search is coming from Google search mobile, clicking on an AMP page, and not being served the AMP URL. Rather, they are being served a URL on the publisher’s site, foodnetwork.com.
Google explained technically how this is working. Again, this is an early beta:
The Chrome team has built enough Signed Exchange support for developers to try it out. Starting with Chrome 67 on Android — in Beta channel at the time of writing — you can enable the experimental “Signed HTTP Exchange” flag under chrome://flags to use Web Packaging’s signed exchanges. In parallel with this experimental implementation, the Chrome team has also been collecting feedback from members of standards bodies, other browser vendors, security experts, and publishers and web developers to refine and improve the Web Packaging specifications.
Last, to tie everything together, the Google Search team has implemented a version of Google Search that illustrates the end-to-end flow. When a signed exchange is available, instead of linking to an AMP page served from Google’s AMP Cache, Google Search links to a signed AMP page served from Google’s cache.
Check out the Google I/O 2018 coverage here.