We knew this is able to occur and on the AMP convention in Tokyo, Google introduced that publishers can be inspired to make use of their very own URLs when publishing AMP pages of their Google searches. That is powered by signed exchanges and supported by extra trendy browsers.
Right here's what it seems like:
A signed alternate appears to me like while you save an SSL certificates. On this case, you save your signed alternate with a vendor, I feel CloudFlare is among the first to do this, and in case you are verified, you might be added to a registry. Later browsers can then seek for AMP cache URLs to see in the event that they match within the registry, after which view the publisher-defined URL.
Google explains it as a signed alternate is a file format, outlined within the Internet packaging specification, that permits the browser to belief a doc as if it belongs to your origin. This lets you use proprietary cookies and storage to customise the content material and simplify the mixing of the analyzes. Your web page seems beneath your URL as an alternative of the google.com/amp URL. Google Search refers to signed exchanges when the writer, browser, and search expertise context assist it. As a writer, you need to publish the signed Trade model of the content material along with the unsigned Trade model.
I really like when outdated Googlers clarify how Google is dangerous. Right here's Pierre Far on this – see his complete feed on Twitter I'm simply going to incorporate the widespread thread:
Signed HTTP Exchanges at the moment are one factor earlier than even ending the normalization course of. It’s because Google wants it to place AMP in each internet nook that it controls (and past to a sure extent).
(Precise) Snark apart, what’s it and is it good?
– Pierre Far (@pierrefar) April 17, 2019
This announcement brought on a number of ink to circulate.
Discussion board dialogue on WebmasterWorld.