{"id":237,"date":"2018-01-25T14:22:11","date_gmt":"2018-01-25T14:22:11","guid":{"rendered":"http:\/\/www.suvaance.com\/microblog\/?p=237"},"modified":"2019-03-18T12:32:42","modified_gmt":"2019-03-18T12:32:42","slug":"from-where-data-is-loaded-when-a-new-amp-link-is-clicked","status":"publish","type":"post","link":"https:\/\/www.suvaance.com\/microblog\/from-where-data-is-loaded-when-a-new-amp-link-is-clicked\/","title":{"rendered":"From Where Data Is Loaded when a New AMP Link Is Clicked?"},"content":{"rendered":"

We all have come across the term \u201cAMP<\/strong>\u201d which helps to create mobile optimized content to provide a fast user experience. But, do you know when a new AMP link clicked, from where data is loaded?<\/p>\n

During a recent discussion on Twitter, John Mueller<\/strong> said, when a new AMP link is clicked, Google actually loads it from its AMP Cache<\/strong> and then requests the data from website\u2019s server<\/strong> to update the cache for upcoming users.<\/p>\n

\"John<\/a><\/p>\n

How It Works<\/h2>\n

Usually Google fetches a document directly from the website\u2019s server when a user clicks the link of that document appeared in search results. But when a user clicks on a new AMP document, that document gets fetched from Google AMP Cache<\/a>. Then the cache requests updated data from the website\u2019s server automatically to provide fresh data to the next users. One major benefits of this model structure is AMP documents get updated automatically.<\/p>\n

The Google AMP cache follows a “stale-while-revalidate<\/strong>” model. This model uses some original caching headers like max-age, which helps it to decide whether a resource or document is stale. So, whenever any document or resource that is stale being requested by users, a new copy of that gets fetched to serve the fresh content to upcoming users.<\/p>\n