Google’s new solutions for the AMP — URL issue are on the way
Since its announcement, the AMP pages showed some issues around URL-generated cache; it was in January 2018 when Google announced a solution for this problem, allowing the page to share the Google AMP URL instead of the publisher’s one.
News around Google I/O
For relief of many developers and publishers, in the recent Google I/O we got a beta version of how this would look for us (and you, of course).
Otherwise said, employing this solution would deliver in showing the publisher’s real URL instead of “http://google.com/amp” (this last URL is just stated for example purposes).
At the I/O 2018, the people at Google explained this process technically, specifying (again) that the solution is still in beta version. Some of the major points or implementations regard the following concepts:
- The Chrome team built a variety of Signed Exchange support for developers, starting with Chrome 67 on Android; you can enable the experimental “Signed HTTP Exchange” flag under chrome::/flags to use Web Packaging’s signed exchanges.
- Also, the Chrome team has been collecting feedback from different developers, other browser vendors, security experts and publishers to improve the Web Packaging specifications.
- At last -but not least-, the Search team implemented a new version of Google Search that illustrates the flow completely; that means that when a signed exchange is available, instead of linking to an AMP page served from the Google AMP cache, it links to a signed AMP page served from the cache at Google.
All these solutions are sure to help out brands and organizations in the deployment of different AMP products, such as AMP landing pages; of course, our people at Moõse and the VIKO Group are focused on all the changes that will be arriving for this URL issue and all news regarding the AMP multiverse.
