How to change your Shopify theme without breaking anything

What is kept when you change themes

The theme is only the presentation layer. Everything in the admin stays the same: products, variants, collections, customers, orders, pages, blog posts, navigation menus, metafields, metaobjects, discounts and redirects. URLs do not change either, because Shopify defines them, not the theme.

That means a theme change done properly does not affect SEO by itself. What can affect it is the new theme showing less content, changing headings or losing structured data the previous one had.

• Products, collections and customers
• Orders and history
• Pages, blog and menus
• Metafields and metaobjects
• URLs and redirects

What is lost and has to be redone

Theme editor settings belong to each theme: colors, fonts, homepage sections, product page blocks, alternate templates. When you change themes, you have to set them up again. Code added by hand to the previous theme does not carry over either, such as custom CSS, snippets or scripts pasted into the layout.

Alternate templates deserve special attention. If you had products or pages assigned to templates like product.gift or page.contact, the new theme needs templates with the same name. If they do not exist, those products will be shown with the default template.

Apps: blocks, embeds and legacy code

Modern apps integrate through app blocks and app embeds, which you enable from the theme editor in the new theme. It is a quick step, but you need to review them one by one: reviews, filters, chat, bundles, back-in-stock alerts.

Older apps injected code directly into theme files. That code does not carry over to the new theme, and sometimes it is better that it does not: it is a good time to uninstall what you do not use and check whether the new theme or a native feature like Shopify Bundles or Search & Discovery covers what the app did.

Review your analytics too. Pixels set up from Settings > Customer events do not depend on the theme, but scripts pasted by hand into theme.liquid are lost.

How to prepare the new theme without touching the store

Add the new theme to your theme library without publishing it. That way you can customize it in the editor and see it with your real products while the store keeps running on the current theme. Duplicate the published theme first as a backup.

From the preview you can share a link with your team so they review the theme on their phones. Use it: most traffic comes from mobile and that is where problems show up.

While you prepare the new theme, note any change made to the published theme. If a banner or homepage text is changed in the current theme during those weeks, that change will not appear in the new one. The easiest approach is to freeze design changes on the published theme and stick to the essentials.

To recreate the content, start with the templates that get the most traffic: homepage, product page, collection and cart. Then content pages and alternate templates. That way, if the timeline gets tight, the important parts are ready first.

Checklist before publishing

Before publishing, go through the store as a customer would and as Google would. These are the points most often forgotten:

• Product page with correct variants, prices and availability
• Alternate templates recreated with the same name
• Metafields visible where they were shown before
• App blocks and embeds enabled
• Cart, cart drawer and a full test purchase
• Product titles, headings and structured data
• Pixels and analytics working
• Mobile version reviewed on real devices

Publish and monitor

Publishing a theme is instant and the previous one stays in the library. If something breaks, you can republish the old theme in seconds while you fix it. Pick a low-traffic moment and avoid doing it right before a campaign.

Over the following days, review conversion, internal searches, speed with Core Web Vitals and Search Console. If conversion drops, compare the funnel with the previous theme's: the cause is often a detail on the product page or cart, not the whole theme.

Theme Store theme or custom theme

If you switch to a Theme Store theme, you gain speed but inherit its structure and limits. A custom Online Store 2.0 theme is built with the sections your store needs and nothing more, which usually means better performance and fewer apps to fill gaps.

Before choosing, check that the candidate theme is Online Store 2.0, with sections on every template and support for app blocks, and look at how it handles the product page and cart on mobile with your real products, not the demo ones. A demo with perfect photos and few products hides many problems that appear with a real catalog.

In both cases the method is the same: prepare without publishing, review, publish with a rollback plan and measure.