Google launches real URLs solution for AMP pages

a minute read

Google solved a problem with displaying the URL of publishers using the AMP format. Now users can see the real URL ( in the search results in the Chrome browser, not the Google AMP URL (

To do this, Google has implemented Chrome’s support for the new Web standard Signed HTTP Exchanges , which allows mobile browsers to display real domains, not Google AMP URLs. Support for this standard will also be added to Microsoft Edge and other browsers in the near future.

Google worked on this solution for over a year. The company opened access to the preview version of the technology in November.

To take advantage of this solution, publishers need to embed signed exchanges into their infrastructure, following the guidance of Serve AMP using Signed Exchanges .

Google also collaborates with Cloudflare, which launched the AMP Real URL function, which can be enabled in one click. As a result, the platform will automatically sign every AMP page sent to Google AMP Cache. Cloudflare is currently the only CDN supporting this feature.

Recall that Google for the first time demonstrated a new solution for AMP at the Google I / O conference in May, and for the first time it became known in January 2018.

Facebook Twitter LinkedIn Telegram Pocket

Related Posts:

Google announced that it almost solved the problem with displaying URLs in the AMP search results. They currently display Google URLs, not publishers that come from AMP Cache. However, later this year the situation will change, and AMP Cache will begin to prov...
Google changed the design of the AMP pages when viewed in search results. Now users can see direct links to publisher sites and share them. Google makes a copy of the AMP content and displays it from its own servers. The company claims that it allows you to sp...
Publishers who use AMP technology have long been concerned about the fact that their own domains are not displayed in the URL when users navigate AMP results from Google search results. The Google AMP team has worked on this problem for many months and finally...