Start with data, not design
Before you open the editor, look at what is happening in your current store. In Shopify's reports and your analytics tool, check which pages get the most traffic, which devices people buy from, at which funnel step they drop off and which product pages convert best. In Search Console, check which pages bring organic traffic and for which searches.
That analysis tells you what to protect and what to improve. If most traffic is mobile, the redesign is designed mobile first. If one collection drives most sales, you do not change its structure without a reason. A redesign without prior data only changes the look, and you have no way of knowing whether things got better or worse.
What changes and what does not when you switch themes
In Shopify, the URLs of products, collections, pages and blog posts depend on each item's handle, not on the theme. Changing themes does not alter URLs, products, customers or orders. That removes much of the SEO risk a redesign carries on other platforms.
What does live in the theme is section content (text, images and blocks on the homepage and landing pages), product and collection templates, code added by some older apps, the structured data the theme generates and any customization made in the code. All of that has to be reviewed and carried over.
Work on a parallel theme
The redesign is built on an unpublished theme in the same store, or in a development store if the change is large. Meanwhile, the live store keeps selling. From the theme library you can preview the new theme with your real products and share the preview link with whoever needs to review it.
Save a copy of the current theme before publishing the new one. If something goes wrong, rolling back is a matter of publishing the previous theme again. If the theme is managed with version control and the GitHub integration, you also get the history of every change.
Content, metafields and apps
Carry over section text and images carefully. A good redesign takes the chance to pull repeated information out of descriptions and into metafields and metaobjects, so product pages fill themselves and your team does not have to lay out each product by hand.
Review your apps too. With Online Store 2.0 themes, most integrate as app blocks or app embeds that you turn on from the editor, but some older ones left code in the theme that needs cleaning up. It is also a good time to uninstall the ones you no longer use.
- Homepage and landing page text and images
- Assigned alternate product and collection templates
- Active app blocks and app embeds
- Leftover code from uninstalled apps
- Tracking pixels and customer events
- Headings, structured data and internal links
SEO: what you must not break
Even if URLs do not change, a redesign can affect SEO if you lose collection copy that was ranking, if headings change on important pages, if internal links disappear or if the new theme does not generate the same product structured data. Compare your key pages before and after.
Watch speed as well. A flashier theme with videos, carousels and heavy fonts can hurt Core Web Vitals. Measure performance on the preview before publishing and fix whatever needs fixing.
If the redesign changes the navigation structure or removes pages or collections, then some URLs do disappear. In that case, create 301 redirects from each removed URL to the closest page, so you do not lose traffic or backlinks.
Testing before launch
Go through the whole store as a customer would, on mobile and desktop: search, filter, choose a variant, add to cart, apply a discount and reach checkout. Place a complete test order. Also check customer accounts, forms and languages if you sell in several markets.
Check that analytics and pixels record visits, add-to-carts and purchases with the new theme. A tracking failure can make you think the redesign performs worse than it actually does.
Launch and measure
Publish at a low-traffic time and away from big campaigns. Over the following days, monitor conversion rate, add-to-cart rate, checkout abandonment and errors in Search Console, comparing them with the previous period. Fine-tuning details in the first few weeks is normal.
At Weblineo we build redesigns as custom code on a development store, review the V1 with you before publishing, and include training and 30 days of support afterwards.
Frequently asked questions
Does changing themes in Shopify affect SEO?
It does not change URLs, which is the most sensitive part. It can have an effect if you lose copy, headings, internal links or structured data, or if the new theme is slower. Review those points before publishing.
Can I go back to the previous theme if something goes wrong?
Yes. The previous theme stays in the theme library and you can publish it again at any time. Always save a copy before making changes.
Will I lose my app settings?
App data is kept, but you have to turn on and place their blocks and embeds in the new theme. Apps that injected older code may need a review.
Is it better to redesign or improve step by step?
If the theme's foundation is good, gradual improvements are safer and easier to measure. A full redesign makes sense when the theme is old, slow or keeps you from working with sections and metafields.
Can I keep selling while the redesign is underway?
Yes. The new theme is built unpublished or on a development store, and the live store keeps running as usual until the day the new design is published.