UPDATE (9/21/17): For SEO, we now recommend Prerender.io over the Meteor Spiderable package. Please refer to our docs for more info.
While many people may know the basics of creating an SEO-friendly site, they may not understand what is happening behind the curtain. So here’s a brief explanation of the search bot’s process.
When a search engine’s bot crawls your site and its content, it captures the HTML document on your server, indexes it, and then follows links to your other content. The result is that when a user enters a query into a search engine, it matches the query against the indexed content and returns the search engine’s best results.
Meteor applications aren’t the first to have encountered this issue though, and several years ago Google, Bing and others started supporting the “_escaped_fragment” schema. If you add
<meta name="fragment" content="!"> to the page, this will indicate to the crawler to request an alternate page source. If the first request isn’t an HTML page, the crawler will try this alternate source.
Because Reaction Commerce is a “single page application” we can use some additional tools such the Meteor package
gadicohen:sitemaps that generates sitemaps, and the
iron:router package that provides simulated pages or routes for specific page content with a unique URL.