How do I keep my blog or shop on a subfolder of my main site instead of a separate subdomain?

This page may contain affiliate links from which Blur Studio earns commissions.

This comes up constantly when a business runs its main site on one platform but needs a specialized tool, a blog platform with better publishing tools, a dedicated shop system, for a specific part of the site. The question is how to make that feel like one cohesive website rather than two visibly disconnected ones living on entirely different domains.

Why a subfolder beats a subdomain for this

yoursite.com/blog and blog.yoursite.com look similar to a visitor, but they're treated quite differently by search engines. A subdomain is often evaluated somewhat independently of your main domain's authority, while a subfolder is generally seen as part of the same site, inheriting more of your main domain's existing trust and ranking signal. For content you want contributing to your main site's overall SEO, rather than building up a separate pool of authority on its own, a subfolder is usually the better structural choice.

How Netlify's proxy redirect actually works

Netlify is the hosting platform that builds and serves your main site from its connected code, and it reads its routing rules from a plain configuration file called netlify.toml. A normal redirect sends the visitor's browser to a different URL, visible in their address bar. A proxy redirect is different: it fetches content from another location and serves it back under your original URL, so the visitor's browser never sees the other domain at all. In netlify.toml:

[[redirects]]
  from = "/blog/*"
  to = "https://your-blog-platform.com/:splat"
  status = 200
  force = true

The key detail is status 200, not 301 or 302. A 200 status tells Netlify to proxy the content transparently rather than redirect the visitor's browser; the page loads at yoursite.com/blog/your-post, but the actual content is being fetched from your-blog-platform.com behind the scenes.

The real dependency risk, stated plainly

This setup works well right up until the platform you're proxying to changes something, moves a URL structure, changes how it serves content, or has downtime, and your main site's subfolder breaks along with it, even though your main site itself didn't change at all. You don't control the other platform's stability, and proxying doesn't give you any buffer against that; it just makes the dependency invisible to visitors until something breaks.

This is a real tradeoff, not a hypothetical. If the proxied tool is a mature, stable platform you're not actively migrating away from, the risk is usually acceptable. If it's a newer tool, or one you're already unsure about long-term, you're building a dependency into your main site's URL structure that's harder to unwind later than it looks now, since every indexed URL under that subfolder depends on the arrangement continuing to work.

Advanced proxy options worth knowing

Netlify's proxy redirects also support custom headers and signed requests for cases where the destination needs authentication or specific headers to serve content correctly:

[[redirects]]
  from = "/shop/*"
  to = "https://api.yourshopplatform.com/:splat"
  status = 200
  force = true
  headers = {X-From = "Netlify"}
  signed = "API_SIGNATURE_TOKEN"

The signed option references an environment variable holding a secret token, which Netlify includes with the proxied request so the destination can verify it's genuinely coming from your site rather than an arbitrary request. This matters if the platform you're proxying to needs to confirm the request's authenticity before serving content, rather than responding to any request that hits its URL.

A worked example: a Shopify shop proxied onto a marketing site

A small brand ran its marketing site as a static Netlify site but used Shopify for the actual storefront, and wanted the shop to live at yoursite.com/shop rather than a separate shop.yoursite.com subdomain, mainly to keep the SEO benefit of product pages contributing to the main domain's authority rather than building up a separate, disconnected pool of ranking signal on a subdomain. Setting up the proxy redirect took an afternoon: pointing /shop/* at Shopify's storefront with status 200, testing that product pages, cart and checkout all loaded correctly under the new path, and confirming Shopify's own analytics still tracked visits correctly despite the URL appearing to come from the main domain.

The real payoff showed up months later during a product launch: a blog post on the main site linking directly to a /shop/ product page passed along meaningfully more of its own ranking value than it would have linking to a separate subdomain, since search engines treated the whole thing as one connected site rather than two. The dependency risk was explicitly accepted going in: Shopify is a large, stable platform unlikely to change its underlying structure unpredictably, which is exactly the kind of case where the SEO benefit is worth the tradeoff.

Common mistakes with proxy redirects

• Proxying to a platform you're already unsure about long-term. If there's a real chance you'll switch platforms within the next year, the dependency risk outweighs the SEO benefit; use a subdomain instead until you're confident in the platform choice.
• Forgetting to test the full user flow, not just the landing page. A shop or blog proxy needs checkout, search, and pagination all verified working under the new path, not just confirming the homepage of the proxied section loads correctly.
• Not monitoring for when the proxied platform changes something. Since the dependency is largely invisible until it breaks, a periodic manual check (does /shop/ still load correctly) catches problems before customers do.

What I'd actually tell you

The SEO benefit of a subfolder over a subdomain is real and worth having, but weigh it against how much you trust the platform you're proxying to staying stable. For an established blog platform or shop system you're committed to long-term, this is a solid, well-understood setup. If you're still evaluating that platform or might switch again soon, consider whether the SEO gain is worth building a structural dependency you'll need to carefully unwind if you do move on.

When to skip this and use a subdomain instead

If the platform you're connecting to is actively unstable, frequently changes its URL structure, or you're not confident it'll still be your choice in a year, a subdomain is the lower-risk option. It's a smaller SEO tradeoff than dealing with a broken subfolder because the underlying platform shifted under you without warning.

How I'd approach this

I set up proxy configurations like this regularly when a business needs a specialized tool to feel native to their main domain. Where I add real value beyond the basic setup is making sure the arrangement is resilient, monitoring for when the proxied platform changes something, and having a clear fallback plan if it ever needs to be unwound. If you're weighing a proxy setup like this against a subdomain, I'll give you a straight read on which risk profile actually fits your situation.