Would you switch to a new eCommerce platform if you knew it would throw off your entire fulfillment operation?

That’s a rhetorical question; of course you wouldn’t.

But in our experience in optimizing SEO for hundreds of eCommerce brands over the past 11 years, we’ve noticed some similarly poor habits when it comes to selecting an eCommerce platform.

Too often, companies are happy to migrate to a hosted eCommerce platform without any clue how it will affect the SEO strategy they’ve been using for years.

This results in a decision process that becomes upside down. Companies that don’t weigh SEO functionality end up choosing the wrong platform for their SEO goals.

This article is meant to help you mitigate or avoid this mistake.

Rather than finding the platform you like, crossing your fingers, and hoping for the best for your SEO, you can use the information below to try to understand the potential SEO functionality of hosted and self-hosted eCommerce platforms first.

To do that, you’ll have to know the variables you most need to focus on, and how they relate to your decision. Here are some of the essentials:

What an eCommerce Platform Gives You (Or Doesn’t Give You)

The methodology behind this list is simple: There are a variety of different knobs you can turn on within your site to improve SEO performance, such as setting the canonical URL of a specific product page. Whether an eCommerce platform lets you control each of these features will affect your ability to make changes that can improve organic search rankings.

The list here is based on our experience turning these knobs and improving SEO performance from multiple approaches for many clients over the years.

Below, we discuss each site control feature, why it’s important for SEO, and how hosted versus self-hosted eCommerce platforms differ in your ability to control the features.

What are hosted and self-hosted eCommerce platforms?

The key distinction that often separates one eCommerce platform from another is whether it’s hosted or self-hosted.

  • Hosted platforms are essentially “turnkey” solutions intended to provide a straightforward infrastructure for your eCommerce.
    • Advantages include ease of use, site stability, and speed of implementation.
    • Disadvantages tend to result from limited control over individual SEO variables like Robots.txt.
    • Examples include BigCommerce; Shopify; Salesforce DemandWare/Commerce Cloud.
  • Self-hosted platforms, which include many popular open source platforms, are more freeing (and challenging) because you’ll have more control.
    • While controlling the development yourself makes it more difficult to get a shop up and running, you’ll have more SEO advantages such as access to log files (depending on which platform you’re using; WordPress may not give you access to log files), easier batch uploading, and control over elements like canonical tags.
    • Examples include WordPress with a WooCommerce plugin; Magento; SpreeCommerce; and of course home built eCommerce systems.

Here is how the different styles of platforms stack up with some common eCommerce SEO concerns:

Site Speed

A customer’s bounce probability increases 32% for a page that takes 3 seconds to load over a page that takes just one second to load. But it’s not just about bounce rates anymore. When Google announced that Page Speed would factor in search results, the speed of your site became a major SEO factor.

To accomplish goals like achieving a 100/100 Page Speed score with Google, you need the ability to control many aspects of your site. For example, we’ve experimented with embedding CSS in-line rather than in HTML and loading external scripts asynchronously.

Platforms like Shopify and BigCommerce tend to give you middle-of-the-road site speed; not bad, but not great, either. If you have a smaller store and speed is a chief SEO advantage, you might want to consider that self-hosted SEO gives you much more control through the following variables:

  • Leveraging browser caching to incorporate visuals without sacrificing load time. If you’re working on a hosted platform, you generally won’t control this.
  • Optimizing your image sizes to minimize load time. Here, almost all platforms will give you that control.
  • Scaling images for separate mobile and desktop experiences. Hosted platforms generally don’t give you this ability.

If you’re obsessed with site speed and beating the competition, a hosted platform simply won’t give you the functionality you need.

The trade-off in controlling your own site speed: that you’re also responsible for handling more bandwidth. If your store was suddenly featured on “The Ellen Show,” would you be able to handle the influx of traffic? On a platform like Shopify or BigCommerce, you probably could, and more importantly, getting the infrastructure in place to handle spikes like that is the host’s problem, not yours. (Although you may still need to work with your hosted platforms to ensure you can handle the traffic, it’s generally easier to handle with hosted systems when you do).  If your store is self-hosted, you likely need additional preparation time before going viral.

Batch Uploading

If you ever find yourself with a large swath of redirect, meta data, or product page problems, batch uploading may be the only way to fix each individual page in one fell swoop.

Batch uploading helps fix sweeping problems such as problematic redirect pages or broad swaths of meta tags that need changing. If you can’t batch upload SEO solutions like these without interfering with your site’s functionality, you’re in for some headaches.

For batch uploading on hosted platforms, you’re at the mercy of your plugins. Failing that, a hosted platform will require you to upload each individual file using a web interface. We want to avoid that for obvious reasons.

Before you conclude that a plugin is a simple thing, remember that you have to weigh price and the risk of unintended consequences before you acquire a plugin.

I’ve personally come across a plugin that promises to handle everything from batch uploads to redirect analytics. Sounds great, right? More analytics means more insight into your site.

The problem with that plugin was that it would conduct redirect analytics by running traffic through their URL – creating redirect hops through another domain – which is less than ideal for your SEO. I wanted batch uploading; the plugin promised that and a whole bunch of negative SEO consequences I didn’t want.

If you plan to incorporate a lot of sweeping changes that require batch uploading, make sure that your hosted platform has an effective plugin available before you make the switch.

In a self-hosted eCommerce solution, batch uploading will require having a developer on hand who can give you a solution specific to your uploading needs.

Canonical Tags

Canonical tags help you tell Google which page on your site is the original source of information, or the “master copy” of your page.

Essentially, Google allows you to consolidate duplicate URLs by designating your “canonical URL.” This results in a consolidated site with targeted pages to which you want to direct SEO attention.

Your inability to control canonical tags means you could end up with a large number of pages that Google essentially sees as “canonicalized to themselves” – even if/when they aren’t true canonicals.

You can use canonical tags to essentially tell Google, “yes, this individual page is duplicate content, and the original source of the content can be found over here. But we need this duplicate content to help the customer experience—so don’t punish us with a lower ranking.”

When You Need to Control Canonical Tags

Let’s imagine you run an eCommerce site selling furniture. A customer browses your products and filters out a specific category like “round tables”:

Furniture -> Tables -> Round Tables

This lands the customer on a unique product listing page like /alltables?shape=round.

That’s fine for the customer. But if that page has the same essential content as the /round-tables category page, you risk diluting the content when it comes to Google’s priorities.

In that use case, we would want to canonicalize the “/alltables?shape=round” to the /round-tables category page so the /round-tables continues to garner positive attention from Google.

Keep in mind that with hosted platforms like Shopify, you generally won’t have this control. You may be able to employ fancy workarounds with the help of a senior developer. Failing that, the existing plugins for hosted solutions are lacking, which is why you would need a developer to handle complicated changes.

If you’re a small company, these use cases can be complex and you won’t always have to worry about them. But the more sophisticated your SEO needs are, the more you’ll need this type of control in the future.

Robots.txt

Most in SEO are familiar with what control over Robots.txt means, and we’ve previously addressed whether to index internal site search URLs. This is another essential avenue of control for eCommerce, allowing you to guide search engine bots as they crawl your site. The most important function is usually telling search engines where not to crawl, which helps preserve precious crawl budget, and avoid consequences as a result of duplicate content.

Self-hosted platforms tend to give you more control here, allowing direct editing of your own Robots.txt. Platforms like WordPress, Craft Commerce, and BigCommerce will allow you to edit Robots.txt, while Shopify limits your access. If you host your own site, you can expect as much control as you’d like.

Sitemap Generation

Your sitemap is a simple document that you use to show search engines. It’s a literal map of your site the search engines can use for reference.

There are generally two types of sitemaps: HTML and XML versions:

  • The HTML version is typically for the user, a list of links (hopefully with an intuitive visual display) to guide them around your site.
  • An XML sitemap is essentially the same thing, but formatted specifically for search engines.

Simple enough, right? The wrinkle: you don’t want an eCommerce platform to automatically generate a sitemap that simply includes every possible URL on the site. This might result in a sitemap with the wrong pages, including non-canonical pages, non-indexable pages or pages that are non-functional (e.g. 404 & 500 errors.) We’ve found it important to present a consistent front to Google regarding whether you do or don’t want content crawled and indexed.

Regardless of platform type, the XML sitemap may be implemented by default or may require a plugin.

There are cases for each in each direction; WordPress needs a plugin but it’s a default in Shopify. However, you may need a Shopify plugin to alter functionality since all pages are included by default.

As with hosted eCommerce platforms, you’ll find that the sitemaps can vary wildly in functionality depending on the quality of these plugins. The key is to test this functionality to ensure that only functional, canonical, & indexable URLs are included.

Log File Access