AMP Cache: How AMPs Content Delivery Network works

Using AMP means your website gets cached on AMP servers across the world via AMP cache partners. What does that mean? In much the same way as a typical Content Delivery Network (CDN) such as Amazon Web Services or Cloudflare serve your website from local delivery points (knowns as POPS) your website will be loaded from AMPCache, ensuring a speedy delivery no matter where your visitors are located.

So AMP Cache is similar to a standard Content Delivery network – for free?

True, although there are differences. Only valid AMP URLs are cached, to ensure performance, consistency and best standards. For these valid AMP URLs your content is automatically cached. Another feature of AMP cache is you don’t need to manually activate or even switch on the AMP CDN, the platform or site that requests your AMP valid URLs chooses the AMP cache to serve your website.

What service providers work with AMP Cache, where is my website mirrored?

AMP Cache makes use of Bing, Google and Cloudflare web servers, among others to serve your AMP valid URLs, ensuring a speedy delivery of your valuable content.

Can I turn off AMP cache, if I want me to website to load the most fresh content each time?

No, when you are using AMP you are allowing your website to be pre-rendered for platforms wishing to serve it. It’s one of the core building blocks of AMP, to ensure websites load fast.

How frequently does my cached website get re-indexed?

The Google AMP CDN ensures that each time a visitor requests an AMP document they are served the most recent cached version, alongside caching a fresh copy from origin, ready to be pre-rendered for the following visitor.

To limit the amount of load it generates for publisher sites, the Google AMP Cache considers any document fresh for at least 15 seconds, and any resource fresh for at least 1 minute.

Google’s AMP Cache also uses a”stale-while-revalidate” model, using the origin’s caching headers, Max-Age to determine caching periods. When a user makes a request for something that is stale, that request causes a new copy to be fetched, so that the next user gets fresh content.

See more information here (based on Google AMP Cache)

This all sounds great, I want to get started using AMP Cache.

Great, simple create some AMP Valid documents and that’s it!


See some related links also to various supporting documentation.