- Press "RENDER JS" as GoogleBot
- Wait Until the WRS processes the page, open rendered page
- Check the source code (see page content in indexable HTML format)
- Validate requested domain as an existing hostname
- Follow all HTTP redirects
- Simulate Evergreen GoogleBot WRS (Google's Web Rendering Service)
- Build Page DOM (Document Object Model)
It is an intermediary process between the request and server response, triggered only for search engines (crawlers, search engine bots) after checking the name of the requesting User Agent, the so-called User-Agent String.
- URL request by a Search Engine (crawler, search engine bot)
- Server-side detection of the requesting User-Agent
- In case the requesting User-Agent is recognized as a regular user - normal content version is sent to the browser during server response
- In case the requesting User-Agent is recognized as a search engine, the following processes are triggered:
- Requested URL is fetched by the middleware (dynamic content rendering)
- All critical page resources are loaded
- Final code (the rendered HTML of the DOM) is placed in the source HTML file generated on the server
- Pre-rendered HTML code of the page is sent to the requesting Search Engine (crawlers, bot)
In other words, Dynamic Rendering in SEO is a process in which a page will be rendered differently depending on the requesting user agent - switching between the content displayed on the client side and the pre-rendered content for specific user agents.
- Crawl Queue
- Crawl process
- Processing (parsing) of raw HTML file
- Processing (parsing) of the rendered HTML
- Indexing of the rendered and processed content
SSR stands for Server-Side Rendering. Search engines try to get the same content that users see in the browser. Google's Web Rendering Service (WRS, part of the Caffeine indexing system) is responsible for the rendering and scanning process.
In case of Server-side rendering of the content Googlebot receives a fully rendered piece of HTML code. This significantly improves the scores of the First Contentful Pain and Largest Contentful Paint metric, which is very important in the context of the new Google Page Experience ranking factor.
Server-side rendering is the preferred option for all sites because all meaningful content is rendered on the website server - both users and bots get a fully loaded page without having to request additional resources. This shifts the burden of rendering the page differently for both human visitors and search engine robots and passes it on to your web server.
Unlike server-side rendering, dynamic rendering can be a pretty turnkey solution. This means you can give the search engine robots what they want without taking up too much time from your development team.
Compared to server-side rendering, the use of a dynamic rendering SEO tool may not always be the cheapest solution. That's because you'll need to pae per rendered and cached jabvascript page.
- Implement dynamic rendering
- Server-side or Pre-rendering
- Implement dynamic rendering