So, depending on when your Amazon A+ pages were published, they could fall into a variety of states of accessibility, mobile friendliness, and visual attractiveness. What can we say? When a company decides to rest uneasily on day one in perpetuity, they can be a fickle beast to deal with.<\/p>\n
However, Amazon recently threw another question mark into this heady stew: they appear to be converting older A+ pages, namely hard-coded custom and template-based product pages, into JavaScript.<\/p>\n
Stay with me here.<\/p>\n
JavaScript<\/a> is a vital part of your online experience, whether you know it or not. It helps websites take in input from you, and it helps customize your online experience and decrease loading times (among its many possibilities and virtues). However, using it to populate product pages with enhanced product content could be a major drawback for online sellers.<\/p>\n Hard-coded product content is a permanent part of the product page. You (or, more importantly in this situation, a search engine crawler) can look at the page\u2019s source code and see how much liquid a water bottle holds or how wide a baby gate is.<\/p>\n This way, when a customer-to-be types \u201c1-liter water bottle\u201d or \u201c36-inch baby gate\u201d into Google or Amazon, that information is available to be indexed, helping your product information be more accessible\u2014and helping your product page rank better for those searches. Great, right? We think so.<\/p>\n Using JavaScript to populate that section of the product page means that, instead of your enhanced product content being right there amidst all the other fixed HTML and CSS that constitutes the product page, there\u2019s a quick snippet of JavaScript that calls your product content from another server. The product page you see, complete with A+ content, exists in its full form only when you load it.<\/p>\n Its components, meaning those parts that Google, Bing, and other search engines can actually index, aren\u2019t fixed and thus may not be crawled. (It can take a lot of effort to get your JavaScript crawled by a search engine \u2013 and there\u2019s no guarantee your labors will be successful over time.)<\/p>\n Once a customer is on the product page, it\u2019s not a big deal. However, your painstakingly crafted product content will no longer be as much help in getting them there.<\/p>\n Standard SEO best practices call for content to be contained exclusively in HTML (and viewable even if your CSS is turned off). Want to see what a search engine might see? Check it out in its Google Cache version<\/a> to get a sense of what\u00a0the<\/em>\u00a0search engine sees when it looks at your page. JavaScript menus are assumed to be unreadable to search engines; it’s a good bet to assume that product information contained in a page’s JavaScript snippets may also be overlooked.<\/p>\n Google can be capricious; what’s read today may not be tomorrow, and it’s best to opt for hard-coded content where possible to future-proof your content’s SEO value. Like text embedded in images<\/a>, this attempt to simplify things on the dev side of your site\u00a0can cause rippling problems that can piss off your customers–or keep them from getting to your product page in the first place.<\/p>\n This appears to be happening exclusively to older pages, and we would guess that these pages are a casualty of Amazon\u2019s fierce new focus on mobile shoppers. If your older pages aren\u2019t yet converted to JavaScript, it\u2019s very likely that they will be soon. Keep an eye on your pages, and be ready to email your merchandiser if the switch happens.<\/p>\n For SEO\u2019s sake (for both search engines and within Amazon itself), it\u2019s worth it to keep your content hard-coded\u2014even if it means switching to the modules. Some search engines may be able to index JavaScript enhanced content, but \u201csome\u201d and \u201cmay\u201d aren\u2019t parts of an effective, worthwhile online selling strategy.<\/p>\n","protected":false},"excerpt":{"rendered":" If you\u2019ve created Amazon A+ pages in the last two years, the design of your product pages falls into one…<\/p>\n","protected":false},"author":34,"featured_media":24996,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[789],"tags":[1403,1334],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n\n\t\n\t\n\t\nJavaScript = Invisible Product Content<\/h2>\n
![\"How](\"http:\/\/content26.com\/wp-content\/uploads\/2015\/01\/javascript-product-page-comparison.png\")
<\/p>\n