---
schema_version: "1"
id: 69a28b09b0fdeb2c470012a0f13b4a7072601353992dc9dc88f1e88b300f9a11
title: Configure Site URL Aliases for .my Domains
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_configure_site_url_aliases_for_my_domains.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_configure_site_url_aliases_for_my_domains.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: c7dde7d549bc05578a060c1363c020bbf8443c4272abc798d03d2f4994dbb32f
description: Prevent cross-origin (CORS) errors after your B2C Commerce storefront moves to the .my Default Domain, manually add the .my hostname to your site URL aliases file.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Configure Site URL Aliases for .my Domains

Prevent cross-origin (CORS) errors after your B2C Commerce storefront moves to the `.my` Default Domain, manually add the `.my` hostname to your site URL aliases file.

[Which Salesforce Commerce Product Do I Have?](https://help.salesforce.com/s/articleView?id=commerce.comm_what_product.htm&language=en_US)

Without the current `.my` storefront hostname in the aliases file, generated storefront URLs can resolve to a different host than the browser's origin, which breaks features that rely on same-origin requests, such as Page Designer preview. This gap commonly appears after the 26.6 default-domain auto-routing on On-Demand Sandboxes (ODS). Add the hostname on each instance that serves the storefront on the Default Domain.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note Site URL aliases files are instance-specific and aren't included in data replication. Individually edit the site URL aliases on each instance (development, staging, production) so that every instance includes the `.my` storefront hostname.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_tip.png)

Tip If external integrations or test automation reference the previous `.dx` storefront hostname, update them to use the new `.my` hostname. Also update any CORS allowed-origins lists and third-party service allowlists so that requests to the `.my` storefront aren't blocked.

1. In Business Manager, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Administration** | **Sites** | **Embedded CDN Settings**. Check to see if the `.my` storefront hostname is on the Embedded CDN Settings page. For ODS instances, the format is `<instance>.sbx.my.commercecloud.salesforce.com`.
2. If the `.my` hostname isn't listed in the aliases file, add it.
    1. In Business Manager, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Merchant Tools** | **site** | **SEO & Discoverability** | **Aliases**.
    2. Add the `.my` hostname as a hostname entry. Set it as the `http-host` and `https-host` in the `settings` section, or add a hostname rule for it, so that generated storefront URLs use the same host that shoppers and preview tools request. For syntax and examples, see [Hostname Aliases for B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_hostname_aliases.htm&type=5&language=en_US).
    3. Click **Save**.