Update AMP Content

The steps described below can be used to update or remove content from the Google AMP Cache.

The easiest way to update the version of any AMP document stored in the Google AMP Cache is to make a new request to access that document using the AMP Cache URL format. The Google AMP Cache automatically requests the latest version of the AMP document from its origin (provided the previous version of the document has been in the cache for longer than its caching headers allow) and serves the updated version to the next user.

For urgent removals, you may not want to wait for the cached version to expire. In these urgent cases, remove content from your server first and then use the "update-ping" mechanism to reflect that removal in the Google AMP Cache.

Update ping format

The "update-ping" mechanism is a GET request. The format of the update ping for this AMP Cache URL, https://cdn.ampproject.org/c/s/ampbyexample.com, is as follows:


Remove AMP content

Use the "update-ping" mechanism to permanently remove content from the Google AMP Cache after the content has been removed from its origin. For example, to purge content formerly served at https://cdn.ampproject.org/i/s/example.com/favicon.ico, send an update ping request to:


Cached content that no longer exists will eventually get removed from the cache; it's just faster to use "update-ping". Using the cache update ping usually reduces the maximum removal latency to:

End-to-end latency = Z + 4 minutes, where Z = the latency of the publisher (if any).

An update ping request to purge content fetched from the origin with HTTPS does not purge content fetched with HTTP. For example, https://cdn.ampproject.org/update-ping/i/s/example.com/favicon.ico will only purge the content served from https://cdn.ampproject.org/i/s/example.com/favicon.ico, not from https://cdn.ampproject.org/i/example.com/favicon.ico (note the lack of /s/ in the latter).