Did 301 Redirect But Still Have Broken Links

Discussion in 'Search Engine Optimization' started by NomadGlass, Oct 18, 2010.

  1. #1
    Did a 301 redirect when I built my new .com site from my old .info site. However, finding out that I have broken links on all of the sub pages on my site like our locations page, services page, etc...

    Should I just go through and delete all of the old website except for the homepage?
     
    NomadGlass, Oct 18, 2010 IP
  2. Canonical

    Canonical Well-Known Member

    Messages:
    2,223
    Likes Received:
    141
    Best Answers:
    0
    Trophy Points:
    110
    #2
    I wouldn't, but that is totally up to you. Your new site will loose credit for ALL links to the old site not pointing to the old site's home page.

    Sounds like you 301 redirected the home page only. You really need to 301 redirect EVERY old URL to the new URL whose content most closely resembles that of the page found at the old URL.

    If your URLs for the new site are EXACTLY the same as those for your old site except the domain portion of the URL is now .com instead of .info AND you are hosted on an Apache web server, you can setup ONE RewriteRule using Mod_Rewrite/.htaccess to take care of this.

    It depends on how you implemented the new site at your web hosting company as to how the redirects should be coded in Mod_Rewrite.

    For example, if the old domain (example.info) and new domain (example.com) resolve to separate folders under your hosting account, you can add the following to the .htaccess file in the root folder of your OLD domain:

    However, if both your .info and .com domains point to the same folder under your hosting account you should be able to add the following to the .htaccess file in the root folder shared by both domains:

    Both of the above assume that the www version of your .com domain's URLs are the canonical version. If you prefer URLs without the www then simply remove the "www." from the RewriteRule in each example.

    If you're hosted on a Windows/IIS platform, you'll need to implement the 301 redirects differently.
     
    Canonical, Oct 18, 2010 IP