Ecommerce Website Redesign Checklist: Keep Rankings and Revenue

An ecommerce website redesign keeps its rankings and revenue when four things survive the launch: URLs (or proper redirects), the content and structured data search engines rely on, analytics and conversion tracking, and page speed. Most redesign losses come from one of those breaking quietly, not from the new design itself. Plan a rollback before you launch, and compare against a baseline you captured before any work started.

The checklist below is split into before, during and after launch. If your redesign also changes domain, platform or URL structure, use it alongside our SEO site migration checklist.

Before: baseline and scope

Capture a baseline

• Export organic landing pages, queries and clicks for the last 12 months from Google Search Console.
• Record conversion rate, revenue and average order value by device and channel from analytics.
• Record field Core Web Vitals per page type (home, category, product, cart, checkout).
• Crawl the current site and save the output: URLs, status codes, titles, meta descriptions, canonicals, headings, structured data, internal links.
• Note your top 100 to 200 revenue and traffic pages; they get extra checks later.

Decide what is changing

If you are choosing a new Magento front end as part of the redesign, see Hyvä vs Breeze vs Luma for the trade-offs.

Assign owners

Redesigns fail at the handoffs between teams. Name one owner for each area before work starts:

• SEO: baseline, redirect map, template rules and post-launch monitoring
• Analytics: tag inventory, data layer and purchase reconciliation
• Development: theme build, performance budget, deployment and rollback
• Merchandising and content: category copy, product content and navigation labels
• Operations: payment, shipping and order flow testing with the ERP or warehouse

During: build with parity in mind

URLs and redirects

• Keep existing URLs wherever possible. A redesign does not need new URLs.
• For any URL that must change, map old to new one-to-one, to the closest equivalent page, not the home page.
• Use server-side permanent redirects (301 or 308). Google recommends keeping redirects for as long as possible, generally at least one year.
• Avoid redirect chains; point old URLs straight to final destinations.

Content and template parity

• Category intro copy, product descriptions, specifications and FAQs must still render, and render in the HTML rather than only after user interaction.
• Titles, meta descriptions, H1s and canonical tags must match the agreed templates.
• Product structured data (Product, Offer, AggregateRating where applicable) and breadcrumbs must still validate.
• Internal links from navigation, footers and related products should not shrink drastically; the new menu often removes links that mattered.
• Image alt text and file names should carry over.
• Pagination, layered navigation and indexing rules should match the current setup unless you are deliberately changing them.

Tracking

• List every tag and event: analytics, ads conversion tags, server-side events, consent banner, heatmaps.
• Rebuild the data layer for new templates, especially add-to-cart, checkout steps and purchase.
• Check consent mode and cookie behavior again; a new theme can load tags before consent.
• Test purchase events with real test orders and compare with Magento order totals.

Speed and accessibility

• Test staging against Core Web Vitals "good" thresholds: LCP 2.5 s or less, INP 200 ms or less, CLS 0.1 or less, at the 75th percentile.
• Set a budget for third-party scripts before design sign-off.
• Check keyboard navigation, focus states, color contrast, form labels and alternative text against WCAG 2.2. Our ecommerce accessibility guide covers the European Accessibility Act and what it means for online stores.

Pre-launch QA

• Crawl staging (with authentication) and compare against the baseline crawl.
• Test the redirect map automatically: every old URL returns one hop to a 200 page.
• Place orders with each payment and shipping method, on mobile and desktop.
• Check robots.txt, the XML sitemap and noindex tags. Staging rules must not go live.

Launch: the rollback plan

Decide before launch day what would make you roll back and how. A rollback plan should include:

• A deployable copy of the previous theme and configuration, tested on staging
• A database backup and a plan for orders placed after launch
• Clear triggers, such as checkout failure, payment errors, a large conversion drop or severe tracking loss
• A named person who can make the call, and a launch window with developers available

Launch early in the week and avoid peak trading periods. Freeze other changes, such as promotions and extension updates, for the launch window so you can attribute any problems.

After: monitor and fix

Some ranking movement is normal while search engines recrawl. Google notes that after URL changes it can take a few weeks or more for the new URLs to replace old ones, longer for large sites. A sharp drop on specific page types usually points to a template problem you can fix.

Common redesign mistakes

• Removing category copy because it "clutters" the new design
• Launching with staging noindex tags or a blocking robots.txt
• Rebuilding tracking last, then losing weeks of conversion data
• Large hero images and new scripts that push LCP and INP into "poor"
• Redirecting all old URLs to the home page

Frequently asked questions

Will a redesign hurt my SEO?

Not if URLs, content, structured data and internal links are preserved or properly redirected. Losses usually come from changes made without checking them.

Should I change URLs during a redesign?

Only when there is a clear benefit. Separating a redesign from a URL restructure makes problems easier to diagnose.

How long should I monitor after launch?

Closely for the first month, and against last year's figures for at least three months.

Next step

Mistri's Magento theme redesign service builds new themes with this checklist built in, and our Magento SEO team can own the baseline, redirect map and post-launch monitoring.

Sources

Site moves with URL changes (Google Search Central); Web Vitals (web.dev); Web Content Accessibility Guidelines (WCAG) 2.2 (W3C).