1. Avoid client-side rendering
Google recommends that websites with fast changing content and large websites should avoid client-side rendering because it can cause UX issues, and it can cause a delay in indexing. Google recommends dynamic rendering, i.e. web crawlers should get an easy to parse static HTML page.
3. Don’t trigger lazy-loading elements by scroll events
Lazy loading means that a web page element won’t be loaded until the point at which it is needed. For example, an image at the bottom of a web page might only be loaded if the browser of the web page visitor displays the bottom of the page.
Google says that you shouldn’t use scroll events to trigger lazy-loading. Desktop users might resize their browser window to get more content so the scroll event wouldn’t be triggered in that case. More importantly, Google does not scroll so that lazy-loading content wouldn’t be visible to Google.
4. You don’t need to specify what Google should render
It is Google’s job to parse the content of your web pages. You don’t have to implement anything on your website to tell Google what they should render. Not rendering particular elements on your web pages can also cause problems.
6. Google can ignore third-party scripts
If Google finds third-party scripts that aren’t useful to render a page, they will avoid fetching these scripts.
You can view the full video here:
Make sure that search engines can index your pages
If possible, deliver your web page content in plain HTML to search engines. The easier it is to parse your web pages, the more likely it is that your content can be indexed correctly.
To make sure that your web pages can be parsed by all crawlers, check your web pages with the website audit tool in SEOprofiler. You can create your SEOprofiler account here: