In January, Google announced a resolution for the AMP cache URL position the set up Google would present and mean it is most likely you’ll presumably perchance presumably share the Google AMP URL as a replace of the writer’s URL. Google at I/O demonstrated an early beta of how this may perchance look adore for a writer.
Let’s suppose, as a replace of showing the URL http://google.com/amp, Google will present the writer’s accurate URL — in this situation, foodnetwork.com. Here’s a GIF of this in motion:
You presumably can gaze a searcher coming from Google search mobile, clicking on an AMP page and now not being served the google.com/amp URL but as a replace being served a URL on the writer’s position, foodnetwork.com.
Google explained technically how right here is working. All over again, right here is an early beta:
The Chrome crew has built adequate Signed Change give a desire to for developers to examine out it out. Initiating with Chrome sixty seven on Android — in Beta channel at the time of writing — it is most likely you’ll presumably perchance presumably allow the experimental “Signed HTTP Change” flag below chrome://flags to make expend of Net Packaging’s signed exchanges. In parallel with this experimental implementation, the Chrome crew has also been collecting ideas from contributors of requirements bodies, other browser vendors, security consultants, and publishers and web developers to refine and enhance the Net Packaging specifications.
Remaining, to tie all the pieces together, the Google Search crew has utilized a version of Google Search that illustrates the discontinue-to-discontinue float. When a signed alternate is on hand, as a replace 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.
Be conscious all of our Google I/O 2018 protection right here.