Every disastrous store launch we’ve been called in to rescue shares a trait: nobody checked the boring things. The design got twelve review rounds; the redirect map got none. This is the pre-launch checklist we actually run — for first builds and, doubly, for replatforms and redesigns, where the expensive mistakes hide.
1. Redirects — the rankings insurance
If any URL is changing (replatform, restructure, even renamed collections), every old URL needs a 301 to its closest new equivalent — not to the homepage, which Google treats as a soft 404. Export the old sitemap, map every URL, spot-check the top 100 traffic pages by hand, and keep the map versioned. Rankings survive perfect redirect maps and punish sloppy ones for months. This is the single highest-stakes item on the list.
2. Tracking — measure from minute one
- GA4 receiving e-commerce events (view_item, add_to_cart, begin_checkout, purchase) with correct values and currency.
- Meta pixel plus Conversions API, deduplicated; Google Ads conversion tags or enhanced conversions wired.
- Search Console verified on the live domain, sitemap submitted the day you launch.
- One real test purchase traced through every system — the ₹100 that saves lakhs in unmeasured spend.
3. Commerce plumbing
Payments in live mode with a real card tested (and refunded), UPI/wallets/COD configured for your market, shipping rates checked against reality (free-shipping threshold included), taxes/GST configured, inventory synced, and transactional emails — order confirmation, shipping, refund — rebranded and test-fired. Check the checkout in Hindi/regional languages if you sell in those markets; default translations ship rough.
4. Speed and correctness budget
Launch is the cleanest your store will ever be — set the baseline now: mobile LCP under 2.5s on the home, top collection and top product page; no console errors; images in modern formats; apps limited to what’s actually used (the pre-launch app audit is the cheapest Shopify development work you’ll ever do). Screenshot the Lighthouse scores — they’re your regression alarm for everything installed later.
5. The unglamorous pages
Privacy policy, terms, returns/refund policy, shipping policy and contact page with a real address — customers check them before trusting a new store, payment providers require them, and ad platforms reject stores missing them. Write the returns policy like a human; it’s a conversion asset, not legal wallpaper.
Run launch as a rehearsal, not an event: full checklist on the password-protected store, fix everything, then a second pass on live within the first hour — test purchase, redirect spot-checks, analytics real-time view, Search Console crawl request. Keep the old platform paid up for 30 days; it’s the cheapest rollback insurance available.
6. The first week is part of the launch
Watch daily for the first week: Search Console coverage report for 404 spikes (missed redirects surface here first), site search queries (what can’t people find?), checkout funnel step conversion against pre-launch benchmarks, and Core Web Vitals field data as real traffic arrives. Most launch damage is done not by launch-day bugs but by week-one bugs nobody was watching for. A launch isn’t done when the site is live; it’s done when the data says the website design and development is performing at or above the old baseline.
Frequently asked questions
What should I check before launching a Shopify store?
The high-stakes five: complete 301 redirect mapping if URLs changed, end-to-end analytics with a traced test purchase, live payments and shipping tested with a real order, mobile LCP under 2.5s, and legal pages in place.
Will redesigning my Shopify store hurt my SEO?
Only if URLs change without perfect 301s, or ranking content gets thinned. Map every old URL to its closest equivalent, keep content parity on top pages, resubmit the sitemap — rankings typically hold.
How long should I keep my old platform after migrating to Shopify?
At least 30 days, paid and frozen. It’s rollback insurance, the reference for missed redirects and content, and the source of record for anything that didn’t migrate cleanly.
What should I monitor in the first week after launching?
Search Console coverage for 404 spikes, checkout funnel conversion by step vs old benchmarks, site-search queries for findability gaps, and Core Web Vitals field data. Week-one bugs cause more damage than launch-day bugs.
The takeaway
Launches fail on the boring things: redirects, tracking, payment plumbing, policies. Run the checklist twice — once behind the password, once live — keep the old platform for 30 days, and treat the first week of data as part of the launch. The design gets the applause; the checklist keeps the revenue.