If both end points are hosted at Pagely, i.e. your DNS for both the master domain (example.com) and any additional sites running in a subdirectory setup (example.com/blog), we can support this for you, free.

Read on to learn the difference between a subdomain and a subdirectory and when a reverse proxy may be needed to support your website’s goals.

Subdomain vs. Subdirectory

The primary factor is dependent upon whether you plan on using blog.example.com (a subdomain install) or example.com/blog (subdirectory install). If it’s the former, nothing additional is needed; it will just live in its own top level install. If the latter, then a reverse proxy will be required to enable subdirectory access on the same domain.

If I wanted to do a WordPress install nested within another install, that is something Pagely can accommodate as well which also involves a proxy.

Having questions around which makes the most sense for you? Head over to our subdomain vs subdirectory article for a quick glance at when each is best suited.

Using WordPress Reverse Proxy

Reverse proxies are typically used in these cases where you’re either a) looking to serve a WordPress site from a subdirectory separate from the root domain or b) resolving a WordPress site from a subdomain to a subdirectory. We often see eCommerce websites who want a separate blog running under WordPress prefer the former route. In both instances, the URL format will appear cleanly as example.com/blog.

At Pagely, we can support and maintain a WordPress reverse proxy for you. Whether both end points are being served from your Pagely VPS or just one, our WordPress engineering experts have done it all and can help you, too.

Find additional information on pricing and implementation for using a Reverse Proxy Setup in the linked article.