For example, Google Search crawls content for any identified and valid AMP pages, the content is added to the Google AMP Cache.Ĭache URL request: Platforms can specifically request an AMP page by using the AMP Cache URL format. Platform discovery: Platforms discover your AMP content via the or tag and cache the content. There are a few ways that your AMP page can end up in an AMP Cache: Mobile apps can link to cached AMP content via the URL (see Google's AMP URL API) or by cross-origin XHRs in Progressive Web Apps (learn more in Embed & use AMP as a data source).īy using the AMP format, you are making your content available to be cached by AMP Caches. Who requests cached AMP pages?Ĭached AMP pages are accessed by platforms (like Google Search, Google News, and Bing) and mobile apps. This makes the document technically invalid AMP, while not impacting the functionality of the document. Should you desire not to have your document cached, one option is to remove the amp attribute from the HTML tag. Publishing a valid AMP document automatically opts it into cache delivery. Can I opt out of caching?Ĭaching is a core part of the AMP ecosystem. To learn about the strict guidelines for creating AMP Caches, see the AMP Cache Guidelines. However, this model allows platforms to provide their users with predictable load performance and among other things allows them to ensure required security and privacy invariants during AMP’s pre-rendering phase. This is an inversion of the typical model where content delivery is the responsibility of the publisher. How do I choose an AMP Cache?Īs a publisher, you don't choose an AMP Cache, it's actually the platform that links to your content that chooses the AMP Cache (if any) to use. To learn about creating AMP Caches, see the AMP Cache Guidelines. Watch this video to learn why AMP Caches exist.Ĭurrently, there are two AMP Cache providers:ĪMP is an open ecosystem and the AMP Project actively encourages the development of more AMP Caches. Learn more about AMP Caches in the YouTube video below, or in the Why AMP Caches Exist blog post. “As the only provider currently enabling this new solution, our global scale will allow publishers everywhere to benefit from a faster and more brand-aware mobile experience for their content.AMP email documents are exempt from the AMP cache. “AMP has been a great solution to improve the performance of the internet and we were eager to work with the AMP Project to help eliminate one of AMP’s biggest issues - that it wasn’t served from a publisher’s perspective,” said Matthew Prince, co-founder and CEO of Cloudflare. For the time being, that makes Cloudflare the only CDN that supports this feature, though others will surely follow. With this, the company will automatically sign every AMP page it sends to the Google AMP cache. It’ll take a bit before it will roll out to all users, who can then enable it with a single click. To launch this new feature, Google also partnered with Cloudflare, which launched its AMP Real URL feature today. Using their own URL also makes it easier to get analytics, and the standard grey bar that sits on top of AMP pages and shows the site you are on now isn’t necessary anymore because the name will be in the URL bar. For now, though, only Chrome supports the core features behind this service, but other browsers will likely add support soon, too.įor publishers, this is a pretty big deal, given that their domain name is a core part of their brand identity. Quite a few publishers already do this, given that Google started alerting publishers of this change in November 2018. Publishers will have to do a bit of extra work, and publish both signed and un-signed versions of their stories. By default, a browser should reject scripts in a web page that try to access data that doesn’t come from the same origin. Last January, the company announced that it was embarking on a multi-month effort to load AMP pages from the Google AMP cache without displaying the Google URL.Īt the core of this effort was the new Web Packaging standard, which uses signed exchanges with digital signatures to let the browser trust a document as if it belongs to a publisher’s origin. This move has been in the making for well over a year. Starting today, when you use Google Search and click on an AMP link, the browser will display the publisher’s real URLs instead of an “http///amp” link. One AMP quirk that publisher’s definitely never liked is about to go away, though. Publishers don’t always love Google’s AMP pages, but readers surely appreciate their speed, and while publishers are loath to give Google more power, virtually every major site now supports this format.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |