A Shopify launch or redesign can improve branding, navigation and conversion, but it can also damage organic visibility when URLs, redirects, canonicals, internal links or indexation settings are overlooked. This technical SEO checklist for Shopify is designed for new stores, theme changes, platform migrations and major site restructures.
The safest approach is to record the existing site before changing it, make reversible updates in a development theme, test important URLs and monitor the store immediately after launch.
Who should use this Shopify technical SEO checklist?
- Merchants launching a new Shopify store.
- Stores migrating from WordPress, WooCommerce, BigCommerce or another platform.
- Teams publishing a new Shopify theme.
- Merchants changing domains or URL structures.
- Stores consolidating products, collections or blog content.
- Agencies reviewing a redesign before launch.
Phase 1: Build a pre-launch inventory
Crawl and export the current site
Record all indexable URLs, titles, meta descriptions, status codes, canonicals, headings, structured data, word counts and internal links. Keep this export as the baseline for redirect mapping and post-launch comparison.
Export performance data
Save recent Google Search Console data for pages and queries. Identify URLs with clicks, impressions, links, conversions or strategic value. These pages require extra protection during migration.
Record analytics and tracking
Document the current analytics property, Google Search Console verification, advertising pixels, consent settings and key conversion events. A launch should not accidentally interrupt measurement.
Back up theme and DNS information
Duplicate the existing Shopify theme and record domain DNS entries before making changes. Do not modify email-related records during a website-only DNS update.
Phase 2: Plan URLs and redirects
| Old URL situation | Recommended action |
|---|---|
| Page remains relevant and unchanged | Preserve the existing URL |
| Page moves to a new path | Create one direct 301 redirect |
| Several weak pages are consolidated | Redirect each old URL to the consolidated page |
| Product is permanently unavailable with no replacement | Evaluate traffic, links and user value before removing; avoid irrelevant redirects |
| URL was never valid | Allow a proper 404 unless a relevant destination exists |
Avoid redirect chains
Old URL A should redirect directly to final URL C, not through intermediate URL B. Chains slow crawling and make future maintenance harder.
Preserve high-value handles
Changing a title does not require changing the handle. Keep established URLs when the page purpose remains the same.
Phase 3: Check crawlability and indexation
- Confirm the storefront is not password-protected at launch.
- Review robots.txt behavior and ensure important pages are not blocked.
- Confirm canonical tags point to the preferred URLs.
- Check that draft, duplicate, search and filtered URLs are not being promoted as primary pages.
- Verify that the XML sitemap is available and includes the intended live resources.
- Submit or refresh the sitemap in Google Search Console.
- Check important pages with URL Inspection after launch.
Phase 4: Audit page templates
Homepage
The homepage should have one clear H1, accurate metadata, crawlable navigation and meaningful links to important feature, collection or service pages.
Product pages
Verify titles, product descriptions, availability, images, alt text, canonicals, structured data and variant handling. Avoid importing empty or placeholder descriptions.
Collection pages
Collections need unique titles and useful introductory content when they target search demand. Check pagination, filters and internal links.
Blog articles
Each article should have visible body content, one theme-generated H1, descriptive H2/H3 headings, working images, an author, related links and a relevant CTA.
Information pages
About, Contact, FAQ, Privacy, Terms and support pages strengthen user trust and should be reachable through navigation or the footer.
Phase 5: Validate structured data
Test representative templates rather than assuming one successful page means every page is correct. Review product, article, breadcrumb and organization markup where applicable.
- Structured data must match visible page content.
- Prices and availability must reflect the live offer.
- Do not add review ratings that are not genuinely displayed and supported.
- Avoid duplicate schema from several apps and the theme.
- Warnings should be evaluated; errors should be fixed before launch when they affect eligibility or accuracy.
Phase 6: Review internal linking and navigation
- Every important page should be reachable within a reasonable number of clicks.
- Navigation labels should describe destinations clearly.
- Update links that still point through old redirects.
- Remove links to deleted, draft or inaccessible resources.
- Link supporting blog posts to their pillar pages.
- Link informational content to a relevant conversion destination.
- Check breadcrumbs and related-content components.
Phase 7: Test performance and mobile usability
Theme changes can introduce oversized images, unnecessary scripts, layout shifts and slow interactions. Test representative pages on real mobile devices as well as performance tools.
Images
- Use appropriately sized files.
- Prefer modern formats where supported.
- Set meaningful alt text.
- Lazy-load below-the-fold content.
- Avoid broken external image URLs.
Theme and apps
- Remove unused app embeds and scripts.
- Check that popups do not block important mobile content.
- Test menus, accordions, forms and buttons.
- Confirm text contrast and tap-target size.
- Review layout shift caused by banners, fonts or media.
Phase 8: Run a pre-launch QA crawl
Crawl the development or preview environment where access allows. Compare it with the original inventory and review:
- Unexpected 404 or 5xx pages.
- Missing titles or descriptions.
- Duplicate titles and canonicals.
- Empty body content.
- Broken images.
- Links to staging or old domains.
- Noindex directives on intended live pages.
- Redirect loops and chains.
- Orphaned strategic pages.
Phase 9: Launch safely
- Confirm the final redirect map is ready.
- Take a last backup of the current theme and settings.
- Publish the approved theme only when QA is complete.
- Apply domain or DNS changes carefully without altering unrelated email records.
- Remove storefront password protection when appropriate.
- Test the homepage, top landing pages, forms and important user journeys.
- Run a fresh crawl immediately.
- Submit the sitemap and inspect priority URLs.
Phase 10: Monitor after launch
First 24 hours
Check uptime, analytics, conversions, major redirects, robots rules, canonicals and top URLs.
First week
Review Search Console indexing, crawl errors, sitemap processing, ranking changes and page-level traffic. Fix systemic issues before making broad content changes.
First month
Compare performance against the pre-launch baseline. Investigate declines by template, directory, device and query rather than assuming every change has the same cause.
Technical SEO launch checklist
- Current URLs and performance data exported.
- High-value pages identified.
- Redirect map completed and tested.
- Canonical tags verified.
- Robots and noindex settings reviewed.
- XML sitemap available.
- Metadata and headings checked.
- Images load and have alt text.
- Structured data validated.
- Internal links updated.
- Analytics and Search Console verified.
- Mobile templates tested.
- Development theme approved before publication.
- Post-launch monitoring schedule prepared.
How CWS fits into the launch process
Technical SEO makes content accessible, while content quality determines whether pages satisfy search intent. CWS can help Shopify merchants prepare blog content, product descriptions, keyword plans and content calendars before or after a launch.
Explore the CWS feature set, review the SEO Copilot, or visit CWS on the Shopify App Store.
Frequently asked questions
Should Shopify URLs be changed during a redesign?
Only when there is a clear reason. Preserving valuable URLs usually reduces migration risk.
When should redirects be created?
Prepare and test them before launch so old URLs resolve correctly as soon as the new structure is live.
Does a new theme automatically improve SEO?
No. A theme can improve usability and performance, but it can also introduce technical or content problems. Test it before publication.
How long should post-launch monitoring continue?
Monitor closely during the first days and weeks, then continue reviewing Search Console and analytics as part of regular SEO maintenance.