Connect with us


Core Web Vitals Might Include Noindexed Pages via @martinibuster



Webmaster Trends Analyst John Mueller answered questions about Core Web Vitals and how the scores are calculated. He also discussed the possibility of noindexed pages being be used as part of the Core Web Vitals calculation in the new ranking signal that is coming soon.

Core Web Vitals

The Core Web Vitals are user experience metrics. They are a group of metrics that Google chose to represent how well a web page downloads and presents a good user experience for site visitors.

There are three Core Web Vitals metrics:

  1. Largest Contentful Paint (LCP)
    How fast a web page is perceived to load
  2. First Input Delay (FID)
    How soon a visitor can interact with a web page
  3. Cumulative Layout Shift (CLS)
    How stable web page elements (like buttons, text and images) are while the page is downloading, without shifting about.

Those three metrics are scheduled to become ranking factors sometime in 2021. That is why many publishers and SEOs are concerned about how Google calculates the core web vitals score because, as a ranking factor, there is a possibility that it may impact rankings in certain scenarios.


Continue Reading Below

Screenshot of Google’s John Mueller Discussing Noindexed Pages and Core Web Vitals

Screenshot of John Mueller discussing core web vitalsScreenshot of Google’s John Mueller discussing why noindexed pages might be used to calculate Core Web Vitals scoreScreenshot of John Mueller discussing core web vitals

Lab Data and Field Data

Knowing what lab data and field data are is key to understanding John Mueller’s answer.

Lab data, in reference to web vitals scores is an estimate of the score. The lab data scores are generated in a simulated environment.

The goal with lab data is to give a publisher an idea of what could be problematic.



Continue Reading Below

Field Data is a score based on actual site visitors under real-world conditions.

It’s the field data that Google will be using to calculate the associated ranking signal score.

Publishers concerned about their ability to rank are concerned with how field data is calculated.

  • Does Google use actual page score?
  • Does Google use an average of several pages to calculate the core web vitals score?
See also  5 HTTP Security Headers You Need To Know For SEO

Noindex and Core Web Vitals

Noindex is a signal that a publisher can use to tell Google not to include a web page in Google’s search results.

According to Google’s official documentation:

“You can prevent a page from appearing in Google Search by including a noindex meta tag in the page’s HTML code, or by returning a noindex header in the HTTP request.

When Googlebot next crawls that page and sees the tag or header, Googlebot will drop that page entirely from Google Search results, regardless of whether other sites link to it.”

The question asked of Google’s John Mueller was whether a noindexed page will be used to calculate the web vitals score.

What made this question important was that the publisher was blocking these pages because they were very slow and the publisher did not want those pages used as part of the calculation of the core web vitals score.


This is the first question:

“With regards to core web vitals, field data is going to be the one to pay attention to, correct (in terms of ranking signals)?”

John Mueller’s response:

“Yes, yes, it’s the field data.”

Google May Aggregate Pages for Core Web Vitals

In the follow up question Mueller reveals how Google may in some cases calculate the core web vitals score as an average of multiple pages.

This is the question:

“When this becomes a ranking signal… is it going to be page level or domain level?”

Mueller answered:

“…What happens with the field data is we don’t have data points for every page.

So we, for the most part, we need to have kind of groupings of individual pages.

And depending on the amount of data that we have, that can be a grouping of the whole website (kind of the domain).

…I think in the Chrome User Experience Report they use the origin which would be the subdomain and the protocol there.


So that would be kind of the overarching kind of grouping.

And if we have more data for individual parts of a website then we’ll try to use that.

And I believe that’s something you also see in search console where we’ll show like one URL and say… there’s so many other pages that are associated with that. And that’s kind of the grouping that we would use there.”


Continue Reading Below

Mueller is clear that the core web vitals score may not always be calculated on a page by page basis.

Will Slow Pages Affect Overall CWV Score?

The person asking the follow up question then related that they have a set of pages that are slow and are no-indexed and asked if those pages can impact the core web vitals score.

“We gave this set of pages that they are slow. And these we have a noindex on them… they are very slow. And that’s why we don’t want it to be accounted for.”

Mueller responded:


“I don’t know for sure how we would do things with a noindex there. But it’s not something you can easily determine ahead of time.

Like, will we see this as one website or will we see it as different groupings there.

Sometimes with the Chrome User Experience Report data you can see like, Does Google have data points for those noindex pages? Does Google have data points for the other pages there?

And then you can kind of figure out like okay, it can recognize that there is separate kinds of pages and can treat them individually.

And if that’s the case, then I don’t see a problem with that.

If it’s a smaller website where we just don’t have a lot of signals for the website then those noindex pages could be playing a role there as well.

So I’m not 100% sure but my understanding is that in the Chrome User Experience Report data we do include all kinds of pages that users access.

So there’s no specific kind of, will this page be indexed like this or not check that happens there because the indexability is sometimes quite complex with regards to canonicals and all of that.

So it’s not trivial to determine… on the Chrome side if this page will be indexed or not.


It might be the case that if a page has a clear noindex then even in Chrome we would be able to recognize that. But I’m not 100% sure if we actually do that.

I would also check the Chrome User Experience Report data. I think you can download data into BigQuery and you can play with that a little bit and figure out how is that happening for other sites, for similar sites that kind of fall in the same category as the site that you’re working on.”


Continue Reading Below

Pages that Users Access

While Mueller hedged by saying that he wasn’t 100% certain if Google used noindexed pages, he did affirm that the Chrome User Experience Report included all kinds of pages (which in this context presumably includes noindexed pages).

The reason they are included is because, according to Mueller:

“…we do include all kinds of pages that users access.”

The logic behind using noindexed pages can be that because users can access a page then it is going to be measured. The reason is because a user will experience the noindexed pages, regardless if those web pages are blocked to Google.

Though Mueller wasn’t 100% certain, until there is further clarification, it may be prudent to assume that noindexed pages will be measured as part of the core web vitals ranking score.



Watch the Office Hours Hangout

[embedded content]


Google December Product Reviews Update Affects More Than English Language Sites? via @sejournal, @martinibuster



Google’s Product Reviews update was announced to be rolling out to the English language. No mention was made as to if or when it would roll out to other languages. Mueller answered a question as to whether it is rolling out to other languages.

Google December 2021 Product Reviews Update

On December 1, 2021, Google announced on Twitter that a Product Review update would be rolling out that would focus on English language web pages.

The focus of the update was for improving the quality of reviews shown in Google search, specifically targeting review sites.

A Googler tweeted a description of the kinds of sites that would be targeted for demotion in the search rankings:

“Mainly relevant to sites that post articles reviewing products.

Think of sites like “best TVs under $200″.com.

Goal is to improve the quality and usefulness of reviews we show users.”



Continue Reading Below

Google also published a blog post with more guidance on the product review update that introduced two new best practices that Google’s algorithm would be looking for.

The first best practice was a requirement of evidence that a product was actually handled and reviewed.

The second best practice was to provide links to more than one place that a user could purchase the product.

The Twitter announcement stated that it was rolling out to English language websites. The blog post did not mention what languages it was rolling out to nor did the blog post specify that the product review update was limited to the English language.

Google’s Mueller Thinking About Product Reviews Update

Screenshot of Google's John Mueller trying to recall if December Product Review Update affects more than the English language

Screenshot of Google's John Mueller trying to recall if December Product Review Update affects more than the English language

Product Review Update Targets More Languages?

The person asking the question was rightly under the impression that the product review update only affected English language search results.



Continue Reading Below

But he asserted that he was seeing search volatility in the German language that appears to be related to Google’s December 2021 Product Review Update.

This is his question:

“I was seeing some movements in German search as well.

So I was wondering if there could also be an effect on websites in other languages by this product reviews update… because we had lots of movement and volatility in the last weeks.

…My question is, is it possible that the product reviews update affects other sites as well?”

John Mueller answered:

“I don’t know… like other languages?

My assumption was this was global and and across all languages.

But I don’t know what we announced in the blog post specifically.


But usually we try to push the engineering team to make a decision on that so that we can document it properly in the blog post.

I don’t know if that happened with the product reviews update. I don’t recall the complete blog post.

But it’s… from my point of view it seems like something that we could be doing in multiple languages and wouldn’t be tied to English.

And even if it were English initially, it feels like something that is relevant across the board, and we should try to find ways to roll that out to other languages over time as well.

So I’m not particularly surprised that you see changes in Germany.

But I also don’t know what we actually announced with regards to the locations and languages that are involved.”

Does Product Reviews Update Affect More Languages?

While the tweeted announcement specified that the product reviews update was limited to the English language the official blog post did not mention any such limitations.

Google’s John Mueller offered his opinion that the product reviews update is something that Google could do in multiple languages.


One must wonder if the tweet was meant to communicate that the update was rolling out first in English and subsequently to other languages.

It’s unclear if the product reviews update was rolled out globally to more languages. Hopefully Google will clarify this soon.


Google Blog Post About Product Reviews Update

Product reviews update and your site

Google’s New Product Reviews Guidelines

Write high quality product reviews

John Mueller Discusses If Product Reviews Update Is Global

Watch Mueller answer the question at the 14:00 Minute Mark

[embedded content]

See also  Content Length: Is It a Google Ranking Factor?
Continue Reading

Subscribe To our Newsletter
We promise not to spam you. Unsubscribe at any time.
Invalid email address