{"id":37760,"date":"2025-01-20T08:32:56","date_gmt":"2025-01-20T08:32:56","guid":{"rendered":"https:\/\/peraltafinancing.com\/affiliate-marketing\/how-to-host-your-wordpress-blog-in-a-sub-folder-hosted-separately\/"},"modified":"2025-01-20T08:32:56","modified_gmt":"2025-01-20T08:32:56","slug":"how-to-host-your-wordpress-blog-in-a-sub-folder-hosted-separately","status":"publish","type":"post","link":"https:\/\/fivemor.com\/?p=37760","title":{"rendered":"How To Host Your WordPress Blog In A Sub-Folder, Hosted Separately"},"content":{"rendered":"


\n<\/p>\n

\n

One of my Concierge clients had an interesting situation we had to figure out.<\/p>\n

His main site is hosted somewhere else because it is a proprietary job board. However, he wants his blog to be on WordPress. The job board cannot host WordPress, so we had to host the blog elsewhere.<\/p>\n

Typically, when you use different hosts, you would use a sub-domain to do that. Your root domain can point to one host while you can have any number of sub-domains you like pointing anywhere you please. It is very simple.<\/p>\n

But, it was determined it would be best not to use a sub-domain and instead use a sub-folder structure. It is better for SEO this way since the SEO benefits of those blog posts would lend strength to the primary domain.<\/p>\n

This same setup would work in other kinds of situations. You could have your main site running on ClickFunnels, Kajabi, Shopify or any other third-party proprietary system and still have your blog run on WordPress.<\/p>\n

Here\u2019s The Setup<\/h2>\n

So, let\u2019s say your main site is running on domain.com<\/strong>.<\/p>\n

You want your blog to run on WordPress and be available at domain.com\/blog\/<\/strong>.<\/p>\n

This way it will all look like the same site, even though it is technically on two different platforms and two different hosting providers.<\/p>\n

Using a sub-domain like blog.domain.com would be much easier. Just point the domain at the DNS level using an A record or a CNAME. But, that doesn\u2019t work for a sub-directory. We need a different approach. An approach that will \u201cfake it\u201d. \ud83d\ude42<\/p>\n

Here\u2019s How It Was Done<\/h2>\n

First off, for this approach, you must be using Cloudflare<\/a> as your domain\u2019s DNS provider. Cloudflare is what I use and use for most of my clients. They happen to be the best at this and that power and flexibility is what we\u2019re using for our solution here.<\/p>\n

Specifically, we will be using Cloudflare Workers<\/a>.<\/p>\n

A Cloudflare worker is basically a script which can be run right at the domain level to do various things. You can use workers to rewrite URLs, run search\/replace operations or any a wide array of things.<\/p>\n

In our case, we\u2019re going to use a Cloudflare worker script to take all URL calls to domain.com\/blog\/ and re-write them over to blog.domain.com.<\/p>\n