Customizing Shopify URL Prefixes: A Deep Dive into Cloudflare Workers for Localization

Hey there, fellow store owners! We’ve all been there, right? You’re building your dream e-commerce site on Shopify, and you want every detail to be perfect, especially for your local audience. One common question that sparks lively discussion in our community is about localizing those default Shopify URL prefixes like /products, /collections, and /pages. While Shopify lets you customize the slug, the part after the prefix, these prefixes themselves are pretty locked down. That’s exactly what Konstantinos (@venomkv13) from Greece ran into when he wanted to translate his URLs to Greek, like /συλλογές instead of /collections.

He came to the community with a Cloudflare Worker code snippet, hoping to use it for URL redirection. It’s a clever idea, leveraging powerful tools like Cloudflare. But as the discussion unfolded, our experts quickly pointed out critical nuances.

The Challenge: Shopify's Fixed URL Structure

First off, let’s be clear: Shopify doesn’t natively provide an option to change these core URL prefixes. As Hardeep and Steve_TopNewYork explained, this is fundamental to their URL routing system. So, any solution will be a workaround, often introducing complexity.

Konstantinos’s initial thought was to use a Cloudflare Worker. He had a map in his code like "/products": "/προϊόντα". His intention was to turn an English prefix into a Greek one. But here’s the catch, as clawmama, Hardeep, and VikashJ pointed out: your mapping was actually running in the opposite direction from what you needed, Konstantinos!

The Worker's Job: Translating Back to Shopify

A visitor to your Greek e-shop will type or click on a URL like www.yourdomain.gr/συλλογές/my-product. Shopify, however, only understands www.yourdomain.gr/collections/my-product. So, your Cloudflare Worker needs to intercept the Greek URL and translate it back to the English equivalent before forwarding it to Shopify. If your Worker tried to turn /collections into /συλλογές for Shopify, it would lead to a 404 error!

VikashJ from Apploy provided a helpful correction to the Worker code, getting the direction right. Here’s how it should look:

export default {
  async fetch(request) {
    const url = new URL(request.url);
    const routes = {
      "/προϊόντα": "/products",
      "/συλλογές": "/collections",
      "/σελίδες": "/pages",
      "/ιστολόγιο": "/blogs",
      "/αρθρά": "/articles",
    };

    for (const [gr, en] of Object.entries(routes)) {
      if (url.pathname === gr || url.pathname.startsWith(gr + "/")) {
        url.pathname = url.pathname.replace(gr, en);
        return fetch(new Request(url.toString(), request));
      }
    }
    return fetch(request);
  },
};

The keys in the routes object are now the Greek prefixes, and the values are their English Shopify counterparts. This ensures that when a visitor requests /συλλογές/..., the Worker rewrites it to /collections/... internally before sending it off to Shopify.

Beyond the Initial Request: The HTML Rewriting Challenge

Here’s where it gets more intricate. As clawmama and VikashJ rightly flagged, simply fixing the initial URL rewrite isn’t enough for full localization. Imagine a visitor landing on your translated Greek URL, then clicking a product in your navigation. Shopify will still output internal links in its HTML response using default English prefixes (/products, /collections). This means your visitor would be bounced right back to an English path!

To truly fix this, your Cloudflare Worker would need a second stage: intercepting Shopify’s HTML response and rewriting all matching href attributes (and canonical tags, pagination links, etc.) before sending the page to the user. This requires Cloudflare’s powerful HTMLRewriter, adding significant complexity.

Setting Up Your Cloudflare Worker: The Infrastructure Checklist

Before any code can do its magic, your Cloudflare setup needs to be just right. Steve_TopNewYork, Hardeep, and VikashJ all emphasized these crucial points:

1. Worker Route: Attach your Worker to the correct route, typically yourdomain.com/* to catch all requests.
2. DNS Record: Your domain’s DNS record for your Shopify store must be set to Proxied (orange cloud) in Cloudflare. If it’s DNS-only (grey cloud), the Worker won’t intercept traffic.
3. Confirm Worker Activation: Add a temporary console.log('Worker hit!'); inside your Worker’s fetch function or return a test header to verify it’s being triggered.

Weighing Your Options: Is a Full Proxy Worth It?

While a Cloudflare Worker can achieve URL prefix translation, the community discussion highlighted the significant long-term maintenance cost. As clawmama put it, you’d essentially be taking on responsibility for:

• HTML link rewriting (every internal link!)
• Canonical tags, redirects
• Cart and checkout transitions (tricky with proxies)
• App routes, sitemaps
• Regression testing after every theme change or Shopify update

That’s a lot to manage, becoming your team’s permanent responsibility. For a business-like solution, you need to consider if this ongoing effort is sustainable.

The Shopify Markets Advantage

This is why Hardeep, clawmama, and VikashJ strongly suggested looking into Shopify Markets. It’s Shopify’s native solution for international and multi-language stores. While it doesn't change those core URL prefixes (/products, /collections), it allows you to:

• Translate all your content (product descriptions, page content, menu items).
• Set up localized domains or subfolders (e.g., yourdomain.com/gr for Greek).
• Handle pricing, currencies, and taxes for different regions.

Shopify Markets is built into the platform, handles many complexities automatically, and significantly reduces the maintenance burden compared to a custom proxy. You keep Shopify’s fixed paths, but your content is fully localized.

So, where does this leave us? For Konstantinos and other store owners aiming for full URL prefix localization, it’s a balancing act. The Cloudflare Worker approach is technically possible with the right code and infrastructure, but it introduces significant complexity and ongoing maintenance. For most businesses, Shopify Markets offers a robust, native, and much more manageable solution for providing a fully localized experience, even if those core prefixes remain in English. It’s all about weighing the benefits of absolute URL control against the long-term operational costs.