A hostname alias is required if you want to create short,
meaningful URLs for external search engines to index. Assign at least one
hostname alias that is the current hostname on which the instance is
running.
Required Editions
Available in: B2C Commerce
You can also create a simpler alias
that reflects your store or brand name. Putting a simple Page URL in the
alias list, such as "www.mystore.com", enables users to get to the
storefront without typing in the full Salesforce B2C Commerce URL, such
as:
Ideally, the long URL is only visible to search
engines if someone posts a link containing the long URL.
Important If you don't assign an alias to your site, enabling
search-friendly URLs causes the storefront to show a 404 error for all
URLs besides the Welcome page.
Click App Launcher , and then select
Merchant Tools | Site | SEO & Discoverability | Aliases.
On the Aliases page, create a set of hostname alias rules.
If you want to test that your rules are valid JSON, we recommend that you test them
against a debugging tool. Remember to remove any comments from your mapping files and use
colons (:) instead of equal signs (=) to separate property and value.
Site URL aliases files are
instance-specific, so site URL aliases are individually managed for
each instance (Development, Staging, and Production). Because each
instance has its own aliases file, these files are not included in
data replication. This ensures that a data replication of Site
URL Management doesn't overwrite URL alias settings on
Production with the Staging configuration.
Individually edit the site URL
aliases on each instance (Development, Staging, Production) to have
the same aliases on all instances.
When you are satisfied that your alias file is valid, copy it
into the editor and click Apply.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.