The webmaster is seeing these pages as duplicates or they see less indexing than they would expect.
John said that the webmaster will need to make sure that their website actually can be rendered for search first. One of the best ways to do this is to use a site query for these specific pages.
It’s important to do this because the testing tools have much stricter guidelines regarding how fast a server should respond compared to how Google actually acts.
It’s possible that the testing tool says that it’s not working when, in fact, it actually does work properly on Google itself.
This is important to keep in mind.
This conversation occurs at approximately 20:58 in the video:
John Mueller Hangout Transcript 09/03/2021
It doesn’t have this issue. And the issue just resolved itself for like one month when developers didn’t change anything. And the server folks also didn’t change anything. So we have no idea what’s happening. And I don’t really know where else to look. So if you have any ideas?
Is this something that you only see in the testing tools? Or is it something that you also see in the search results?
Webmaster 8 22:14
We see these pages being seen as duplicate, for example, or we see less indexing that we expect. So I think it’s actually not rendered correctly.
But that’s, that’s kind of the direction I would take there. So I would first check if it’s really a critical issue and then also check in with Martin to see if it’s maybe something on the edge where sometimes it works, sometimes it doesn’t work.
Webmaster 8 24:43
But at least in the cases I’ve looked at it, it is more something where they’re almost like hundreds or 200 300 400 500 requests that are required to render a page. And when you have that many in place, even if we cache a lot of those requests, it’s—it can be a bit hit and miss if the timing works out that we can actually complete all of those requests in time for rendering.