Google Working Towards Solution to AMP Cache URL Display Problem

[engine]

Google is to fix the the url problem many publishers complain about in AMP, namely to enable linked pages to appear under publishers’ URLs instead of the google.com/amp URL, and is to retain the performance and privacy benefits of AMP Cache serving. The aim is to get this through in the second half of 2018, although there's a lot to do before then, including making it available in not just Chrome, but many web browsers.

As recommended by the W3C TAG, we intend to implement a new version of AMP Cache serving based on the emerging Web Packaging standard. Based on this web standard AMP navigations from Google Search can take advantage of privacy-preserving preloading and the performance of Google’s servers, while URLs remain as the publisher intended and the primary security context of the web, the origin, remains intact. We have built a prototype based on the Chrome Browser and an experimental version of Google Search to make sure it actually does deliver on both the desired UX and performance in real use cases.

https://amphtml.wordpress.com/2018/01/09/improving-urls-for-amp-pages/amp/

W3C Distributed and syndicated content [w3.org...]
Web packaging standard [github.com...]