Using a Reverse Proxy and 301 redirect to appear Sub Domain as Sub Directory - what are the SEO Risks?

[joshibhargav_20]

We’re in process to move WordPress blog URLs from subdomains to sub-directory. We aren’t moving blog physically, but using reverse proxy and 301 redirection to do this.

• Blog subdomain URL is https://blog.example.com/ and
• destination sub-directory URL is https://www.example.com/blog/

Our main website is e-commerce marketplace which is YMYL site. This is on Windows server. Due to technical reasons, we can’t physically move our WordPress blog to the main website.

Following is our Technical Setup

1. Setup a reverse proxy at https://www.example.com/blog/ pointing to https://blog.example.com/
2. Use a 301 redirection from https://blog.example.com/ to https://www.example.com/blog/ with an exception if a traffic is coming from main WWW domain then it won’t redirect. Thus, we can eliminate infinite loop.
3. Change all absolute URLs to relative URLs on blog
4. Change the sitemap URL from https://blog.example.com/sitemap.xml to https://www.example.com/blog/sitemap.xml and update all URLs mentioned within the sitemap.

SEO Risk Evaluation

We have individual GA Tracking ID and individual Google Search Console Properties for main website and blog. We will not merge them. Keep them separate as they are.

Keeping this in mind, I am evaluating SEO Risks factors

1. Right now when we receive traffic from main website to blog (or vice versa) then it is considered as referral traffic and new cookies are set for Google Analytics. What’s going to happen when its on the same domain?
2. Which type of settings change should I do in Blog’s Google Search Console? (A). Do I need to request “Change of Address” in the Blog’s search console property? (B). Should I re-submit the sitemap?
3. Do I need to re-submit the blog sitemap from the https://www.example.com/ Google Search Console Property?
4. Main website is e-commerce marketplace which is YMYL website, and blog is all about content. So does that impact SEO?
5. Will this dilute SEO link juice or impact on the main website ranking because following are the key SEO Metrices. (A). Main website’s Avg Session Duration is about 10 minutes and bounce rate is around 30% (B). Blog’s Avg Session Duration is 33 seconds and bounce rate is over 92%

[BlueprintMarketing]

I wrote this on my phone and I will update this in 2-3 hours

rewrite the URLs do not redirect

[BlueprintMarketing]

PS

tools like CloudFlare & Fastly don’t care what you’re server is .

https://blog.cloudflare.com/subdomains-vs-subdirectories-best-practices-workers-part-1/

https://blog.cloudflare.com/subdomains-vs-subdirectories-improved-seo-part-2/

https://azwa.1clkaccess.in/community/q/reverse-proxy-a-successful-blog-from-subdomain-to-subfolder

frontend ssl_in
bind :443 ssl crt /etc/haproxy/website.com.combined
acl root path /
acl blog path_beg /blog
acl sitedomain path_beg /leasopedia
acl glossary path_beg /glossary
acl wpadmin path_beg /wp-
acl blog_search query -m reg ^s=.$
acl blog_preview query -m reg ^p=.*$

use_backend wpengine if blog OR sitedomain OR glossary OR wpadmin OR root blog_search OR root blog_preview
default_backend main-site

backend wpengine
server wpengine examplecompany.wpengine.com:443 ssl ca-file /etc/ssl/certs/ca-certificates.crt

backend main-site
server main-site example.examplecompany.com.:443 ssl ca-file /etc/ssl/certs/ca-certificates.crt

https://blog.examplecompany.com or https://examplecompany.com/blog.

It’s worth noting that WPEngine does not recommend this practice. 

For those that want to host at https://site.com/blog and do it with a managed WordPress hosting provider like WPEngine, this article is for you.

(Note, WPEngine will automatically block your reverse proxy, so you will need to contact customer support and ask them to whitelist its IP address in their firewall. I found this to be a painless process thanks to the friendly support staff at WPEngine.)

How?

The trick to getting the blog to look like it’s living on the main site (but actually living elsewhere) is to use a reverse proxy.

HAProxy is a powerful reverse proxy, though its configuration has a bit of a learning curve compared to Nginx or Apache.

We use HAProxy internally because it works well with AWS Elastic Load Balancers, which frequently change their IP address. Learn more

HAProxy config

| 1 | bind *:443ssl crt/etc/haproxy/website.com.combined |

You’ll need to use SSL, as all WPEngine installs redirect to SSL.

Of note is that HAProxy expects your certificate chain and your private key to be combined into one file

| 1 | acl |

These are the pattern matching lines that we’ll use to determine which traffic is forwarded to WPEngine

| 1 |

use_backend wpengine ifblog orsitename ORglossary ORwpadmin ORroot blog_search ORroot blog_preview

|

This directs /blog*, /sitename*, /glossary* and /wp-* to WPEngine.

You can replace these with your own blog and page paths configured in wordpress.

This line also directs /?s= and /?p= to wordpress using the combined root and blog_search and blog_preview lines.

These are necessary to making searching and page previews work in WordPress.

| 1 | default_backend main-site |

Everything that doesn’t match one of the above patterns will go to the main site.

| 1 | backend wpengine |

Directives in the frontend that resolve to this backed will route to the blog.

| 1 | backend main-site |

Directives in the frontend that resolve to this backed will route to your main site.

I would use Fastly

https://thoughtbot.com/blog/host-your-blog-under-blog-on-your-www-domain

https://blog.cloudflare.com/subdomains-vs-subdirectories-best-practices-workers-part-1/

https://link.medium.com/g1ReAhcnZ4

[BlueprintMarketing]

Hi I have done this for 20+ websites.

Following is our Technical Setup

1. Setup a reverse proxy at https://www.example.com/blog/ pointing to https://blog.example.com/

please remember that the hosting or reverse proxy on the server is so important. Some managed WordPress hosts do this better then others.

https://pressidium.com/ now offers reverse proxy's on all plans for free

https://pressidium.com/blog/2019/wordpress-reverse-proxy-how-universities-corporations-are-benefitting-from-reverse-proxy-setups/

if you want to do this with out having to worry about it any problem I cannot stress how easy it is done by hosting the blog on Pagely.com it’s now free!

(don’t worry about the $200 they don’t change it)

https://support.pagely.com/hc/en-us/articles/213148558-Reverse-Proxy-Setup

or kinsta for $50 more a month

https://kinsta.com/knowledgebase/reverse-proxy/

Pantheo.io (my go to host) now offers the “Advanced Global CDN” it lets you run a reverse proxy & much more via Fastly (my favorite CDN) the cost is very reasonable.

https://pantheon.io/product/advanced-global-cdn

Servebolt.com offers reverse proxy & hosts all PHP sites Wordpress too. They use CloudFlare & they will setup everything for you for free. They are also a full enterprise partner

https://servebolt.com/help/article/cloudflare-workers-reverse-proxy/

You  can also use Fastly, CloudFlare business, Incapsula, Cloudfront

2.    Use a 301 redirection from https://blog.example.com/ to https://www.example.com/blog/ with an exception if a traffic is coming from main WWW domain then it won’t redirect. Thus, we can eliminate infinite loop.

This is something that is very easy I would use Fastly

• Change all absolute URLs to relative URLs on blog

NO don’t do that it will hurt your site & will not help you change the URLs they need to be rewritten not made relative it’s a very bad way of trying to do this and will not help your site.

• Change the sitemap URL from https://blog.example.com/sitemap.xml to https://www.example.com/blog/sitemap.xml and update all URLs mentioned within the sitemap

Our main website is e-commerce marketplace which is YMYL site. This is on Windows server. Due to technical reasons, we can’t physically move our WordPress blog to the main website.

If  you’re website site is YMYL I would use Pagely but Linode , AWS can do this to  with Fastly or  Nginx

https://thoughtbot.com/blog/host-your-blog-under-blog-on-your-www-domain

<code>location /blog/ {
    proxy_pass https://blog.example.com;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}</code> 

<code>please let me know if you need help
Tom</code>