My Blog


Displayed during Google I/O: Publisher’s URL appears in AMP cache URLs rather than the Google AMP URL.

In January, Google introduced a solution for the AMP cache URL trouble wherein Google could show and allow you to share the Google AMP URL as opposed to the writer’s URL. Google at I/O validated an early beta of how this would appear to be for a publisher.


For instance, in place of showing the URL https://google.Com/amp, Google will display the writer’s actual URL — in this situation, foodnetwork.Com. Here is a GIF of this in motion:
You can see a searcher coming from Google seek cell, clicking on an AMP page and not being served the google.Com/amp URL but as an alternative being served a URL on the writer’s web site, foodnetwork.Com.


Google defined technically how this is operating. Again, this is an early beta:


The Chrome team has built sufficient Signed Exchange assist for builders to attempt it out. Starting with Chrome 67 on Android — in Beta channel at the time of writing — you could enable the experimental “Signed HTTP Exchange” flag under chrome://flags to apply Web Packaging’s signed exchanges. In parallel with this experimental implementation, the Chrome crew has also been gathering feedback from members of requirements our bodies, other browser carriers, protection specialists, and publishers and net developers to refine and enhance the Web Packaging specifications.


Last, to tie the whole thing collectively, the Google Search group has implemented a model of Google Search that illustrates the stop-to-cease float. When a signed change is available, in preference to linking to an AMP web page served from Google’s AMP Cache, Google Search hyperlinks to a signed AMP web page served from Google’s cache.


Follow all of our Google I/O 2018 insurance right here.


Categorized as Blog

Leave a comment

Your email address will not be published. Required fields are marked *