\n<\/p>\n
In an interview<\/a> with Kenichi Suzuki from Faber Company Inc., Google Developer Advocate Martin Splitt recently shared key information about JavaScript rendering, server-side vs. client-side rendering, and structured data<\/a>.<\/p>\n The talk cleared up common SEO confusion and offered practical tips for developers and marketers working with Google\u2019s changing search systems.<\/p>\n When asked how AI systems handle JavaScript content, Splitt revealed that Google\u2019s AI crawler (used by Gemini) processes JavaScript well through a shared service.<\/p>\n Splitt explained:<\/p>\n \u201cWe don\u2019t share what Googlebot sees for web search, but Google\u2019s AI crawler that Gemini uses also renders. It uses WRS [Web Rendering Service], but it\u2019s basically like we have a service Googlebot uses, and Gemini uses the service as well.\u201d<\/p>\n<\/blockquote>\n This gives Google\u2019s AI tools an edge over competitors that have trouble with JavaScript.<\/p>\n While one study mentioned in the interview claimed rendering sometimes takes weeks, Splitt explained that it usually happens much faster.<\/p>\n \u201cThe 99th percentile is within minutes,\u201d Splitt noted, suggesting that long delays are rare and might be due to measurement errors.<\/p>\n Part of the discussion covered the debate between server-side rendering (SSR) and client-side rendering (CSR).<\/p>\n Instead of saying one is always better, Splitt stressed that the right choice depends on what your website does.<\/p>\n Splitt stated:<\/p>\n \u201cIf you have a website that is a classical website that is basically just presenting information to the user, then requiring JavaScript is a drawback. It can break. It can cause problems. It will make things slower. It will need more battery on your phone.\u201d<\/p>\n<\/blockquote>\n Splitt suggests SSR or even pre-rendering static HTML<\/a> for websites focused on content. But CSR works better for interactive tools like CAD programs or video editors.<\/p>\n Splitt clarified:<\/p>\n \u201cIt\u2019s not one or the other. It is two tools. Do you need a hammer or do you need a screwdriver? That depends on what you\u2019re trying to do.\u201d<\/p>\n<\/blockquote>\n See also:<\/strong> Understand the Difference Between Client-Side and Server-Side Rendering.<\/a><\/p>\n The talk then moved to structured data, which is becoming more important<\/a> as AI systems grow in search.<\/p>\n When asked if structured data helps Google\u2019s AI understand content better, like Microsoft claims about Bing, Splitt confirmed it helps.<\/p>\n He stated:<\/p>\n \u201cStructured data gives us more information and gives us more confidence in information. So it makes sense to have structured data.\u201d<\/p>\n<\/blockquote>\n However, Splitt clarified that while structured data adds context, it \u201cdoes not push rankings\u201d directly. This is an important difference for SEO professionals who might think it directly boosts search positions.<\/p>\n Here are the key things we learned from this interview:<\/p>\n In his final advice to SEO professionals, Splitt highlighted basic principles over technical tricks:<\/p>\n \u201cThink about your users. Figure out what is your business goal, how to make users happy, and then just create great content.\u201d<\/p>\n<\/blockquote>\n As AI changes search technology, understanding these technical details becomes more important for marketers who want to optimize content for people and search algorithms.<\/p>\n Hear the full discussion in the video below:<\/p>\nGoogle\u2019s AI Crawler & JavaScript Rendering<\/h2>\n
\n
Server-Side vs. Client-Side Rendering: Which is Better?<\/h2>\n
\n
\n
Structured Data\u2019s Role in AI Understanding<\/h2>\n
\n
What This Means<\/h2>\n
\n
\n