Revamp or rebuild: a WordPress and Shopify decision guide that protects your rankings

Revamp the site if the platform and the content structure still fit the business and the problems sit in design, speed or page layout. Rebuild on the same platform if the theme or the plugin and app stack blocks routine changes. Migrate only if the platform itself is the limit. In all three cases, map your current URLs and redirect each one that changes before launch, because a URL that disappears without a redirect takes its search traffic with it.

Three options, and the work each one involves

A revamp keeps your platform, your content and most of your URLs. You refresh the design and fix slow templates.

A rebuild on the same platform replaces the theme and the tooling under it. You stay on WordPress or Shopify and move the content to a clean theme. URLs can stay the same.

A migration moves the site to a different platform, for example WooCommerce to Shopify. Many URLs change, so it carries the most search risk.

How to tell which one you need

Read each row and note which column describes your site. The column you land in most often is your answer.

I recommend the smallest option that removes the blocker. A rebuild is more work than a website revamp, and a migration adds URL changes on top.

WordPress: what to check before you decide

Theme and page-builder debt. Check if your site runs a multipurpose theme with a bundled page builder. Many builders store layouts as shortcodes or their own markup inside your content, so switching themes can leave pages full of broken shortcodes. Leaving that builder means a rebuild.

Plugin sprawl. List every active plugin and its job. Look for two plugins doing the same job and plugins without recent updates. Replacing them is revamp work.

PHP and core updates. Ask your host which PHP version the site runs, and check the WordPress version in the dashboard. If updating either one breaks the theme, a visual refresh will not fix the security risk.

Theme-registered content types. Permalink settings belong to WordPress and survive a theme change. Custom post types that the old theme registers, such as "services" or "vehicles", lose their URLs unless the rebuild registers them again under the same slugs.

Shopify: what to check before you decide

Vintage theme or Online Store 2.0. Shopify calls its original theme architecture vintage themes, and those support sections on the home page only. Online Store 2.0 themes use JSON templates, so you can add and reorder sections on product, collection and other pages, and apps can add app blocks without code edits. A store on a vintage theme is a rebuild candidate.

App sprawl. Note the job and the monthly cost of each app. On older themes, an app can leave code in the theme after you uninstall it, and that leftover script still loads for shoppers. On an Online Store 2.0 theme, app cleanup plus template work is a revamp.

Checkout. Shopify no longer supports the old checkout.liquid customization method. Checkout changes now go through apps and extensions, which Shopify calls checkout extensibility. At the time of writing, Shopify reserves apps that customize the information, shipping and payment steps for Shopify Plus, while other plans can customize the thank-you and order status pages. Plan features change, so check Shopify's pricing page before you commit to a checkout design.

When to move from WooCommerce to Shopify, or the other way

A WordPress to Shopify migration makes sense if the store is the business and your team wants out of server, update and security work. Shopify hosts the store and maintains the checkout. In exchange, it fixes parts of the URL structure, and deep content models take more effort than in WordPress.

Moving from Shopify to WordPress with WooCommerce makes sense if content leads and commerce follows, if you need custom data structures or unusual integrations, or if you want full control of hosting and code. The updates and security work become yours.

Stay put if the complaint is design or speed. A new platform does not fix thin product or service pages.

The pre-launch SEO checklist

Run this list for all three options.

Before you build

1. Crawl and export all current URLs. Use a crawler, your XML sitemap, Google Search Console and your analytics tool.
2. Record the current state. Save titles, meta descriptions, H1s, canonical tags and structured data for each URL, plus rankings and organic traffic for your top pages.
3. Keep URLs where you can. An unchanged URL needs no redirect.
4. Build a 301 redirect map. A 301 is a permanent redirect that sends visitors and search engines from an old address to its new one. List each changed URL beside its closest new equivalent, one to one. Google's guide warns against sending many old URLs to the home page.

On Shopify the map is mandatory. Shopify uses fixed URL prefixes such as /products/, /collections/, /pages/ and /blogs/, so old paths cannot carry over. You can add redirects in the Shopify admin or import them in bulk from a CSV file.

Take a hypothetical auto business with a repair shop and a parts store on one WooCommerce site. The repair pages sit at /services/brake-repair/ and the parts at /shop/brake-pads/. On Shopify the parts move under /products/ and the repair pages under /pages/, so each URL changes. Shopify's URL redirect documentation also lists prefixes its redirect tool will not accept as a source, and /shop and /services are on that list. Compare the list with your URL export before you choose Shopify, and get a written plan for any URL the tool refuses.

During the build

5. Carry over on-page elements on pages that perform: titles, meta descriptions, headings, body copy and image alt text.
6. Update internal links so they point at final URLs and not at redirects.
7. Preserve structured data such as Product, LocalBusiness and breadcrumb markup, and validate it with Google's Rich Results Test.
8. Block the staging site with noindex or a password so Google does not index a duplicate.

At launch

9. Remove the noindex and check robots.txt on the live site.
10. Test the redirects. Run the old URL list through a crawler and confirm each one returns a 301 to the right page.
11. Submit the new XML sitemap in Google Search Console.
12. Check Core Web Vitals on the main templates: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift.

After launch

13. Watch for 404s in Search Console and add redirects for the ones that matter.
14. Track rankings and organic traffic for your top pages against the numbers you recorded in step 2.
15. Keep the redirects in place. Google advises keeping them as long as possible, and in general for at least one year.

Google's guide to site moves with URL changes covers the mapping, the redirects and the monitoring.

What to expect from rankings after launch

Expect rankings to move after a migration. Google's guide says to expect temporary fluctuation while it recrawls and reindexes the site. For a medium-sized site, it says new URLs can take a few weeks or more to replace the old ones, and larger sites take longer.

Investigate a broad drop that lasts beyond that window. Check first for missing redirects, a live noindex tag, changed titles and removed content. No agency, devinsta included, can guarantee that rankings hold through a migration.

When to do nothing

Leave the site alone if it brings in leads or sales, your team can edit it, and updates install without trouble. A dated look alone is a weak reason to risk pages that rank. Fix single problems instead, such as a slow template or a confusing booking form.

What devinsta does here

We at devinsta sell this work, so read the advice above with that in mind. We take on all three paths. For WordPress sites we offer WordPress development and theme engineering and migrations. For stores we offer Shopify and e-commerce development.

The redirect map, staging checks and post-launch monitoring sit under our technical SEO and CRO service. If you run a dealership or repair shop, the automotive industry page describes what we offer for those sites, and the e-commerce page does the same for stores.

You see working progress every week, and you own the code and the accounts. Request a free site audit and you get a written report within five working days, or book a free 30-minute strategy call.

Common questions

Will a website redesign hurt my SEO?

A redesign can hurt SEO if URLs change without redirects, if titles and content disappear, or if a staging noindex tag reaches the live site. Keep URLs where possible, redirect each changed URL with a 301, and carry over the on-page elements of pages that rank.

Do I need redirects if I move from WordPress to Shopify?

Yes. Shopify uses fixed URL prefixes such as /products/ and /collections/, so most WooCommerce product and category URLs change in the move. Map each old URL to its new Shopify URL and add 301 redirects before launch.

Can I keep my URLs in a rebuild on the same platform?

In most cases, yes. WordPress lets you keep the permalink structure and page slugs under a new theme, and a Shopify theme change does not alter product or collection URLs. Crawl the staging site and compare its URL list with the live one to confirm.

Should I revamp or rebuild a site that still ranks well?

If the site ranks and your team can edit it, a revamp of the weak templates protects what works. Choose a rebuild only if the theme or the plugin and app stack blocks updates or routine changes.