Implementing SEO Rule On Website Hosted on IIS8

In this post, we are going to optimize a website that is hosted on IIS8, by implementing basic SEO rules to help improve the user experience as well as to increase the SEO ranking.

 

We will optimize our IIS application according to Google’s Search Engine Optimization Starter Guide. Let’s get into it. First of all, we will get a basic overview of IIS8 and SEO.

 

IIS8: Microsoft’s Internet Information Server (IIS) is an extensible web server that hosts multiple web applications/sites.

 

IIS supports HTTP, HTTPS, FTP, FTPS, SMTP and NNTP protocols.

 

Other web servers include:

1. Apache
2. NGNIX (pronounced engine X) from NGNIX
3. Novell’s NetWare Server
4. Google Web Server (GWS)
5. IBM’s family of Domino Servers

SEO: SEO (Search Engine Optimization) is a process of improving the visibility of a website in search engine results. Learn more from Google SEO guide

 

Table of Content

1. Improving Site Structure
• Sitemap
2. Dealing with Crawlers
• robot.txt
• BOT accessibility(Libwww-perl Access)
3. Server Security
• Server Signature (Server: Microsoft-IIS/8.0)
4. Canonicalization
• URL Canonicalization
• IP Canonicalization
5. Optimizing Content
• Page Cache (Server Side Caching)
• Expires Tag
• HTML Compression/GZIP

Let’s get the details about these topics with a basic sample application hosted in IIS. First of all, we need to configure the IIS in order to host our website. We will change Windows host file to set hostname with local IP and port.

 

Modification of Host file

Browse the file : c:\Windows\System32\Drivers\etc\hosts.

 

 

 

Hit enter or open it with notepad. Copy the following content to this file. You can copy its existing content to another opened note for future uses.

 

 

 

Now, open your browser. In address bar, write localseo.com and hit enter. Our local site will load.

 

Improving Site Structure

 

Sitemap

 

Applications need to be well structured based on the root/home page. It is better to use breadcrumbs that help users to navigate to root/home page. Sitemap improves the crawling of site by crawlers. We can also use a sitemap XML file to help web crawlers (Google or Other search engine) with listing the page content of the site.

 

Below is a sample sitemap XML format. Upload the XML file (sitemap.xml) to root folder. 

<?xml version="1.0" encoding="UTF-8"?>
<urlset
      xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9
      http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">

  <url>
    <loc>http://localseo.com</loc>
  </url>
  <url>
    <loc>http://localseo.com/Home</loc>
  </url>
  <url>
    <loc>http://localseo.com/About</loc>
  </url>
  <url>
    <loc>http://localseo.com/Contact</loc>
  </url>
</urlset>

In IIS, I have placed the sitemap.xml file in the root folder.

 

 

 

Dealing with Crawlers

 

Web Robots

 

Web robots, known as spider/crawler, are programmed to visit/index the site content automatically. Robots.txt file is used to give instructions to the web robots about the crawling of the website. There are two statements used: User-agent: * and Disallow. 

1. The “User-agent: *” means this section applies to all robots.
2. The “Disallow: /” tells the robot that it should not visit any pages on the site.

Learn more about robot.

 

Libwww-perl Access BOT

 

We can restrict BOT access using webconfig by URL rewrite rules. We need to enable IIS URL Rewrite 2.0. Click Web Platform Installer in the IIS Management section.

 

 

 

A list of components will appear. Search the “Rewrite” here. 

 

 

 

Search result will show URL Rewrite 2.0. Install it now.

 

 

After installation, the URL Rewrite icon will appear. Double click on it.

 

 

 

Let’s create a new rule for Libwww-perl BOT to restrict access website.

 

 

 

Then, configure for BOT rule to restrict.

 

 

 

Or simply copy paste below code in webconfig. Then, replace your pattern.

<rule name="BOT request BLOCK" stopProcessing="true">
          <match url=".*" />
          <conditions>
            <add input="{HTTP_USER_AGENT}" pattern="^Libwww-perl$" />
          </conditions>
          <action type="CustomResponse" statusCode="403" statusReason="Forbidden: Access is denied." statusDescription="You do not have permission to view this directory or page using the credentials that you supplied." />
</rule>

Server Security

 

Server Signature

 

From security aspects, it is important to turn it off. By default, it is set ON. Here, we will rewrite the server signature with outbound rule in IIS.

 

 

 

Again, double click on URL Rewrite icon and add Server variable, like in the following image.

 

 

 

 

 

 

 

or simply copy and paste the below code in webconfig and replace your changed values.

<outboundRules>
        <rule name="Server Signature">
          <match serverVariable="RESPONSE_SERVER" pattern=".+" />
          <action type="Rewrite" value="Changed" />
        </rule>
</outboundRules>

 

 

Canonicalization

 

URL Canonicalization

 

 

 

Make sure the bindings are proper with the host name in IIS. Now, create a new inbound rule for Canonicalization of both the IP and the URL, with www.

 

 

 

Or simply copy paste the below code in webconfig. Replace your values here and redirect.

<rule name="Canonical HOST redirect">
          <match url="(.*)" />
          <conditions>
            <add input="{HTTP_HOST}" pattern="^www\.localseo\.com$" negate="true" />
          </conditions>
          <action type="Redirect" url="http://www.localseo.com/{R:1}" />
</rule>

Optimizing Content

 

For better performance, it is good to cache the static content. There are three different cache Control Modes. The default is NoControl.

1. NoControl - Does not add a Cache-Control or Expires header to the response.
2. DisableCache - Adds a Cache-Control: no-cache header to the response.
3. UseMaxAge - Adds a Cache-Control: max-age=<XXX> header to the response, based on the value specified in the CacheControlMaxAge attribute.
4. UseExpires -  Adds an Expires: <DATE> header to the response, based on the date specified in the httpExpires attribute.

Page Cache (Server Side Caching) 

 

 

 

 

<staticContent>
      <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="7.00:00:00" />
 </staticContent>

 

 

Expires Tag

<staticContent>
<clientCache cacheControlMode="UseExpires" httpExpires="Wed, 01 Jan 2020 00:00:00 GMT" />
</staticContent>

 

 

HTML Compression/GZIP

 

 

 

 

Finally, the web.config file.

<?xml version="1.0" encoding="utf-8"?>
<!--
  For more information on how to configure your ASP.NET application, please visit
  http://go.microsoft.com/fwlink/?LinkId=301880
  -->
<configuration>
  <appSettings>
    <add key="webpages:Version" value="3.0.0.0" />
    <add key="webpages:Enabled" value="false" />
    <add key="ClientValidationEnabled" value="true" />
    <add key="UnobtrusiveJavaScriptEnabled" value="true" />
  </appSettings>
  <system.web>
    <compilation targetFramework="4.5.2" />
    <httpRuntime targetFramework="4.5.2" />
  </system.web>
  <system.webServer>
    <staticContent>
      <clientCache cacheControlMode="UseExpires" httpExpires="Wed, 01 Jan 2020 00:00:00 GMT" />
    </staticContent>
    <!--<staticContent>
      <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="7.00:00:00" />
    </staticContent>-->
    <rewrite>
      <rules>
        <rule name="Canonical HOST redirect">
          <match url="(.*)" />
          <conditions>
            <add input="{HTTP_HOST}" pattern="^www\.localseo\.com$" negate="true" />
          </conditions>
          <action type="Redirect" url="http://www.localseo.com/{R:1}" />
        </rule>
        <rule name="BOT request BLOCK" stopProcessing="true">
          <match url=".*" />
          <conditions>
            <add input="{HTTP_USER_AGENT}" pattern="^Libwww-perl$" />
          </conditions>
          <action type="CustomResponse" statusCode="403" statusReason="Forbidden: Access is denied." statusDescription="You do not have permission to view this directory or page using the credentials that you supplied." />
        </rule>
      </rules>
      <outboundRules>
        <rule name="Server Signature">
          <match serverVariable="RESPONSE_SERVER" pattern=".+" />
          <action type="Rewrite" value="Changed" />
        </rule>
      </outboundRules>
    </rewrite>
  </system.webServer>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <system.codedom>
    <compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:6 /nowarn:1659;1699;1701" />
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:14 /nowarn:41008 /define:_MYTYPE=\"Web\" /optionInfer+" />
    </compilers>
  </system.codedom>
</configuration>
<!--ProjectGuid: 7D096796-F3E8-4C10-BB3F-2BC4542846C6-->

Hope this will help!