Post by account_disabled on Feb 19, 2024 10:45:58 GMT 1
We have translated and delivered episode 3 of the series "SEO Mythbusting", which debunks misconceptions about SEO urban legends, distributed on the Google Webmasters YouTube channel . (Episode 2 is summarized in this article ) Episode 3 was released on June 7, 2019, in which Martin Splitt, Webmaster Trends Analyst at Google, and Jamie Alberico, SEO Product Manager at Arrow Electronics, discuss JavaScript, a topic that is often misunderstood and attracts a lot of attention. I'm talking about. I will introduce the contents of the episode below. overview Is JavaScript the devil? (About JavaScript usage from Google's perspective) Using Ajax and its impact on crawl budget About the relationship between Googlebot and JavaScript About pre-rendering Advantages of properly implementing JavaScript for SEO About noteworthy performance indicators and testing tools Q&A Below is a summary of the contents of Episode.
This time as well, we had a conversation with a lot of telephone number list interesting digressions, so I've omitted some of it or paraphrased it, and I've tried to summarize it so that the main meaning is not lost. Q: Is JavaScript the devil? That's a good question! It's easy to think that way, especially when things don't go well. There are a lot of misunderstandings from an SEO perspective and a development perspective, but I don't think it's the devil. JavaScript has its benefits. You can create amazing things, and you can create things that are tailored to user behavior and requests. I think JavaScript is great for moving the web from a document-based platform to an application platform. We are currently battling the misconceptions that "JavaScript is the devil" and "If you use JavaScript, you won't be indexed." This idea is old, and now the help documentation has been updated to show things to be careful about.
For example, SPAs (single-page applications, websites that use JavaScript to display content and transition between pages) are often considered to be high-risk. There is one important point in particular that many developers do not understand, and that SEO personnel fail to convey. That is, Google is stateless. SPA has an application-like state, and you always know which page you are looking at and what kind of transitions you are making. However, when a user clicks on a link in a search result, they are directed to a page indexed by Google without that state. Google only indexes pages that are directly accessible. Functions that depend on JavaScript are often based on user transitions.
This time as well, we had a conversation with a lot of telephone number list interesting digressions, so I've omitted some of it or paraphrased it, and I've tried to summarize it so that the main meaning is not lost. Q: Is JavaScript the devil? That's a good question! It's easy to think that way, especially when things don't go well. There are a lot of misunderstandings from an SEO perspective and a development perspective, but I don't think it's the devil. JavaScript has its benefits. You can create amazing things, and you can create things that are tailored to user behavior and requests. I think JavaScript is great for moving the web from a document-based platform to an application platform. We are currently battling the misconceptions that "JavaScript is the devil" and "If you use JavaScript, you won't be indexed." This idea is old, and now the help documentation has been updated to show things to be careful about.
For example, SPAs (single-page applications, websites that use JavaScript to display content and transition between pages) are often considered to be high-risk. There is one important point in particular that many developers do not understand, and that SEO personnel fail to convey. That is, Google is stateless. SPA has an application-like state, and you always know which page you are looking at and what kind of transitions you are making. However, when a user clicks on a link in a search result, they are directed to a page indexed by Google without that state. Google only indexes pages that are directly accessible. Functions that depend on JavaScript are often based on user transitions.