Custom Error-Pages and 301 redirects

By -
Let´s assume, you´ve just acquired an expired domain and you´ve recognized that there are plenty of back links pointing to a forum, a blog or something like that. Well, the first problem is, that (in most cases) you won´t be able to use that exactly software and you may not use the formerly used content.

For SEO-purposes it will be good to 301-redirect the urls that have deep links, because otherwise google may penalize you because of lots of 404-errors. 2nd reason to do this is tousle the link power of all incoming links. The solution:

You may use custom 404-pages in IIS. But this one is better, in web.config in system.web just add this section:

<customErrors defaultRedirect="404.aspx"
                  redirectMode="ResponseRewrite" mode="On">
        <error statusCode="404" redirect="404.aspx"/>
</customErrors>

In my case I´ve added a "404.aspx" where I´m just redirecting via 301-redirect to the root of my domain. Now a requests gets processed like this:
  1. Request comes in, get´s handled by web.config and redirects (301) to 404.aspx - 301 because of redirectMode="ResponseRewrite"
  2. (ResponseRedirect would create a 302)                                                                                   404.aspx receives the request (inculding the error-path)
  3. Now you can conditionally (error-path) redirect.
 In my particular case this one is already overloaded - I could have just used this one:

      <customErrors defaultRedirect="~/" redirectMode="ResponseRewrite" mode="On">
        <error statusCode="404" redirect="~/"/>
      </customErrors>

This way, a clean and fully functional 301 redirect for all 404-errors will be available.

301 redirect with ASP.NET

Response.Redirect("http://www.google.com"); ‘creates a 302-Redirect to http://www.google.com

302-Redirects are bad for search-engines, just because it is a "temporarily moved" Message, which means, that its target could change by each and every request. To pass Linklove, PageRank, Trust etc of a URL to another, you need to use a 301-redirect.

The most flexible way to do this, is to use a small code-behind snippet:

 Response.Clear();
 Response.StatusCode = 301;
 Response.AppendHeader("location", "http://www.google.de");
 Response.End();

This way Google tranfers the trust, the linklove, the PageRank, etc to the redirect´s target

Comments

Post a Comment

Popular posts from this blog

Setting up Dotnetnuke (DNN) to work with Active Directory

By -
Image
Setting Up Active Directory Integration with DotNetNuke Seems like enough people ask, and the information is hidden enough around the DNN AD forum that this information could be posted in one place.  These are the steps I take to get my DNN AD integration to work every time.  I have never had it fail.  I hope you find it helpful.  Now if you are setting up your AD in Mixed-Mode most likley this little write up isn't for you. The setup process is a three step process.  The first step is done from within DNN.  The second step takes place in DNN’s web.config file.  The final step takes place in IIS. Within the DNN Website Login as Admin or Host to your DNN website. After login go to                                        ...
Read more

SQL Server 2016 TDE ( Transparent Data Encryption)

By -
Image
Transparent Data Encryption is designed to protect data by encrypting the physical files of the database, rather than the data itself These physical files include the database file (.mdf), the transaction log file (.ldf) and the backup files (.bak). Its main purpose is to prevent unauthorized access to the data by restoring the files to another server.  With Transparent Data Encryption in place, this requires the original encryption certificate and master key. The protection of the database files is accomplished through an encryption key hierarchy that exists externally from the database in which TDE has been enabled. The service master key exists at the instance level. The database master key and certificate at the Master database are used to protect the database encryption key that is located at the user database The dependency upon the encryption key hierarchy in the Master database, as well as the instance, prevents the database files from being restored to an in...
Read more

jQuery Tips for DotNetNuke Developers

By -
Image
Make sure you call jQuery.noConflict();. This is necessary to not cause other client scripts and libraries to run errors. This is due to the fact that other client scripts might be using the $ designator for a JavaScript class. [jQuery.noConflict(); documentation] If manually adding jQuery, try to load the jQuery library in the header before all others. Not doing this can lead to the jQuerylibrary not being loaded before another client script or library tries to use it. This is especially true of jQuery plugins. Always call the jQuery core methods using the jQuery() format. This is related to the previous issue. Check the jQuery plugin source code. Not all jQuery plugins use the long form of calling jQuery. This can result in errors if you have called jQuery.noConflict();. In DNN 5+, register jQuery. DNN 5+ allows module developers to register jQuery to be loaded only when modules need it. Just callDotNetNuke.Framework.jQuery.RequestRegistration(). This prevents jQuery f...
Read more