Post by account_disabled on Mar 10, 2024 15:11:05 GMT 7
The the latest and greatest from Moz. Surface actionable competitive intel New Feature Moz Pro Surface actionable competitive intel Log in Save with MozCon Early Bird tickets. Prices go up on March Register now Advanced seo daa Will Critchlow By Will Critchlow May Evidence of the Surprising State of JavaScript Indexing Advanced SEO Technical SEO Onpage SEO The authors views are entirely their own excluding the unlikely event of hypnosis and may not always reflect the views of Moz. Back when I started in this industry it was standard advice to tell our clients that the search engines couldnt execute JavaScript JS and anything that relied on JS would be effectively invisible and never appear in the index.
Over the years that has changed gradually from early workarounds such as the horrible Europe Cell Phone Number List escaped fragment approach my colleague Rob wrote about back in to the actual execution of JS in the indexing pipeline that we see today at least at Google. In this article I want to explore some things weve seen about JS indexing behavior in the wild and in controlled tests and share some tentative conclusions Ive drawn about how it must be working. A brief introduction to JS indexing At its most basic the idea behind JavaScriptenabled indexing is to get closer to the search engine seeing the page as the user sees it.
Most users browse with JavaScript enabled and many sites either fail without it or are severely limited. While traditional indexing considers just the raw HTML source received from the server users typically see a page rendered based on the DOM Document Object Model which can be modified by JavaScript running in their web browser. JSenabled indexing considers all content in the rendered DOM not just that which appears in the raw HTML. There are some complexities even in this basic definition answers in brackets asScript that requests additional content from the server This will generally be included subject.
Over the years that has changed gradually from early workarounds such as the horrible Europe Cell Phone Number List escaped fragment approach my colleague Rob wrote about back in to the actual execution of JS in the indexing pipeline that we see today at least at Google. In this article I want to explore some things weve seen about JS indexing behavior in the wild and in controlled tests and share some tentative conclusions Ive drawn about how it must be working. A brief introduction to JS indexing At its most basic the idea behind JavaScriptenabled indexing is to get closer to the search engine seeing the page as the user sees it.
Most users browse with JavaScript enabled and many sites either fail without it or are severely limited. While traditional indexing considers just the raw HTML source received from the server users typically see a page rendered based on the DOM Document Object Model which can be modified by JavaScript running in their web browser. JSenabled indexing considers all content in the rendered DOM not just that which appears in the raw HTML. There are some complexities even in this basic definition answers in brackets asScript that requests additional content from the server This will generally be included subject.