Not every 404 has the same value
Old URLs with traffic, backlinks, revenue or internal links need attention first. Low-value retired URLs should not distract from priority losses.
Redirects must preserve intent
A redirect that sends an old category to the homepage may return 301 and still fail commercially.
Validation matters after upload
Redirect maps should be crawled after launch and compared against Search Console, analytics and server responses.
A 404 list is not a recovery plan
A Shopify migration can create hundreds or thousands of 404s. The list looks urgent, but the real job is prioritisation.
An old product with no traffic and no links is not equal to a category URL that drove revenue for years. Treating them equally wastes the first recovery window.
Start with value
Group old 404s by evidence: Search Console clicks, backlinks, revenue, internal links, product/category role and current replacement page. Priority URLs need matching destinations, not generic redirects.
Use this order when the list is long:
| 404 type | First question | Likely action |
|---|---|---|
| Old category with clicks or backlinks | Is there a matching Shopify collection? | Build or improve the collection, then redirect one-to-one |
| Old product with revenue or links | Is there a replacement product or close alternative? | Redirect to the replacement product or strongest relevant collection |
| Old guide or blog post | Did it support product discovery? | Rebuild, consolidate or redirect to a useful guide |
| Old filter or tag URL | Did it earn meaningful search demand? | Decide whether it needs a collection, a noindex state or retirement |
| Junk/search/account URL | Did anyone valuable use it? | Usually leave, block or retire deliberately |
This keeps the first recovery pass focused on URLs that can still affect traffic, revenue or crawl signals.
Preserve intent
A retired category should usually redirect to the closest matching Shopify collection. A discontinued product may redirect to the replacement product, parent collection or a useful alternative. Blog and guide pages need content-sensitive decisions.
The test is simple: if someone clicked the old result from Google, would the new page still feel like a fair answer?
Bad redirect:
/product-category/wide-fit-boots/->/
Better redirect:
/product-category/wide-fit-boots/->/collections/wide-fit-boots/
Acceptable fallback if the exact collection does not exist:
/product-category/wide-fit-boots/->/collections/boots/, with internal links and copy that still helps wide-fit shoppers
The fallback is weaker than a proper destination, but it is usually better than hiding the problem behind a homepage redirect.
Example
An old WooCommerce category /product-category/wide-fit-boots/ returns 404 after launch. Redirecting it to the homepage is technically quick and strategically weak. The safer destination is the new wide-fit boots collection, rebuilt with products and buying guidance.
Another example:
An old product is discontinued, but it still has backlinks from a review site. Sending it to a generic sale page wastes the link and confuses shoppers. A better choice is a replacement product if one exists, or a parent collection with a note that helps users find the current alternative.
When a 404 is acceptable
Not every missing URL needs to be rescued.
A 404 or 410 can be fine when the old page had no useful search value, no links, no internal support and no relevant replacement. The mistake is not the status code itself. The mistake is letting valuable pages fall into the same bucket as junk URLs.
For old URLs with evidence, make the decision visible:
- keep and redirect
- merge into a stronger page
- rebuild as a Shopify collection
- redirect to a replacement product
- retire deliberately
- investigate before deciding
That record matters later when Search Console starts reporting losses.
What not to do
Do not bulk redirect everything to the homepage. Do not fix low-value 404s before high-value category losses. Do not assume a redirect plugin import worked until the map has been crawled. Do not edit content before the old URL destination is repaired.
Safer next step
Export old 404s, score them by value, map priority URLs to intent-matched destinations and crawl the finished redirect map before interpreting recovery.
If you need a printable review sheet, download the Migration Redirect Risk Review.
Quick answer
Protect search equity during a Shopify migration by turning the old site into an evidence map before URLs, templates or tracking change.
What you will do
- Know which old URLs must be protected.
- Build redirects before launch pressure starts.
- Keep metadata, analytics and Search Console evidence available after the move.
- Reduce the risk of avoidable traffic loss.
What to check first
- Crawler export for the old site and Shopify staging site.
- Google Search Console page, query and indexing exports.
- GA4 annotations and landing-page reports.
- Shopify URL redirects.
- Redirect Mapping Sheet, Migration QA Checklist and Post-Migration Monitoring Sheet.
Work through it in this order
- Crawl the current site and export all indexable URLs.
- Export Search Console pages and queries for at least the last 16 months where available.
- Tag each old URL as protect, merge, replace, retire or investigate.
- Map protected URLs to the closest Shopify destination before launch.
- Copy or improve critical titles, descriptions, headings, content blocks and internal links.
- Test redirects, canonicals, sitemap output, robots rules and tracking on staging.
- Monitor Search Console, analytics and 404 logs for four weeks after launch.
Real-world notes
- The most common failure is redirecting old category URLs to the homepage because the Shopify collection structure was not ready.
- Traffic drops often look like ranking problems when the real issue is missing tracking, missing redirects or changed internal links.
- Blog URLs are easy to ignore during ecommerce migrations, but they often carry internal links and long-tail traffic.
Final checks
- Old URL crawl saved.
- Search Console export saved.
- Top landing pages mapped.
- Redirects uploaded and tested.
- Metadata for priority pages reviewed.
- Analytics and conversion tracking checked.
- Post-launch monitoring owner assigned.
Watch-outs
- If the old site has faceted URLs indexed, decide which should become Shopify collections and which should be retired.
- If products are discontinued during migration, redirect only where the replacement is genuinely useful.
- If the domain changes as well as the platform, follow a stricter site-move process and expect a longer stabilisation period.
Download the Migration Risk Kit or request an audit if organic revenue, product count or URL complexity is high.
Field questions
What is the first check for Shopify migration 404 errors?
Start with the affected URLs and page types, then compare crawl access, redirects, indexation, content strength and trusted measurement before changing pages.
Should I rewrite content first?
Usually no. Rewriting content before URL, indexation, tracking or page-type evidence is trusted can hide the real issue.
What data should I keep?
Keep the URL list, Search Console landing pages, analytics baselines, revenue pages, backlinks, crawl exports, redirects and launch notes.
Can this affect AI visibility?
Yes. AI-shaped discovery is more likely to reflect confusion when URLs, categories, product evidence and merchant data are inconsistent.
When should this be reviewed?
Review it before launch, immediately after launch, and again when Search Console has enough new data to show whether important pages are recovering.
What is the common mistake?
The common mistake is treating a symptom as the cause and making broad changes before the failed page type has been isolated.
Should every old URL be redirected?
No. Important URLs should be mapped carefully. Truly worthless URLs can return 404 or 410, but that decision should be deliberate.
Is a homepage redirect safe?
Usually not for important old pages. It often weakens intent and can behave like a soft failure.
