{"id":47192,"date":"2019-03-21T14:20:59","date_gmt":"2019-03-21T21:20:59","guid":{"rendered":"https:\/\/eigene-homepage-erstellen.net\/?p=47192"},"modified":"2019-06-19T18:10:19","modified_gmt":"2019-06-20T01:10:19","slug":"javascript-bad-for-seo","status":"publish","type":"post","link":"https:\/\/eigene-homepage-erstellen.net\/blog\/seo\/javascript-bad-for-seo.htm","title":{"rendered":"Is Javascript Bad For SEO?"},"content":{"rendered":"\n

Does a bear poop in the woods? With javascript and SEO, the answer is just as clear, if a little more complicated.<\/p>\n

Javascript-driven sites aren’t bad for indexation<\/strong>. Google can crawl a site that populates content client-side.<\/p>\n

Javascript-driven client-side content is bad for SEO<\/strong>. Javascript-driven sites make Google work harder. At the very least, Google renders them more slowly. In the SERPs, that’s a competitive disadvantage.<\/p>\n

To demonstrate (Ian rubs his hands together) I get to use quadrant diagrams.<\/p>\n

If you already know how javascript works, what client-side rendering is, and how Google handles client-side rendering, print this, stick it to your forehead, and move on:<\/p>\n

For us mere mortals, here’s a fuller explanation:<\/p>\nTwo Types Of Javascript<\/h2>\n

There are two ways client-side javascript—javascript executed by a web browser—can interact with web content:<\/p>\n

UI enhancement<\/strong> changes the way the browser interacts with content rendered on the server. Examples include tabbed, drop down navigation, and (sigh) carousels.<\/p>\n

Client-side rendering<\/strong> delivers pages and content separately. Your web browser uses javascript to merge the two.<\/p>\n

This post talks about client-side javascript rendering and why it’s bad for SEO.<\/p>\n

Client vs. Server-Side<\/h2>\n
Every web page is an interaction between a client (a browser, like Chrome, or a bot, like Google) and a server.<\/p>\n
Generating a web page involves three steps:<\/p>\n
\n
Fetch the page template (the layout)<\/li>\n
Fetch the content<\/li>\n
Merge the content with the template<\/li>\n<\/ol>\n
Server- and client-side rendering perform these three steps differently.<\/p>\n
Server-side rendering does all three steps on the server, then sends the result to the client. The client has everything it needs, renders the full page, and goes on its merry way.<\/p>\n
Client-side rendering uses javascript to split the labor: It sends the template to the browser or bot, then sends the content separately. The browser uses javascript to merge the content and the template. Client-side rendering has advantages: It’s speedy (if you do it right). It’s a great way to build interactive applications. But it requires more work by the client.<\/p>\n
Here’s our quadrant diagram so far:<\/p>\n