JavaScript SEO is a very expansive subject and I suggest reading this

[bhasan01854]

If JavaScript is required to load key content on a page, this means that Google must perform a two-step indexing process where it processes the initial HTML, and then must return to the site to render any content loaded via JavaScript. Where SEOs need to check is in the second stage of the indexing process, to ensure that Google was able to “see” all of the content that is on the page. If any elements are loaded via JavaScript, it’s worth checking whether they’re indexed.


For instance, here’s an example of a product page in Magento where JavaScript is iran gambling data enabled in the browser. We can see thumbnail images, text in tabs, and a related products section at the bottom: JavaScript enabled on a product page for a clothing site. However, most of that content is reliant on JavaScript to load. When turning JavaScript off using the Web Developer extension for Chrome, most of those elements do not render. Notice how we can only see the initial three tabs on the page: Reduced elements on a page when JavaScript is turned off.


Since JavaScript is required to load a lot of the content on the page, we’ll want to ensure that it’s getting indexed properly. Fortunately, we can use tools such as The Mobile Friendly Testing Tool and The Rich Results Test to determine what Googlebot is able to render on the page. We also like to manually check the index by identifying content that’s loaded via JavaScript, and then using a “site:” search operator to verify that Google is able to read that text on the page.


guide by Pierce Brelinsky for more information. Just understand that if you use Magento, some of your content is likely loaded through JavaScript. 3. URL paths Out of the box, Magento will add the URL extension “.html” to the end of the site’s product and category URLs. While this isn’t necessarily “bad” for SEO, it does create lengthier URLs that are harder to read from a user perspective.