Rebuilt website from static html to CMS need to redirect indexed links

Rebuilt website from static html to CMS need to redirect indexed links - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Rebuilt website from static html to CMS need to redirect indexed links error on your web browser. Problem :

I have rebuilt a website which was all created with static html pages, it has now been rebuilt using a CMS system.

I need to find a way of redirecting all the existing links to there new corresponding pages which utilise friendly URL rewrites on the CMS based website

I imagine there will be several hundred if not 1000s as i have pages and images linked from google.

What is the most efficient way to complete this

Thanks in advance

Mike

Solution :

I've been working on a similar problem this week, a website I've taken over has 4,000+ broken links because the site was migrated away from an old CMS, so all the URL's are different.

The only way I've managed to solve the problem is by adding a fair number of new Redirect rules to my .htaccess file. What you will find is that a lot of your old links can be grouped together and directed to one section of your site. So for example, instead of writing rules to deal with links like:

• http://www.mydomain.com/news_article/01


• http://www.mydomain.com/news_article/02

Also

Redirect permanent /news_article/01 http://www.mydomain.com/news/01/
Redirect permanent /news_article/02 http://www.mydomain.com/news/02/

You would instead divert these URL's like this:

Redirect permanent /news_article http://www.mydomain.com/news/

So essentially everything contained inside the /news_article folder would direct to the /news/ folder of the new site.

It's not a glamorous fix, but either way you are faced with a long drawn out process of redirects.

What an interesting problem - I think you have a few options.

• Consider if you want this automated or letting users click through manually.
  
  
  
  
  • If manual then you can write a program which will update all your HTML pages to enter the new code - not ideal, I've done this in the past and it was a little hassle but not too bad.
  
  
  • If automatic, you could also add an iFrame to your HTML pages and then use some javascript to forward it all (http://stackoverflow.com/questions/580669/redirect-parent-window-from-an-iframe-action-using-javascript).
  
  

The above suggestions works if you're happy to send users to your new page home page - to send to the equivalent of the HTML page is more tricky.

Lose the SEO, remove the pages and let the new pages get indexed (totally not recommended). However, this may work but depends on the language you're using. For example, in ASP.NET you can set up what to do if you get a page not found. You then have a list of your 'old' HTML pages and link to your new versions.

I hope something here helps.

We hope that this article has helped you resolve the html, redirects, cms error in your web browsers. Enjoy browsing the internet uninterrupted!