Commercial disclosure: this page may mention Shopify. Recommendations should be weighed against the stated testing status and native Shopify alternatives. See the affiliate disclosure.
Desk Researched. Last reviewed 2026-05-02.
Commercial fit
Tools and partners mentioned here
These mentions support the site commercially only where a tested use case, migration route or practical SEO workflow justifies them.
Shopify
Affiliate link activeHigh-intent platform comparisons, migration planning and audit enquiries.
Quick answer
Run crawl and indexing checks before and after a Shopify migration so the team can prove which old URLs existed, which new URLs replaced them, and which pages are crawlable, indexable and internally linked after launch.
What you will do
- Save old-site crawl evidence before migration work changes the source site.
- Catch staging noindex, canonical, robots, sitemap and template problems before launch.
- Use live crawl evidence to fix redirect chains, 404s and indexation gaps quickly.
Tools and setup
- Screaming Frog, Sitebulb or an equivalent crawler.
- Google Search Console page, query and indexing exports.
- GA4 or Shopify reports for landing-page value.
- Backlink export for URLs that may not appear in the current crawl.
- Shopify sitemap, robots.txt and URL redirect controls.
Step-by-step process
- Crawl the old site and export indexable URLs, status codes, titles, meta descriptions, canonicals, H1s and inlinks.
- Merge the crawl with Search Console, analytics and backlink exports so commercial URLs are not treated like low-value crawl noise.
- Crawl the Shopify staging store and check product, collection, blog and page templates for indexability, schema, links and password/noindex leftovers.
- Prepare an old-URL test list from the top organic, revenue and backlinked pages.
- After launch, crawl the live domain, sitemap URLs and old high-priority URL list.
- Fix one-hop redirect failures, unexpected 404s, noindex/canonical mistakes and sitemap-only orphan pages before lower-value warnings.
- Keep the old, staging and live crawl exports in the migration evidence folder.
Real-world notes
- Old category pages often vanish because the new Shopify collection structure was built from product imports rather than search demand.
- Staging crawls regularly catch noindex tags, password remnants and app schema conflicts before anyone notices in Search Console.
- A post-launch crawl can reveal that internal links still point through old redirected URLs even when the redirect map itself works.
Checklist
- Old site crawl saved before migration changes.
- Search Console and analytics data merged into URL list.
- Staging crawl reviewed for noindex, canonical, robots and schema issues.
- Top old URLs tested after launch.
- Redirect chains and loops reviewed.
- Live sitemap URLs crawled.
- 404s prioritised by traffic, links and revenue.
- Crawl exports stored with launch date.
Edge cases
- If stock sync unpublishes products after launch, crawl data may show sudden 404s that are actually inventory workflow problems.
- If an app creates filter or search-result pages, the crawl may expose index bloat that the original migration plan never considered.
- If old redirects existed in WordPress, Shopify imports can create chains unless the final destination is mapped directly.
Run this crawl pass before final redirect QA, then use the traffic-drop guide if Search Console movement looks abnormal.
A crawl is migration evidence, not a vanity audit
Crawl checks prove whether important old URLs, new Shopify destinations, redirects, canonicals, indexability and internal links behave the way the migration plan says they should.
Run separate crawls for old, staging and live
The old site crawl captures what must be protected. The staging crawl catches Shopify template and indexability mistakes. The live crawl confirms redirects, canonicals, robots and sitemap output after launch.
Crawl data needs commercial context
A crawler will not know which URLs earn revenue or links. Merge crawl data with Search Console, analytics and backlink evidence before deciding what matters.
The Three Crawl Files To Save
Create three separate crawl exports:
- Old site crawl: current WooCommerce or WordPress URLs before migration work changes them.
- Shopify staging crawl: password-protected or preview store checks before launch.
- Live launch crawl: final domain after redirects, theme, robots, sitemap and tracking are live.
Keep them separate. Do not overwrite the old crawl after launch. When traffic drops, the old crawl is often the only proof of what existed before the move.
Old Site Crawl Setup
In Screaming Frog, Sitebulb or another crawler:
- crawl the canonical old domain;
- include subdomains only if they are part of the ecommerce journey;
- crawl XML sitemap URLs as well as discovered URLs;
- export indexable HTML URLs;
- export titles, meta descriptions, H1s, canonicals and status codes;
- export internal inlinks for priority pages;
- export images only if image search, media URLs or product image migration matter.
Then merge the crawl with:
- Search Console landing pages and queries;
- GA4 organic landing pages and revenue;
- backlink exports;
- product/category exports;
- existing redirect lists;
- paid or email landing-page URLs.
A crawler can tell you a page exists. It cannot tell you whether the page pays the bills.
Shopify Staging Crawl Setup
Before launch, crawl the Shopify staging or preview version where possible.
Check:
- homepage, product, collection, blog and page templates;
- noindex tags from staging tools or theme settings;
- canonical tags;
- product schema and breadcrumb schema;
- collection product links;
- pagination or load-more behaviour;
- filtered collection URLs;
- empty collections;
- unpublished products;
- theme-generated duplicate H1s;
- app-generated pages or scripts.
Staging crawls often reveal issues that are easy to fix before launch and painful afterwards: password remnants, missing collection copy, app schema conflicts, thin product templates and internal links pointing to old URLs.
Live Launch Crawl
After launch, crawl:
- the final canonical domain;
- the submitted sitemap URLs;
- the old high-priority URL list;
- top old organic landing pages;
- old product and category URL samples;
- blog and guide URLs;
- redirect chains and 404s.
For old URLs, record:
| Check | Pass condition |
|---|---|
| Status | Old URL returns a 301 or intentional 404/410 |
| Destination | Redirect lands on the closest useful Shopify URL |
| Hop count | One hop for priority URLs |
| Final status | Destination returns 200 |
| Indexability | Destination is indexable where intended |
| Canonical | Canonical matches the preferred Shopify URL |
| Internal links | New site links to final URLs, not old redirected URLs |
What Usually Breaks
In real migrations, crawl QA often catches:
- old category URLs redirecting to the homepage;
- product URLs redirecting to collections even when replacement products exist;
- redirect chains caused by old WordPress redirects plus Shopify redirects;
- staging noindex tags left on live templates;
- Shopify collections blocked or canonicalised unexpectedly;
- app-generated filter URLs entering crawl paths;
- old blog URLs forgotten because the team focused only on products;
- products disappearing because stock sync unpublished them;
- product schema duplicated by theme and review apps;
- sitemap URLs that exist but are weakly linked from navigation.
The crawl does not fix these issues. It gives the migration team evidence before the damage compounds.
Crawl Review Order
Review in this order:
- Top old organic landing pages.
- URLs with backlinks.
- Revenue-driving landing pages.
- Product and collection templates.
- Blog and guide URLs.
- Redirect chains and loops.
- 404s with evidence.
- Canonical and noindex patterns.
- Filter and parameter URLs.
- Sitemap-only URLs with weak internal links.
Do not spend the first hour debating hundreds of low-value URLs while the old top category page returns a homepage redirect.
Suggested Next Reads
- Shopify redirect mapping guide
- Shopify migration QA checklist
- Shopify SEO traffic drop after migration
- Shopify URL structure for SEO
Sources Used
- Google Search Central: site moves with URL changes
- Shopify URL redirects
- Shopify sitemap guidance
- Shopify robots.txt guidance
Field questions
Should I crawl the old WooCommerce site before moving to Shopify?
Yes. Crawl the old site before URLs, navigation, content or plugins change. Keep the export because it becomes the source list for redirects, metadata checks and post-launch 404 monitoring.
What should I crawl after Shopify launch?
Crawl the final domain, high-priority old URLs, sitemap URLs, top organic landing pages and a sample of product, collection, blog and page templates.
Can Search Console replace a migration crawl?
No. Search Console is essential, but it lags and does not replace a controlled crawl of old URLs, staging URLs and live redirects.