Now, with dynamic rendering comes as a solution as it renders a website server-side and serves it to the bots as “static HTML,” while the site remains unchanged to visitors.
The process let search engine bots quickly crawl the website, understand the content and index them properly and helps sites to gain an SEO position.
Dynamic rendering means switching between client-side rendered and pre-rendered content for specific user agents.
Here is a flowchart of Google Dynamic Rendering:
Here is a video of @John Mueller talking about the dynamic rendering at the I/O:
Explaining more he said, “dynamic rendering is the principle of sending normal client-side rendered content to users and sending fully server-side rendered content to search engines and to other crawlers that need it.”
📢If you have heard @johnmu mention dynamic rendering at I/O and wonder what it is, when to use it and how to solve common issues, we’ve got you covered with the new 📖”Get started with dynamic rendering” docs at https://t.co/e4pmAlMBqP 🎉 pic.twitter.com/MXhigsZPQx
— Google Webmasters (@googlewmc) 3 October 2018
The image above the fold shows the process for dynamic rendering. In the image below you can see a diagram of Google Dynamic Rendering Infrastructure setup:
The help documentation begins with explaining what is dynamic rendering and goes on in details about when to use it, and how to implement it. It’s divided into the following categories:
- Get started with dynamic rendering
- Sites that should use dynamic rendering
- Understand how dynamic rendering works
- Implement dynamic rendering
- Verify your configuration
- Content is incomplete or looks different
- High response times
- done Fix the issue
- Structured data is missing
The documentation is available here.