Fix Cloudflare Worker Reverse Proxy Setup (Redirect → Proxy) for WordPress Blog on Subfolder

I have a WordPress.com blog currently set up as a redirect from tradewolf.ai/blog → blog.tradewolf.ai. I need this changed to a true reverse proxy instead, so the URL stays as tradewolf.ai/blog while WordPress content is served behind the scenes — no redirect, no URL change, no visible subdomain. Why this matters: I'm running an SEO content strategy (30 articles/month) and want all of that content to build domain authority for my main site, tradewolf.ai. With the current redirect, Google indexes and ranks blog.tradewolf.ai as a separate site — meaning months of content investment build authority for the wrong domain. A proper reverse proxy keeps everything consolidated under tradewolf.ai, which is critical for my SEO/ranking goals. I want google to rank tradewolf.ai Setup: Main domain tradewolf.ai is connected to Lovable.dev (a no-code app builder) Domain DNS is on Cloudflare Blog content lives on WordPress.com at blog.tradewolf.ai I need tradewolf.ai/blog/* to transparently proxy to the WordPress backend via a Cloudflare Worker — visitors and Google should only ever see tradewolf.ai/blog/... URLs What I need done: Write/deploy a Cloudflare Worker that intercepts requests to tradewolf.ai/blog/* and fetches content from blog.tradewolf.ai, rewriting internal links/assets so they stay under tradewolf.ai/blog Ensure canonical tags on the WordPress side point to tradewolf.ai/blog/..., not the WordPress hostname Confirm root domain (tradewolf.ai) keeps working normally on Lovable — no downtime to my main site Test that the URL bar stays on tradewolf.ai/blog (not blog.tradewolf.ai) for both root blog page and individual posts Budget: $50 fixed price — this is a narrowly scoped fix, not a full build (I already have sample Worker code/architecture from a prior consultation, happy to share). To apply, please confirm: You understand the difference between a redirect and a reverse proxy (please briefly explain in your application so I know you've read this) Experience with Cloudflare Workers specifically Availability to do this within the next few days