# How about Discourse Support Google AMP?

**URL:** <https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697>\
**Category:** Feature\
**Created:** [2 בדצמבר,‏ 2016,‏ 4:42pm UTC](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697 "2016-12-02T16:42:57Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![rrit](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@rrit](https://meta.discourse.org/u/rrit)\
**Post date:** [13 במרץ,‏ 2022,‏ 8:24pm UTC](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697/39 "2022-03-13T20:24:48Z")

</div>

There is another nice “new” technologie - also working for non-amp pages:  
[Signed exchanges (SXG)](https://developers.google.com/search/docs/advanced/experience/signed-exchange?hl=en)

> [@](#):
>
> [Signed exchanges](https://web.dev/signed-exchanges/) (SXG) allow Google Search to prefetch your content while preserving the user’s privacy. In practice, this means that both AMP and non-AMP results shown on Google Search may prefetch a few key resources (such as HTML, JavaScript, CSS, images, or fonts) in a privacy-preserving manner, if the associated website supports SXG.
> 
> When the user ultimately clicks the result, the web page starts rendering much sooner since key resources are already available, leading to a better user experience. This could mean a lower [Largest Contentful Paint (LCP)](https://web.dev/lcp/) score for your content. While Google Search doesn’t consider use of SXG as a direct factor in ranking, the lower LCP may affect ranking because [page experience will be a ranking factor](https://developers.google.com/search/docs/advanced/experience/page-experience).

---

_[View the full topic](https://meta.discourse.org/t/how-about-discourse-support-google-amp/53697)._