To break it down, Googlebot crawls a page fetching the server-side rendered content. Then runs some initial indexing on that document.
Because Googlebot runs two waves of indexing, it’s possible that some details might be missed. For example, if you’re not server-side rendering important metadata, Google might miss it on the second wave. Missing metadata can have obvious implications for your visibility.
Googlebot uses Chrome 41
At Google I/O, we discovered Googlebot uses Chrome 41 to render websites, which was released in 2015.
You might be wondering:
You should use caniuse.com to debug any code that may not be supported by Chrome 41.
Diagnosis rendering problems for Google Search
Google gave some tips on how to check if your website is being rendered and indexed correctly.
- Use Fetch as Google to check server response code and pre-rendered HTML
- Check how the page is rendered in Google’s mobile-friendly test.
- View the source HTML after rendering in Google’s mobile-friendly test
- Use the Rich results test to check the desktop version of your website.
If your website appears as expected in these tools, then your content should be indexed correctly.