Using a Reverse Proxy to Install a WordPress Blog for Enhanced SEO

Have you ever encountered a situation where you need to have a blog on your existing company website that does not run on WordPress? I’m sure most of you have confronted such scenarios.

In this article, you’ll discover a way to achieve it without compromising SEO.

Before we dive into it, let’s explore how the organizations and institutions make use of hosting the blog separately from the main website.

Many large businesses have complicated IT systems, making it difficult for their internal departments to look outside the scope of their internal systems. Take, for example, the content marketing department’s desire to create a blog for enlightening its audience. However, the present arrangement makes creating a blog, such as on  WordPress hosting impossible.

On the other hand, businesses may use the “.NET Framework” for their web applications, and other companies are hesitant to use Open-Source frameworks.

When you need to host a blog in any of the scenarios listed above, you have no choice but to think of an alternative server to host it.  This server is thus outside the server where you have hosted your website. Let’s look at some of these options and the impacts they would have, shall we?

For example, if your main website has a URL of www.myorganization.com, the most technically competent professionals of the past would be inclined to install the WordPress blog by purchasing a subdomain of the main domain. As an example in this situation, it would be on ourblog.myoraginzation.com.

In yesteryear, this solution would be perfect. However, currently, when you’re targeting to generate a considerable amount of traffic to your blog, you need to consider the SEO( Search Engine Optimization) aspects as well. We will look into it in the next section.

The primary reason site owners purchase subdomains is to have separate content based on various products for your brand. While there can also be other reasons, such as a separate website for mobile and driving traffic, the fundamental reason lies in content and expanding your brand based on several niches.

So in the scenarios mentioned above, it makes sense to have a subdomain. But how about in the case of blogs?

Well, the search engines view the subdomains as separate websites. This implies that search engines have to crawl and index each subdomain separately. Also, the backlinks to the main domain do not get shared with their subdomains. Thus, building the page rank for a subdomain is almost as difficult as it is for the primary domain.

So it would help if you had subdomains in circumstances where it makes sense to do so. Therefore, an ideal option in blogs would be to have the blog as a subdirectory on your main site.

However, as I have mentioned above, how can you do so in circumstances where your leading site operates and when you hot it on a different platform that does not support WordPress hosting?

This is precisely what Reverse Proxies are for, and we”ll provide you with an overview of reverse proxies in the next section.

Understanding the concept of reverse proxy would be easier if you knew what a forward proxy does.

Likewise, you can use a Reverse Proxy to direct the traffic to the server where you have hosted the WordPress blog. On the other hand, the Reverse Proxy will direct the non-blog traffic to the relevant server. I know it’s easier said than done. So Let’s demonstrate with an example. 

Since the main website does not support WordPress, here are the steps that your web development team has to follow:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
 <system.webServer>
  <rewrite>
   <rules>
    <rule name="blog.somedomain.com" stopProcessing="true">
     <match url=".*" />
     <conditions>
      <add input="{HTTP_HOST}" pattern="^blog.somedomain.com$" />
      <add input="{PATH_INFO}" pattern="^/blog/" negate="true" />
     </conditions>
     <action type="Rewrite" url="\blog\{R:0}" />
    </rule>
   </rules>
  </rewrite>
 </system.webServer>
</configuration>

In the below two lines, the “blog.somedomain.com”  should be replaced by your subdomain where your blog is located:

 <rule name="blog.somedomain.com" stopProcessing="true">
<add input="{HTTP_HOST}" pattern="^blog.somedomain.com$" />

Then in these two lines, you may replace the “blog” folder if you have given a different name to it:

<add input="{PATH_INFO}" pattern="^/blog/" negate="true" />
<action type="Rewrite" url="\blog\{R:0}" />

The Circumstances discussed above are when you are running a server that doesn’t support PHP. However, if you run into a scenario where your leading site is running PHP or Drupal, for instance, but you want to have a different site for the blog in the same domain, you need to configure the Reverse Proxy according to the below steps.

sudo a2enmod proxy proxy_http ssl

This command will restart Apache on most occasions to reload the new directives that you have defined above:

Next is the step that you have been waiting for. That is creating the reverse proxy by editing the server’s virtual host file.

<VirtualHost *>
DocumentRoot /var/www/app/public
SSLProxyEngine On ProxyRequests off
ProxyPass /blog http://blog.somedomain.com
ProxyPassReverse /blog http://blog.somedomain.com
</VirtualHost>

Two vital points to note here is:

Now the next steps are for WordPress, which is typical for both of the above scenarios.

Then you need to go to the server where you have installed WordPress and update the wp-config.php file. This is because you don’t usually configure WordPress to run on a reverse proxy.

So you have to update the wp-config.php file as below:

$_SERVER[‘REQUEST_URI’] = str_replace("/wp-admin/", "/blog/wp-admin/", $_SERVER[‘REQUEST_URI’]);

Then in the same file, you update the  following variables:

In the meantime, you can update the Database configuration values as below:

UPDATE wp_options SET option_value = 'https://www.somedomain.com/blog' WHERE option_name IN('siteurl', 'home');

The next step is to modify the .htacess file so that you can rewrite the URLs correctly:

Becomes:

RewriteRule . /blog/index.php [L]

After completing all of the above steps, you need to ensure that the post and the category links are working as expected. To do so, you need to log in with the old subdomain URL like below:

blog.somedomain.com/wp-login.php

Then it would help if you navigated to ‘settings’ from the main dashboard and then clicked on the “General” tab.

In the Site Address (URL) field update as below:

After doing so, if you’re still in doubt if the URLs would work correctly, then you can install the “Better Search Replace” plugin. It would update all the records on your database where necessary.

Furthermore, you must also be cautious of updating canonicals and robot.txt. 

After doing so, if you’re still in doubt if the URLs would work correctly, then you can install the “Better Search Replace” plugin. It would update all the records on your database where necessary.

Furthermore, you must also be cautious of updating canonicals and robot.txt.

Now you may have discovered that WordPress is highly customizable. This is because you can use WordPress to host only the blog part of the website separately while untouching the rest. As you have seen through this blog, the rest of the website might be hosted on different platforms that do not support WordPress.

So including the blog to the rest of the website can be a challenging task. However, you can overcome them by using reverse proxies.

Stay tuned for further articles.