[null,null,[],[[["\u003cp\u003eGoogle's page experience update, focusing on user experience factors like Core Web Vitals and mobile-friendliness, will fully roll out by the end of August 2021, starting gradually in mid-June.\u003c/p\u003e\n"],["\u003cp\u003eThe update includes expanding eligibility for Top Stories to all news content meeting Google News policies, regardless of AMP format or Core Web Vitals scores.\u003c/p\u003e\n"],["\u003cp\u003eSearch Console now features a Page Experience report that combines Core Web Vitals data with other page experience signals for easier site performance evaluation.\u003c/p\u003e\n"],["\u003cp\u003eSigned Exchanges (SXG), a privacy-preserving prefetching technique, is now generally available for all web pages on Google Search, offering potential page experience improvements.\u003c/p\u003e\n"],["\u003cp\u003eInteraction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital metric on March 12, 2024.\u003c/p\u003e\n"]]],["Google's page experience ranking update will begin a gradual rollout in mid-June 2021, finishing by August. The update includes Core Web Vitals metrics (LCP, FID/INP, CLS), HTTPS, and mobile-friendliness. The Top Stories carousel will include all news content, not just AMP. Signed exchanges (SXG) are now available for all web pages, potentially improving page speed. A new Page Experience report is available in Search Console to monitor performance. An update on the removal of FID for INP is stated for March 12, 2024.\n"],null,["# More time, tools, and details on the page experience update\n\nMonday, April 19, 2021\n| It's been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Check out our updated documentation on [page experience](/search/docs/appearance/page-experience).\n\n\nLast November we [announced](/search/blog/2020/11/timing-for-page-experience) that the\npage experience ranking change will go live on Google Search this year, in what we're calling the\n\"page experience update\". To help publishers and site owners improve their page experience and\nprepare, today we're announcing a few key updates:\n\n1. [Gradual rollout starting in mid-June this year](#gradual-rollout)\n2. [Details on what will be included in the update](#details)\n3. [A new Page Experience report in Search Console](#new-report)\n4. [Support for signed exchanges for all content on Google Search](#sxg)\n\nGradual rollout starting in mid-June this year\n----------------------------------------------\n\n\nWe'll begin using page experience as part of our ranking systems beginning in mid-June 2021.\nHowever, page experience won't play its full role as part of those systems until the end of\nAugust. You can think of it as if you're adding a flavoring to a food you're preparing. Rather\nthan add the flavor all at once into the mix, we'll be slowly adding it all over this time period.\n\n\nAs we have said before, while this update is designed to highlight pages that offer great user\nexperiences, page experience remains one of many factors our systems take into account. Given\nthis, sites generally should not expect drastic changes. In addition, because we're doing this as\na gradual rollout, we will be able to monitor for any unexpected or unintended issues.\n\n\nWe hope that this adjusted roll-out schedule will help you continue to make refinements to your\nwebsite with page experience in mind. Ahead of this change, we've been gathering feedback to\nensure that we're providing helpful guidance and [answering\nquestions](https://support.google.com/webmasters/thread/104436075) that site owners may have about how to improve page experience for their users.\n\nDetails on what will be included in the update\n----------------------------------------------\n\n\nAs previously [announced](/search/blog/2020/05/evaluating-page-experience#page-experience-and-the-mobile-top-stories-feature),\nthe page experience update will consider several [page\nexperience signals](/search/docs/appearance/page-experience#signals), including the three [Core\nWeb Vitals metrics](https://web.dev/articles/vitals): [LCP](https://web.dev/articles/lcp),\n[FID](https://web.dev/articles/fid), and [CLS](https://web.dev/articles/cls)\n(as well as [Chrome's recent fix to\nCLS](https://web.dev/articles/evolving-cls)). In addition, the Top Stories carousel feature on Google Search will be updated to\ninclude all news content, as long as it meets the [Google\nNews policies](https://support.google.com/news/publisher-center/answer/6204050). This means that using the AMP format is no longer required and that\nany page, irrespective of its Core Web Vitals score or page experience status, will be eligible to\nappear in the Top Stories carousel.\n\n\nWe're also bringing similar updates to the Google News app, a key destination for users around\nthe world to get a comprehensive view of the important news of the day. As part of the page\nexperience update, we're expanding the usage of non-AMP content to power the core experience\non [news.google.com](https://news.google.com/) and in the Google News app.\n\n\nAdditionally, we will no longer show the AMP badge icon to indicate AMP content. You can expect\nthis change to come to our products as the page experience update begins to roll out in mid-June.\nWe'll continue to test other ways to help identify content with a great page experience, and we'll\nkeep you updated when there is more to share.\n\n\nIf you're looking for more details, take a look at the\n[Core Web Vitals\nand Page Experience FAQs](https://support.google.com/webmasters/thread/104436075)\nthat we published on the Search Central forums recently. If you're an AMP publisher, the AMP team\nhas built an [AMP\npage experience guide](https://blog.amp.dev/2020/10/13/meet-amps-page-experience-guide/) that offers tailored advice on how to make your AMP pages perform at\ntheir best.\n\nA new Page Experience report in Search Console\n----------------------------------------------\n\n\nTo provide you with more actionable insights, we're introducing the\n[Page Experience\nreport](https://support.google.com/webmasters/answer/10218333). This report combines the existing Core Web Vitals report with other components of\nthe page experience signals, such as HTTPS security, absence of intrusive interstitials, and mobile friendliness.\n\n\nThe Page Experience report offers valuable metrics, such as the percentage of URLs with good page\nexperience and search impressions over time, enabling you to quickly evaluate performance. You can\nalso dig into the components of page experience signal to gain additional insights on opportunities\nfor improvement.\n\n\nIn addition to launching the Page Experience report, we've also updated the\n[Search Performance\nreport](https://support.google.com/webmasters/answer/7576553) to allow you to filter pages with good page experience, which helps you keep track of how\nthese pages compare to other pages on the same site.\n\nSupport for signed exchanges for all content on Google Search\n-------------------------------------------------------------\n\n\nToday we're also announcing the general availability of [signed\nexchanges (SXG) on Google Search](/search/docs/appearance/signed-exchange) for all web pages. Google Search previously only\n[supported](https://blog.amp.dev/2019/05/22/privacy-preserving-instant-loading-for-all-web-content/)\nSXG built with the AMP framework.\n\n\nSXG allows Google Search to leverage the privacy-preserving prefetching technique in\n[compatible\nbrowsers](https://web.dev/articles/signed-exchanges#browser-compatibility), which can lead to improved page experience. This technique enables Google Search\nto load key resources of a page (HTML, JavaScript, CSS) ahead of navigation, which makes it\npossible for the browser to display pages faster.\n| **Note**: The use of SXG is not a requirement for page experience benefits, and you can consider the technology as one of the options for improving your page experience.\n\n\nNikkei, a large publication based in Japan, has been testing SXG on [Nikkei\nStyle](https://style.nikkei.com) and saw a 300ms reduction in Largest Contentful Paint (LCP). They also saw\n12% more user engagement and an improvement of 9% in pageviews per session on Android Chrome where\nthis test was implemented. To implement SXG on their site, Nikkei chose\n[`nginx-sxg-module`](https://github.com/google/nginx-sxg-module), an\nopen source extension for NGINX servers.\n\n\nFor more information on SXG tooling, see [Signed\nExchanges (SXGs)](https://web.dev/articles/signed-exchanges#tooling). For instructions on setting up SXG, see\n[How to set up signed\nexchanges using Web Packager](https://web.dev/articles/signed-exchanges-webpackager).\n\nBuilding a better web, together\n-------------------------------\n\n\nOur vision for page experience is to build a web ecosystem that users love---together. We're hard\nat work to make sure that you have the right tools and resources available before the ranking\nrollout starting in mid-June 2021.\n\n\nWe hope the updates that we shared today will make it easier for you to build great websites.\nIf you have questions or feedback, please visit our [help\nforums](https://support.google.com/webmasters/community/), check out the [FAQs](https://support.google.com/webmasters/thread/104436075)\nthat we published recently, or let us know through [Twitter](https://twitter.com/googlesearchc).\n\n\nPosted by [Jeffrey\nJose](https://twitter.com/jeffjose), Product Manager on Search\n\n*** ** * ** ***\n\nUpdates\n-------\n\n- **Update on August 4, 2021** : [Clarified that Safe Browsing isn't used as a ranking signal](/search/blog/2021/08/simplifying-the-page-experience-report). Safe Browsing systems continue to play an important role to keep users of Google Search safe, and any flags will continue to be surfaced in Search Console outside of Page Experience report.\n- **Update on June 15, 2021**: The page experience update is rolling out to all users globally. It will be complete by the end of August 2021.\n- **Update on January 31, 2024** : [Interaction to Next Paint (INP) will replace FID](https://web.dev/blog/inp-cwv-march-12) as a part of Core Web Vitals on March 12, 2024.\n- **Update on March 12, 2024** : [Interaction to Next Paint (INP) has replaced FID](https://web.dev/blog/inp-cwv-launch) as a part of Core Web Vitals."]]