So, Remember, implementation. And maintenance of dynamic, rendering can, use a significant, amount of server resources and, if, you see Googlebot is able to index your pages properly. Then, if, you're not making critical high-frequency, changes, to your site maybe. You don't need to actually make employment anything special most, sites should, be able to let Googlebot render their pages just, fine. Like, I mentioned if Google web can render your pages they, probably, don't need dynamic, rendering for that side let's take a look at a few tools to help you figure out what, what the situation, is. What diagnosing, rendering we. Recommend doing so incrementally first, checking. The raw HTTP, response, and then, checking the rendered version either, on mobile, or on mobile, and desktop if. You serve different content for example let's. Quick take a quick look at these. So. Looking. At the raw, HTTP. Response, one. Way to do that is to use Google search console, to gain. Access to Google search console, and to, a few other features that they have their unit. First need to verify ownership of, your website this is really easy to do there, are a few ways to do that so I'd, recommend doing that regardless, of what you're working on once, you have your site verified, you can use a tool called fetch. As Google which. Will show, the, HTTP. Response that, was received by Googlebot including, the response code on top and the. HTML, that was provided, before any rendering was done this, is a great way to double-check, what is happening on your server especially. If you're using dynamic, rendering to, serve, different content, to Googlebot. Once, you've checked the raw, response, I recommend. Checking how, the page is actually rendered, so. The tool I use for this is the mobile-friendly, test it's, a really fast way of checking Google's rendering, of a page as as, I mentioned the, name suggests, that it's made. For mobile devices, so. As you might know over, time our indexing. Will be primarily focused on the mobile version of a page we, call this mobile, first the indexing so it's, good to already.
Another. Approach is to use structured. Data on a page when. We see structured, data that refers to an image we can also pick that up for image search as. A side note for images we, don't index images that are referenced. Only, through CSS we, currently only index images that are kind. Of embedded with the structured data markup, or with image tags. Apart. From lazy. Loaded, images, there are other types of content that require some, kind of interaction, to be loaded what about tabs, that. Load. The content after you click on them or if you have infinite scroll patterns, on his site Googlebot. Generally. Won't interact with a page so, it wouldn't be able to see these there are two ways that you, can get this to. Googlebot though either, you, can preload the content, and just, use CSS, to toggle visibility on. And off that way Googlebot can't see that content from, the preloaded version or, alternately, you can just use separate URLs and navigate, the user and Googlebot, to those pages individually. Now. Googlebot. Is a patient, bot, but. There. Are a lot of pages that we have to crawl so we have to be efficient, and kind of go, through pages fairly, quickly, when pages are slow to load or rendered Googlebot, might miss some of the rendered content and since. Embedded, resources, are aggressively, cached for search rendering. Timeouts, are really, hard to test for so, to limit these problems, we, recommend making performant. And efficient, web pages which. Are hopefully already. Doing for users anyway right. Anyway. In particular, limit, the number of embedded, resources and, avoid. Artificial, delays, like timed interstitials. Like here you, can test pages with the usual, set of tools and roughly. Test rendering with the mobile-friendly testing, tool and while timeouts, here are a little bit different for indexing in general, if the pages work in the mobile-friendly test they'll work for search injecting, -. Additionally. Googlebot. Wants to see the page as a new user would, see it so, we, crawl, and render pages in a stateless way any. API, that, tries to store something locally, would not be supported so if you use any of these technologies, make. Sure to use graceful, degradation techniques. To allow anyone, to view your. Pages, even if these api's are not supported. And. That. Was it with regards to critical, best practices, now it's time to take, a quick circle back and see what we see.
So. First. We. Recommend checking, for proper implementation of, best, practices, that we talked about in particular lazy. Loaded images are really common. Second. A sample, of your pages with. The mobile-friendly test and, use the other testing tools as well remember. You don't need to test all of your pages just make sure that you have all of the templates cover and then. Finally, if pages. Are large, and if, sites are large and quick changing, and you. Or you can't reasonably, fix rendering, across the site then, maybe, consider using dynamic rendering, techniques to serve Googlebot, and other crawlers, a pre-rendered. Version of your page and finally. If you do decide, to use dynamic rendering make. Sure to double check the results there as well. One. Thing to keep in mind, indexing, isn't, the same as ranking but generally speaking pages. Do need to be indexed before their content can appear in search at all I. Don't. Know Tom do you think that, covers about everything, well. It was a lot to take in John, some. Amazing content but I guess one, question I have and I think maybe other people in the audience have this on that mind as well as is, it always gonna be this way John. That's. A great question Tom I don't know is I think, things, will never stay the same, so as, you, mentioned in the beginning this is a challenge, for us that's important, within Google search we want our search results to reflect, the, web as it is regardless. Of the type of website that's use so, our long-term version, is that you the, developers, should, need to worry as much about. This for. Search, crawlers, so. Circling, back on the diagram that Tom. Showed at the beginning with deferred rendering one. Change we want to make is to move rendering, closer, to, crawling and indexing, another. Change, we want to make is to make Googlebot. Use a more, modern version of chrome over time both, of these will. Take a bit of time I don't, like making long-term, predictions, but I suspect there will be at least until end of year until.