3

I use Google Search Console to see how the crawler sees my page with a "Fetch & Render" option.

In the results:

  • Fetching tab: I can see the whole valid HTML without any errors
  • Rendering tab: The top of the page renders fine, but it stops rendering at some deep scroll point

The page has 3,260 words 18,458 characters of the main content.

I validated it with v3 HTML validator and its OK, except some irrelevant errors from Yoast Breadcrumbs which do not collide with other pages.

I did check it on 7 devices so far and on four main browsers (Firefox, Chrome, Opera, Edge) and it does fully render.

If I see the whole HTML fetched, should I be worried about the full HTML not rendered in the Search Console?

  • Can you add some more details about how your page is coded (e.g., does it use JavaScript to load portions of the page)? – dan Jun 26 '18 at 8:22
  • Yes, sure. It is coded and rendered with PHP, does not use javascript to load portions of the page. – wscourge Jun 26 '18 at 8:26
  • 1
    It's best if you edit the question to add that and any other details you can think of. For example, it seems that you're using WordPress? Are there any other plugins that might not respond to a bot (i.e., the Googlebot is a headless server that doesn't scroll, hover-over, click on things, etc...)? Have you also tried loading the page in an online screenshot site like Browsershots.org? Is your page more than 10,000 pixels? If so, even though it's cut-off it will still be indexed OK. – dan Jun 26 '18 at 8:34
  • 1
    @dan - thank you. Please publish your 10k pixels thing as an answer and I'll accept it, this is it. – wscourge Jun 27 '18 at 4:37
  • No problem. Feel free to add that as an answer below and accept it when you can. You'll earn some more reputation points if you do. – dan Jun 27 '18 at 23:12
2

Based on my experience, I'll try to make sure the rendering is perfect in order to avoid indexing problems.

You must have in mind this about Google Rendering Service:

  • doesn't support WebSocket protocol.
  • some interfaces and capabilities are disabled (webGL, IndexedDB , Service Worker, etc).
  • declines permission requests.
  • is affected by page load.

Sometimes, it just extracts the 'essential content':

Googlebot and WRS (web rendering service) continuously analyze and identify resources that don’t contribute to essential page content and may not fetch such resources. For example, reporting and error requests that don’t contribute to essential page content, and other similar types of requests are unused or unnecessary to extract essential page content.

Follow this steps in order to debug the rendering and locate the problem: https://developers.google.com/search/docs/guides/debug-rendering

  • Extracting "essential content" does not seem like cutting the bottom half of the page. By the page load, do you mean page speed that I can check with pagespeed.insights tool? If so, it is good - 85% on Desktop, and I fetch as Desktop. What experience do you base on exactly? – wscourge Jun 26 '18 at 7:52
  • Of course not, but it could be a mix of things and it's important to know everything that could affect the rendering. Run the debug in order to know where the problem might be. My experience is based on migrations from SSR to CSR, dynamic rendering or using prerender.io on a site with +1M indexed URLs. – Emirodgar Jun 28 '18 at 8:35
  • 1
    You can learn what caused the problem originally by reading the comments under the question. Thanks for your input anyway, grab the upvote as it might help somebody else. – wscourge Jun 28 '18 at 8:53
  • 1
    Glad you found the answer and also for letting me know what was the problem, Regards – Emirodgar Jun 29 '18 at 7:44
1

In my case, the page was more than 10,000 pixels and if so, even though it's cut-off it will still be indexed OK.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.