Wednesday, August 4, 2021

The
Page Experience report
in Search Console
launched earlier this year to
offer publishers and site owners a way to quickly understand how their sites fare against the page
experience signals. Today, we’re launching a new version that simplifies the report by removing
the Safe Browsing and Ad Experience widgets from the Page Experience report, and fixes on how
missing data is handled.

As a reminder, the page experience ranking update started
slowly rolling out
on June 15, 2021 and the rollout will be completed by August 31, 2021.

Safe Browsing systems at Google
are designed to keep users safe on the internet. Sometimes sites fall victim to third-party
hijacking, which can cause Safe Browsing warnings to be surfaced. We recognize that these issues
aren’t always within the control of site owners, which is why we’re clarifying that Safe Browsing
isn’t used as a ranking signal and won’t feature in the Page Experience report. Any Safe Browsing
flags will continue to be surfaced in the Search Console outside of the Page Experience report.

Similarly, we’re removing the
Ad Experience
widget to avoid surfacing the same information on two parts of Search Console. The Ad Experience
report will continue to be available as a standalone tool that you can use to review the status of
your site and identify ad experiences that violate the Better Ads Standards. To be clear, the Ad
Experience report was never used as a factor for page experience, so this change won’t affect your
site’s page experience status.

Updated graphic of the factors that make up page experience signal, namely Loading (LCP), Interactivity (FID), Visual Stability (CLS), Mobile Friendliness, HTTPS and No Intrusive Interstitials
Updated graphic of the factors that make up page experience signal, namely Loading (LCP),
Interactivity (FID), Visual Stability (CLS), Mobile Friendliness, HTTPS and No Intrusive
Interstitials.

Other improvements to the report

Along with the two updates mentioned above, we’re rolling out more improvements to how the report
handles missing data:

  • Added a “No recent data” banner to the
    Core Web Vitals report
    and
    Page Experience report.
  • Fixed a bug that caused the report to show “Failing HTTPS” when Core Web Vitals data was
    missing.
  • Rephrased the empty state text in the Page Experience report and Core Web Vitals report.

We hope the improvements make it easier to use the Page Experience report, and help you build
websites with great page experience.

If you have questions or feedback, please visit our
help forums or let
us know through Twitter.





Source link

By Ryan Bullet

I am interested in SEO and IT, launching new projects and administering a webmasters forum.

Leave a Reply

Your email address will not be published. Required fields are marked *