WordPress Blog Subfolder Migration
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
I’m moving my WordPress blog from **blog.joyandchaosshop.com** to **joyandchaosshop.com/blog** within our BigCommerce storefront. WordPress itself will stay on its current server; Cloudflare Workers will handle the reverse proxy that makes the blog appear under joyandchaosshop.com/blog.
Here’s what I need done:
• **Configure the reverse proxy and permanent redirects.** Set up a Cloudflare Worker and any supporting rules so the public-facing blog lives at joyandchaosshop.com/blog. Anyone visiting an old blog URL should automatically be sent to its exact matching new page using a **301 permanent redirect**, rather than being sent to the blog homepage. For example, blog.joyandchaosshop.com/post-name should redirect to joyandchaosshop.com/blog/post-name. Preserve existing links and SEO signals, and identify any URLs that need individual mapping.
• **Keep all WordPress functions working through the proxy.** This includes posts, categories, tags, on-site search, images, internal links, comments, contact forms, email sign-ups, free file downloads, RSS feeds, Yoast, and WP-Admin access. Internal links, canonical URLs, and XML sitemaps should use the new public-facing URLs where appropriate. BigCommerce pages and domain email should remain unaffected.
• Preserve existing redirects. Audit and carry over all existing WordPress and Cloudflare redirects, including older or renamed post URLs. Update them to send visitors directly to the correct final page under joyandchaosshop.com/blog using a 301 redirect, avoiding redirect chains or loops. Include these redirects in the testing checklist.
• **Test before launch.** Use staging to verify the proxy, redirects, and functions listed above. Check for broken links, redirect loops, and conflicts with BigCommerce’s existing /blog route. Please flag any limitations or additional requirements before starting.
• **Provide a concise hand-off document.** Include the Worker code, supporting rules, any DNS or BigCommerce changes, a completed test checklist, and instructions for rolling back if needed.
I’ll provide the necessary Cloudflare and hosting access, plus staging URLs for testing before we go live.
Please confirm that this approach is feasible with our setup and let me know your proposed scope, timeline, and cost.
Here’s what I need done:
• **Configure the reverse proxy and permanent redirects.** Set up a Cloudflare Worker and any supporting rules so the public-facing blog lives at joyandchaosshop.com/blog. Anyone visiting an old blog URL should automatically be sent to its exact matching new page using a **301 permanent redirect**, rather than being sent to the blog homepage. For example, blog.joyandchaosshop.com/post-name should redirect to joyandchaosshop.com/blog/post-name. Preserve existing links and SEO signals, and identify any URLs that need individual mapping.
• **Keep all WordPress functions working through the proxy.** This includes posts, categories, tags, on-site search, images, internal links, comments, contact forms, email sign-ups, free file downloads, RSS feeds, Yoast, and WP-Admin access. Internal links, canonical URLs, and XML sitemaps should use the new public-facing URLs where appropriate. BigCommerce pages and domain email should remain unaffected.
• Preserve existing redirects. Audit and carry over all existing WordPress and Cloudflare redirects, including older or renamed post URLs. Update them to send visitors directly to the correct final page under joyandchaosshop.com/blog using a 301 redirect, avoiding redirect chains or loops. Include these redirects in the testing checklist.
• **Test before launch.** Use staging to verify the proxy, redirects, and functions listed above. Check for broken links, redirect loops, and conflicts with BigCommerce’s existing /blog route. Please flag any limitations or additional requirements before starting.
• **Provide a concise hand-off document.** Include the Worker code, supporting rules, any DNS or BigCommerce changes, a completed test checklist, and instructions for rolling back if needed.
I’ll provide the necessary Cloudflare and hosting access, plus staging URLs for testing before we go live.
Please confirm that this approach is feasible with our setup and let me know your proposed scope, timeline, and cost.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.