What to keep in mind: to 301 redirect every page in an entire online store

[BobGW]

Hello,

I've got to put a 301 redirect on every page in an entire online store. We're moving to a better premade cart. Who has experience with this? How do I not lose traffic, if that is possible? What do I need to keep in mind?

Thanks!

[BobGW]

Very good, I'll go with the redirect map. Thank you.

[Mobilio]

IF (!!!) everything is tested and prepared correctly there isn't risk. But only building this redirect map can take few days, few days for testing and few days for deploying. And everything dependent from size of shop.

Moving to responsive site or staying in pre made card - isn't decision that i can advise based on actual input data. Probably you can make it since working there and know all details. I also can advise to switch to Volusion too.

Here in Bulgaria we have quote as "the devil is in the little details". This mean that it may sound good/great but something that you didn't think as important initial can ruin everything. One of closest example can be agreements with small fonts underline.

So - i can't advise on eCommerce platform now without knowing all details to your customer, their needs, actual issues with platform, etc. BUT i can advise you for redirect map files. And once you make first map you will see that isn't scary at all.

[BobGW]

How risky is this Peter, for an intermediate SEO with an intermediate sized online store?

Should we just move to a responsive site and stay with a not-so-good pre made cart?

Or switch to Volusion, which is a lot better?

Your opinion?

[Mobilio]

Building rewrite URLs one-by-one for webserver isn't suitable for your needs. All you need is to use redirect map based on your webserver or use/create CMS redirect map.

If your URLS for redirects around 100 you can use webserver configuration typing all of them in server configuration. But when links become 1000+ then this will slow down webserver and make configuration not-so-simply for changes. This is why almost all of webservers support redirect map:
https://httpd.apache.org/docs/2.4/rewrite/rewritemap.html
https://www.nginx.com/resources/wiki/modules/lua/
http://www.iis.net/learn/extensions/url-rewrite-module/using-custom-rewrite-providers-with-url-rewrite-module

Then all you need is to build redirect map for your webserver and do one quick test in dev environment. With many redirects anything can happen - ram or cpu hogging, etc. Once you check and recheck this you should make also CMS redirections with some plugins or write new one. You should keep both (redirect map and CMS redirects) working for some time (6 months or year). Then you can drop redirect map and use only CMS redirects for old bookmarks.