Is there anything else I need to consider moving our root domain to a shop subdomain?

Topic summary

A user plans to migrate their Shopify store to a subdomain (shop.mywebsite.com) while maintaining a separate product selection on the root domain (mywebsite.com).

Proposed approach:

  • Connect subdomain via DNS provider to Shopify
  • Create two collections: one for subdomain products (90% of inventory), another for root domain products (10% selective items)
  • Set up a landing page for the shop subdomain with redirect

Key considerations raised:

  • DNS propagation may take several days; cache invalidation needed for web apps
  • Clarification needed on how products will display on the root domain if Shopify’s online sales channel points to the subdomain (embeddable buy buttons suggested as potential solution)
  • Question about whether an additional landing page/redirect creates unnecessary friction versus directing users straight to the subdomain homepage

Current status: The original poster acknowledged the DNS timing concern and clarified the dual-front structure, but indicated they need to review the technical implementation details around displaying products across both domains.

Summarized with AI on November 1. AI used: claude-sonnet-4-5-20250929.

We’re planning to move our current store to a shop.mystore.com subdomain.

The shop will contain different products vs root domain but will still include a navigation to our shop page.

I have looked into previous discussions around this and would like to know if I have covered everything or are there things I still need to consider or work on.

Things I am planning to do:

  1. Create a subdomain in our DNS provider and connect to Shopify.
  2. Create two new collections - one for products on our shop subdomain, the other for our root domain products.
  3. Create a new page to be the landing page for our shop and redirect the subdomain to that page.

Hi @kraftivsoftware :waving_hand:

  1. DNS propagation can take days. If the current frontend is a webapp/has-app features make sure caches will invalidate.
  2. Do you mean shop.mywebsite.com or literally shop.my**store.**com. Why that redundancy, shop.mystore.com makes it seem like there should be two separate stores A) mystore.com/products and B) shop.mystore.com/products . If the intent is to show a collection on the old domain how do you intend to do that if the online-sales channel points to a subdomain. See embeddable buy-buttons etc
  3. Why haveredirect to a subdomain a landing page instead of just using a a direct url to that subdomains homepage. Aside from campaigns the shop should be it’s own landing page not have yet another interstitial page creating a friction maze for customers unless there’s a specific business constraint like regional selection.
1 Like

Hi @PaulNewton

  1. Got it! I will take note of this.

  2. I meant shop.mywebsite.com. So we basically have two “fronts” - one is the shop.mywebsite.com where 90% of the products are shown, the other one is the mywebsite.com where 10% of the products are there - very selective.

  3. Hmm, I will review this point again - I don’t seem to understand it completely.