My advice since the start of this thread was against the “Transfer” thing as it does not fit your use case. Please do not use a saw to hammer in a nail. … that’s not what it was made for.
If you moved and your site now does have a different baseURL for the BLOG/POSTS, please set up 302/301 redirects to fit your needs and the official google requirements.
If you set up a transform rule, your content will be available from:
Which google will punish you for. So please set up proper redirects as the content has moved from the one base URL to the other baseURL and redirect your visitors according to you changes. As you mentioned your “valuable” PageRules and that you just have 3 of them (as free user) please still do it that way and later change back to origin and also set up these rules at your origin.
But for the next time you probably want to set up the redirects at Cloudflare to make the redirects happen at the edge and therefore faster.
So for now, please set up an PageRule that redirects your traffic from:
URL Forward Code:
302 (or if proofen stable “301”)
And after two weeks or one month you should implement that at your origin and set up a Apache .htaccess rule or a NGINX rule like this, to solve that problem natively but slover as it is getting executed on your origin:
RedirectMatch ^/posts(.*)$ https://www.a-hr.pro/ua/blog/$1
rewrite ^/posts/(.*)$ https://www.a-hr.pro/ua/blog/$1 redirect;
Hope that helps. And please keep in mind that Cloudflare will help you to make that switch faster, but on long term if you care about your 3 free PageRules you will most probably be better with solving that problem natively on your origin and not on Cloudflare. Use Cloudflare when it is important to process things on the Edge fast and if it is not important anymore (1-2 month after) you can fall back to your origin server.