E-Commerce Nov 19, 2026

Ecommerce Replatforming SEO: Redirect Acceptance Test Before Go-Live

Ecommerce Replatforming SEO: Redirect Acceptance Test Before Go-Live

Time to read: 11 minutes

Content

  1. The redirect acceptance sheet
  2. Build the URL inventory from logs, Search Console, analytics and backlinks
  3. Map by intent: one-to-one, patterns, consolidations and retired pages
  4. Platform constraints that shape the map: Shopify, Adobe Commerce, Shopware, BigCommerce
  5. Run the acceptance test on staging: one hop, 200, canonical, sitemap, hreflang
  6. Cutover day and the first 28 days: what to watch and when to act
  7. Who signs off: SEO, engineering and the business owner
  8. What our migration projects show
  9. Exceptions
  10. Test the result
  11. FAQ
  12. Your next step
Bookmark

Before the DNS switch, prove on staging that every old URL that earns clicks, links or revenue answers with one permanent redirect to its closest new equivalent, and that the destination is a live, indexable, self-canonical page listed in the new sitemap. The SEO lead owns that proof, the engineering lead runs it, and the head of ecommerce makes the go/no-go call on its results.

Treat search continuity as a go-live gate, not a post-launch fix. Replatforming often changes URL patterns, templates and content in one release, the combination Google warns about: combine a move "with a redesign of the site's content and URL structure" and you "will probably see some traffic loss as Google might need to relearn and reassess the individual pages". Even a clean move can bring "ranking fluctuations while Google recrawls and reindexes your site." So aim narrower than "no change": remove avoidable errors before launch (missing, chained or irrelevant redirects, stray noindex rules, stale canonicals), then measure the new site against a pre-move baseline.

Below: the sheet, its crawler checks, go/no-go thresholds and a 28-day watch list. The example is fictional.

The redirect acceptance sheet

Keep one row per old URL that matters:

ColumnWhat to recordPass condition
Old URL, page typeProduct, category, content, filter or mediaOne protocol, host, slash and case rule
WeightClicks over 16 months, referring domains, revenueRanks rows; sets thresholds
New URL, rule type1:1, pattern, consolidation, intentional 404/410Chosen by intent
RedirectStatus code, number of hopsOne 301 or 308 hop
DestinationStatus, robots rules, canonical200; indexable; canonical to itself
Sitemap, hreflangNew sitemap; language alternatesListed; every alternate links back
Result, ownerPass, fail or accepted exceptionNo failure without an owner

Illustrative example (fictional). An outdoor-gear retailer moves 18,000 URLs from Magento 2 to Shopify Plus. The inventory finds 1,240 URLs with clicks in the last 16 months and 310 with external links. Category paths such as /men/jackets.html become /collections/mens-jackets, and product URLs gain /products/. A sample of the filled sheet:

Old URLWeightRuleNew URLStaging resultOwner
/men/jackets.html9,800 clicks; 41 linking domains1:1/collections/mens-jacketsPass: one 301, then 200, self-canonical, in sitemapSEO lead
/trail-runner-gtx.html2,100 clicks; 6 linking domainsPattern: one rule generates 14,000 product rows/products/trail-runner-gtxPassEngineering lead
/men/jackets.html?feature=waterproof1,450 clicksManual: one of 60 filter URLs with traffic/collections/mens-waterproof-jacketsPass, tested explicitlySEO lead
/tents/alpine-2p.html (line discontinued)640 clicks; 3 linking domainsConsolidation to the closest category/collections/tentsPass; not the homepageMerchandising lead
/sale/winter-2023.html310 clicks; 9 linking domains1:1/collections/saleFail: two hops through an old Magento redirectEngineering lead
/catalog-request.html (print catalog retired)12 clicksIntentional 410NonePass: 410SEO lead

The first staging crawl failed 37 URLs, all chains through the old platform's redirect table. Each was remapped straight to its final destination and passed on the second run.

Write the go/no-go thresholds down before the first crawl; they are your team's decision. A workable set:

The crawler test spec

Request every old URL in the sheet without following redirects. For each row, the crawler checks:

  1. The old URL returns 301 or 308, or the intended 404 or 410.
  2. The Location header equals the sheet's new URL after normalization.
  3. Exactly one hop: the new URL does not redirect again.
  4. The new URL returns 200.
  5. No noindex in the robots meta tag or X-Robots-Tag header, and no block in the production robots.txt.
  6. The canonical points to the URL itself. Google: "Each new URL should have a self-referencing rel="canonical" <link> tag."
  7. The URL is listed in the new XML sitemap.
  8. On multi-language stores, every hreflang alternate exists and links back: "If two pages don't both point to each other, the tags will be ignored."
  9. No loop, and no homepage destination unless the row says so.
Redirect acceptance flow Six steps from top to bottom: URL sources (logs, Search Console, analytics, backlinks, sitemaps, CMS export and feeds) feed a weighted inventory; each row gets a mapping rule; a staging crawl checks one permanent hop, a 200 page, self-canonical, indexable, in sitemap and hreflang pairs; a go/no-go gate requires every top-band row to pass and every other failure to be fixed or owned; a post-launch watch runs on day 1, day 7 and day 28. Redirect acceptance flow 1 URL sources Logs, Search Console, analytics, backlinks, sitemaps, CMS, feeds 2 Weighted inventory Clicks, links, revenue 3 Mapping rules 1:1, pattern, consolidation, intentional 404/410 4 Staging crawl test One 301/308 hop, then 200 Self-canonical, indexable In sitemap, hreflang pairs 5 Go/no-go gate Top band passes; other failures fixed or owned 6 Post-launch watch Day 1, day 7, day 28
From URL sources to post-launch watch: one weighted inventory, one mapping rule per row, a staging crawl of every row, a go/no-go gate (top band passes, other failures fixed or owned), then checks on day 1, 7 and 28.

Build the URL inventory from logs, Search Console, analytics and backlinks

Google's site-move guide says to "Start with your important URLs" and names where to look: sitemaps, server logs or analytics "for the URLs that get the most traffic", the links feature in Search Console "for pages that have internal and external links", your CMS, and server logs "for URLs that were visited at least once recently". Merge these sources:

Normalize before you count: one protocol and host, consistent trailing slashes and letter case, and parameters split into those that change content (filters with traffic) and those that do not (tracking, sorting). Then score the weight. In the example, thresholds apply to the 1,240 URLs with clicks and the 310 with external links; every other URL still gets its redirect.

Map by intent: one-to-one, patterns, consolidations and retired pages

Every row gets exactly one rule type:

Flatten chains while you map: old redirects plus new rules produce A → B → C. Googlebot follows chains of as many as 10 hops, yet Google advises "redirecting to the final destination directly". The sheet accepts one hop.

Use server-side permanent redirects. Google lists HTTP 301 and 308 as permanent, which means "Show the new redirect target in search results"; 302, 303 and 307 are temporary. Client-side redirects are a last resort.

Mapping rulesMapping rules: one rule type per row, one hop straight to the final destination, server-side 301 or 308 redirects, and no bulk redirects to the homepage, with 404 or 410 where nothing equivalent exists.Mapping rulesMap by intent, accept one hopOne rule type per row1:1, pattern, consolidation orintentional 404/410One hop to the finaldestinationOld redirects plus new rules formchains; redirect to the finaldestination directlyServer-side and permanentHTTP 301 or 308; 302, 303 and 307are temporaryNo bulk redirects to thehomepageNothing equivalent: return 404 or410 instead

Platform constraints that shape the map: Shopify, Adobe Commerce, Shopware, BigCommerce

The target platform decides how much of the map you can write as rules. As of November 2026, each vendor's documentation says:

Platform fit beyond URLs is covered in our Magento to Shopify migration guide, and the full project sequence in the step-by-step replatforming guide.

Run the acceptance test on staging: one hop, 200, canonical, sitemap, hreflang

Load the production redirect rules onto staging and run checks 1 to 9 above against every old URL in the sheet. Google suggests the URL Inspection tool for single URLs, "or command line tools or scripts to test large numbers of URLs". Staging often sits behind a password or a sitewide noindex: record those as staging-only results, keep the list of URLs whose noindex rules must come off (Google recommends preparing it), and repeat checks 1 to 9 on the production host right after the switch. Rerun the full crawl after every fix.

Cutover day and the first 28 days: what to watch and when to act

On cutover day, remove migration-only noindex rules and robots.txt blocks, switch the redirects on, rerun the crawl on production and submit the new sitemap in Search Console. Google also suggests submitting the old sitemap: warnings about its redirecting URLs are "normal", and its indexed count should fall as the new one's rises. Point internal links, feeds and ad campaigns at the new URLs.

Cutover dayCutover day in order: remove migration-only noindex rules and robots.txt blocks, switch the redirects on, rerun the crawl on production, and submit the new and old sitemaps in Search Console.Cutover dayThen watch day 1, day 7 and day 28Remove migration-onlyblocksNoindex rules and robots.txt blockscome offSwitch the redirects onThe production rules the stagingcrawl testedRerun the crawl onproductionChecks 1 to 9 on the production hostSubmit the new sitemapPlus the old one: its indexed countshould fall as the new one's rises

The day 1, 7 and 28 checkpoints are a team convention, not Google deadlines; Google says a small to medium-sized site "can take a few weeks for most pages to move, and larger sites take longer."

WhenCheckAct if
Day 1404 log; Page indexing report; URL Inspection on the top 20 URLsA weighted URL returns 404 or a chain: fix the same day
Day 7Sitemaps report; clicks and impressions of top URLs against the baselineIndexing stalls for one template: check its canonical and robots rules
Day 28The same comparison, plus the 404 logA weighted URL keeps losing clicks: inspect its mapping and destination

Keep the redirects: Google says "generally at least 1 year" and, for users, "consider keeping redirects indefinitely". Release windows and rollback belong in your release and rollback checklist.

Who signs off: SEO, engineering and the business owner

The sign-off artifact is the final crawl report, measured against the thresholds above.

What our migration projects show

Our case pages describe migration scope, not search outcomes. The Richter Gabelstapler Magento migration moved a B2B forklift exporter from Magento 1.7 to Magento 2.0 in four months, using the official Magento Migration Tool for products, customers, orders and the SEO setup. The myfelt case is a multilingual Magento to Shopify migration. Goddess, a Magento 1 to 2 migration, listed "Implementing the delta-migration" among its tasks and required "full-regression testing along with raw testing of each involved module". None of these pages states a search-traffic result.

This test removes avoidable errors and gives you evidence and a baseline against which to judge the move.

Exceptions

Test the result

Export every URL in your weighted inventory (clicks, external links or revenue), run the sheet's checks against staging, and you should get a pass/fail list in which every failure has an owner. After go-live, the Sitemaps and Page indexing reports should show new URLs being indexed as old ones drop out, and the 404 log should contain no weighted URL.

FAQ

Do 301 redirects lose link value?

Google says: "301 and other permanent redirects don't cause a loss in PageRank." Rankings can still fluctuate while pages are recrawled.

Can discontinued products redirect to the homepage?

Not in bulk. Send each to its closest replacement or category, or return 404 or 410 when nothing equivalent exists.

How long should redirects stay in place?

Google says "generally at least 1 year"; for visitors, consider keeping them indefinitely.

Do I need Change of Address in Search Console?

Only for a move to another domain or subdomain. A platform change on the same domain needs redirects and updated sitemaps.

Your next step

Fill the sheet for your top weight band first, then the remaining weighted rows, and run checks 1 to 9 before you sign the cutover plan. If you want a second review, our ecommerce replatforming consultancy team can check the inventory, the mapping rules and the staging crawl against your source and target platforms.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon