Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Moving E-Commerce Store to Subdomain?
-
Hi all,
We have a customer who currently uses Square for their in-store point-of-sale system as well as for their e-commerce website. From my understanding, a Square site is a watered-down version of Weebly, and is proving to be highly restrictive from an SEO and content structuring standpoint. It's been an uphill battle to try and get traction for their site in SERPs. Would it be a bad idea to move the entire Square online store to a subdomain, and install WordPress on the root domain? This way their online store would remain as-is, but the primary pages on the site would be on WordPress which would give us a lot more control over the content. I just want to make sure this doesn't negatively impact their SEO.
Thanks!
-
Thanks for the clarification on the platform Suarezventures.
I have worked with plenty of brands that have a similar setup on Shopify. They usually put the blog on a subdomain because Shopify's content management system - let's see, how do I say this nicely... sucks. These clients put up Wordpress on a subdomain. Some also put up a landing page platform like Hubspot or Unbounce to which they send paid traffic.
Your plan to put the eCommerce site on a subdomain has some benefits in that the content side won't be affected by future platform migrations on the eCommerce site. However, the content side will benefit the most from being at the main level with the homepage and most of the backlinks. Thus, organic search traffic to the eCommerce site could be harmed by this move. I normally wouldn't recommend it for that reason (because the business is eCommerce, which is what pays for the content) but in your case, it sounds like the eCommerce site doesn't bring in much traffic as it is.
Good luck. Let us know how it turns out.
-
Hi Everett,
In this case both the sites would be tied into each other and aren't that different, but my thought was that separating the online store would give us more flexibility with the root domain. If I implemented this, their WP site would be customersite.com and the e-commerce side of it would be at shop.customersite.com.
Their current website is through Square (not Squarespace), and it's a watered-down version of Weebly. Square also handles their online payments, in-store payments, customer loyalty system, and inventory management, so that's why we were thinking of relegating it to a subdomain instead of switching everything over to WordPress. Thankfully, Square makes it really easy to change the site address to a subdomain, so there isn't going to be a ton of migration work involved.
-
Thank you for the detailed response! The client has the same inventory for in-store sales and online sales, so their physical and virtual storefronts are both important to them. As for restrictions on the current platform, they're using a website through Square (which is a watered-down Weebly I believe) and it doesn't even have proper blogging functionality which is one of our primary points of concern.
-
If they are not planning to do any link building then you should be fine with setting up everything on the subdomain.
Ross
-
Hi Suarezventures,
I typically draw the subdomain vs top-level domain line at whether the two sites / experiences and purposes are vastly different. For example, a site like blogspot that hosts different websites on subdomains, or a brand that has a forum community on a subdomain because it runs on a different server and has a much different purpose than the main domain.
Ideally, if you're moving to Wordpress you'd have the content and the store on the same site (e.g. https://site.com). If this isn't possible for them, having one or the other on a subdomain would be better than having them on (Squarespace?).
What about having the new site on a subdomain so you don't have to deal with migrating the existing site? Can' t you leave it there and put up store.site.com on WP?
-
I think that might be a successful approach under some circumstances. For example, if the company is a brand, and their storefront is only one aspect of that brand but you think that they might otherwise rank for searches of non-transactional intent. An example might be a museum which also runs a gift shop. Or a manufacturer who also manages a direct-to-consumer storefront but where that is not the focus of their business. In these and similar cases, having a separate set of pages (whether on a subdomain or preferably just in a subfolder if feasible) for the commerce isn't necessarily a bad idea. I'm assuming when you wrote "proving to be highly restrictive", you meant more than just for example not being able to set the exact H1 tags you might want on a page or not being able to insert schema markup for certain types of objects. There are going to be those kinds of tactical challenges for on-page SEO in every platform, just varying degrees between the platforms, and I wouldn't take a drastic approach like separating the storefront just because of those kinds of issues. But, if the SEO challenges with the current platform are really of the highest severity and can't be addressed within that platform, then the approach of a separate storefront might make sense in the kinds of scenarios like the museum or the manufacturer mentioned above.
-
Hi Ross,
Would it still be a bad idea if we're not really planning to rank category pages or products on the subdomain? Or if they don't have much SEO traction at all at the moment anyway? Ideally we would love to switch them to WordPress + WooCommerce in the long term but everything in their business is tied to Square (including physical operations, email list and even their loyalty program) and they don't have the budget to switch everything over completely.
Thanks!
-
Hi there,
I think it is a bad idea if you are planning to rank category pages or products on that subdomain. The best option is to set up everything on WordPress with the Woocomerce plugin. The WordPress CMS is very flexible, SEO friendly and you have an access to your server if you need to pull server logs from it.
Ross
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Subdomain 403 error
Hi Everyone, A crawler from our SEO tool detects a 403 error from a link from our main domain to a a couple of subdomains. However, these subdomains are perfect accessibly. What could be the problem? Is this error caused by the server, the crawlbot or something else? I would love to hear your thoughts.
Technical SEO | | WeAreDigital_BE
Jens0 -
Does using a reverse proxy to make a subdomain appear as a subdirectory affect SEO?
Using a reverse proxy only makes it appear that a subdomain is really a subfolder. However, links in the end remain the same. Does this have any negative (or positive) impact on SEO? Does it make it difficult from the blog's (subdomain's) sitemap or robots.txt file to be properly read by search engines?
Technical SEO | | rodelmo41 -
Robots.txt on subdomains
Hi guys! I keep reading conflicting information on this and it's left me a little unsure. Am I right in thinking that a website with a subdomain of shop.sitetitle.com will share the same robots.txt file as the root domain?
Technical SEO | | Whittie0 -
Does an subdomain hosted offsite provide SEO value
We have a job board hosted through an applicant processing system which we've setup as a subdomain (jobs.ourcompany.com), most of the assets are hosted on our primary domain (ourcompany.com). My question is does having it hosted offsite provide any value? Do we get credit for that content being shared and distributed on the web or does the applicant processing system? As I see it the options are (correct me if I'm wrong): Host the job listings on our primary domain (ourcompany.com/jobs) and have it point to the application on the subdomain. Advertise the job listings pointing to the primary domain on the paid sites. The free job listing sites will automatically point to the sub-domain because the applicant processing system automatically submits them. Host the job listings entirely on the sub-domain applicant tracking system and link to it from our primary site navigation. Advertise the job listings to the sub-domain so that both free and paid point to the same place. Obviously the second one would be much easier just not sure on the technical side of our website getting credit by search engines as the one who has produced the content.
Technical SEO | | r1200gsa0 -
Http to https - is a '302 object moved' redirect losing me link juice?
Hi guys, I'm looking at a new site that's completely under https - when I look at the http variant it redirects to the https site with "302 object moved" within the code. I got this by loading the http and https variants into webmaster tools as separate sites, and then doing a 'fetch as google' across both. There is some traffic coming through the http option, and as people start linking to the new site I'm worried they'll link to the http variant, and the 302 redirect to the https site losing me ranking juice from that link. Is this a correct scenario, and if so, should I prioritise moving the 302 to a 301? Cheers, Jez
Technical SEO | | jez0000 -
Staging & Development areas should be not indexable (i.e. no followed/no index in meta robots etc)
Hi I take it if theres a staging or development area on a subdomain for a site, who's content is hence usually duplicate then this should not be indexable i.e. (no-indexed & nofollowed in metarobots) ? In order to prevent dupe content probs as well as non project related people seeing work in progress or finding accidentally in search engine listings ? Also if theres no such info in meta robots is there any other way it may have been made non-indexable, or at least dupe content prob removed by canonicalising the page to the equivalent page on the live site ? In the case in question i am finding it listed in serps when i search for the staging/dev area url, so i presume this needs urgent attention ? Cheers Dan
Technical SEO | | Dan-Lawrence0 -
Subdomain Removal in Robots.txt with Conditional Logic??
I would like to see if there is a way to add conditional logic to the robots.txt file so that when we push from DEV to PRODUCTION and the robots.txt file is pushed, we don't have to remember to NOT push the robots.txt file OR edit it when it goes live. My specific situation is this: I have www.website.com, dev.website.com and new.website.com and somehow google has indexed the DEV.website.com and NEW.website.com and I'd like these to be removed from google's index as they are causing duplicate content. Should I: a) add 2 new GWT entries for DEV.website.com and NEW.website.com and VERIFY ownership - if I do this, then when the files are pushed to LIVE won't the files contain the VERIFY META CODE for the DEV version even though it's now LIVE? (hope that makes sense) b) write a robots.txt file that specifies "DISALLOW: DEV.website.com/" is that possible? I have only seen examples of DISALLOW with a "/" in the beginning... Hope this makes sense, can really use the help! I'm on a Windows Server 2008 box running ColdFusion websites.
Technical SEO | | ErnieB0 -
What is the best method to block a sub-domain, e.g. staging.domain.com/ from getting indexed?
Now that Google considers subdomains as part of the TLD I'm a little leery of testing robots.txt with something like: staging.domain.com
Technical SEO | | fthead9
User-agent: *
Disallow: / in fear it might get the www.domain.com blocked as well. Has anyone had any success using robots.txt to block sub-domains? I know I could add a meta robots tag to the staging.domain.com pages but that would require a lot more work.0