Advice for redirecting over 3000 urls following site move and update?

Paisley: 6 days ago

My client has decided to completely revamp their website and no longer wants to use MijoSef, in fact they do not want to use any SEF component at all. At present google hase over 3250 urls indexed for the existing site, thus I need to redirect each of the indexed URL's to the new URL following the site update/move.

I have exported the URL's from MijoSef and have attempted to test the redirect by inserting one into the jos_redirect_links table, publishing it and then testing it. However the redirect does not seem to take effect. I have also tried the same with ReDJ and the redirect does not seem to take effect either.

For example, the url on the currently live site is is:

I have set up a redirect in ReDj (and in the core redirect component - now removed) to:

Is there another (better?) way to do this to ensure the indexed links do not return a 404? I'd be happy for some suggestions. The MijoSEF export contains over 13000 urls, thus I was thinking maybe I could scrape a list of indexed URL's in google, compare to the list from MiJoSEF and add the 3250 indexed redirects to the htaccess file? Is this a feasible method?

Thank you in advance. D

Nova: 6 days ago

I a little confused with your question or likely your approach to do the redirect, but I ll give a try to post an answer to help you clear things out a bit:

This URL that you call the old URL, is a working URL in the site

While this URL is actually a 404 error.

It's not clear from where you get these URLs?

But, I don't know about ReDJ, but you can't redirect your first URL to the one you said - while the first one is actually working. To add to this that you are trying to redirect a working URL to a 404 URL.

So from where you get this URL : 


Do I suspect correctly that this is a URL that exists on the old version of site? One of those Google Indexed URLs?

If so, you are approaching the Redirects thing from the opposite way. As that indexed URL 

will be the one that after you switch to the new site, it will produces the 404 (it already does so). And this is the URL that you need to redirect to the new corresponding one that will be working on the site, and will be able to display the same content as before. The new URL that you need to redirect to will actually be the result of the SEF-isized: