My client's web dev team migrated the site last week from CFM to ASP.NET.
Now all 15000 pages we have indexed in the engines produce 404 errors.
I've been told to use 301 redirects to fix this problem. My question is - should I use 301 redirects on 15,000 unique pages, or wait for reindexing ? Is it a major project to redirect 15,000 CFM pages to their ASP counterparts?
I'm a bit lost since I've never been in this type of situation. Thanks yall.
Hi I saw your comment. As you have migrate CF to ASP.Net I need some help from you. Can you please give me the Tool name which you have used for migration.
My client's web dev team migrated the site last week from CFM to ASP.NET.
Now all 15000 pages we have indexed in the engines produce 404 errors.
I've been told to use 301 redirects to fix this problem. My question is - should I use 301 redirects on 15,000 unique pages, or wait for reindexing ? Is it a major project to redirect 15,000 CFM pages to their ASP counterparts?
I'm a bit lost since I've never been in this type of situation. Thanks yall.
301 redirects will save any backlinks to have to existing pages so it is worth it if you have a lot of them. If the site just launched I wouldn't worry about it too much.
You should use 301 redirects for all 15,000 pages. It’s essential for preserving SEO and user experience. Automate the process if possible to manage the workload.
For 15,000 pages, using 301 redirects is crucial to preserve SEO and user experience. Although it’s a major project, it’s generally better than waiting for reindexing, as redirects will ensure that visitors and search engines find the correct pages. Consider using tools or scripts to automate the process if possible.
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.