Manage Site Domains URLS and Other Site Details

Manage site domains, URLs, and other site details

The Site Details page in OrchestraCMS Setup contains a variety of site properties, some of which need to be modified under certain circumstances.

The following is a list of the properties included on the Site Details page and instructions about when they should be modified.

Edit site properties

In OrchestraCMS Setup, under Site, click Details.
On the Site Details page, click Edit.
Edit site properties as required, and then click Save.

Properties on Site Details page

Field label	Purpose
Site Name	The name of the site that was provided when the site was created. This field can’t be modified.
Site Domain	The domain of the site. This field only needs to be modified under certain circumstances, such as a full sandbox refresh (the field needs to be populated with the sandbox domain instead of the production domain) or when a custom domain is being used (the field needs to be populated with the custom domain instead of the Force.com domain).
Site Secure Domain	The secure domain of the site. This only needs to be populated if the Salesforce organization is hosted on its own server (not a standard shared Salesforce server) and the site has its own security certificate. If applicable, the site secure domain is often the same as the site domain.
Site Prefix	If this is not the only site you have in your Salesforce organization, the site prefix is the additional path that was entered during site creation to distinguish the site from other sites in the organization. For example, if the site URL is http://example.force.com/support, the site prefix is “support”. This is automatically populated from Salesforce.
Site URL	The URL for the site. This field only needs to be modified under certain circumstances, such as a full sandbox refresh (the field needs to be populated with the sandbox URL instead of the production URL) or when a custom domain is being used (the field needs to be populated with a URL that uses the custom domain instead of the Force.com domain).
Site Secure URL	The secure URL for the site. This only needs to be populated if the Salesforce organization is hosted on its own server (not a standard shared Salesforce server) and the site has its own security certificate. This URL should use HTTPS.
Site Guest User	The Salesforce guest user profile that is associated with the site; this field is not set by default. Click Change User, and in the Find User dialog, select the guest user profile that is associated with the site. This field must be populated before you can use the OrchestraCMS Private Sharing feature.
Package Prefix	The prefix of the OrchestraCMS installed managed package (cms). This field can’t be modified.
Salesforce Instance	The Salesforce instance that the Salesforce organization resides on (i.e., na14, cs10). This field can’t be modified.
Model Version	A reference number for customer support to determine if an OrchestraCMS upgrade requires data migration. This field can’t be modified.

Enable unique URLs

An OrchestraCMS System Administrator or Site Administrator can enable unique URLs for your site. This option reduces the number of ways that people can access each page, which can improve search engine optimization by eliminating the possibility of the total number of page hits being split between multiple URLs. By enabling unique URLs, there are only two types of URLs available:

Vanity URLs. Additional URLs can be added to a page on the properties dialog, which is accessed from the page editor. These URLs are static regardless of whether the page is in the site map. For example, if a page called Case Studies has an additional URL of success-stories, the URL will be in the format www.example.com/success-stories.

Site Map URLs. When a page is in the site map, its URL is constructed using the URL Name field, configured on the Manage Pages section, and the page’s position in the site map. For example, if the About page in the following site map had a URL Name of about, and the Our Team page had a URL Name of our-team, the URL for the Our Team page would be in the following format: www.example.com/about/our-team.

The maximum number of pages you can have in the Site Map is determined by the number of languages in use for each page, and the number of URLs for each page. As a consequence, there is no definitive maximum number we can quote. As a guide, we have successfully tested Site Map with a single site language and 450 pages; but this number could be significantly impacted by the number of active languages on your site. The maximum number of levels you can have in the Site Map hierarchy is 6 including the top-level Site Map node (i.e. you can have 5 levels including the home page node).

When unique URLs are not enabled, all pages are associated with a URL that uses the Unique URL Name of the page in the format www.example.com/URL-Name. These URLs are not available after unique URLs are enabled.

Keep in mind that if a page is in the site map and has a vanity URL, there will be at least two URLs that the page can be accessed from even if unique URLs are enabled. Also, users are still able to add multiple vanity URLs to a page.

To enable unique URLs

In OrchestraCMS Setup, under Site, click Details.
Under URL Options, click to select the Enable Unique URLs check box or the Enable Case-sensitive URLs check box.
Click Save.

Enable case-sensitive URLs

Unless URL case sensitivity is enabled for a site, URLs for pages created in OrchestraCMS are case insensitive. This means that www.example.com/about and www.example.com/About would return the same page. When URLs are case sensitive, only the URL that uses the correct case directs the user to the page, while all other forms of the URL return a 404 error. Using the previous example, if www.example.com/about is the correct case for the URL, then www.example.com/About would return a 404 error.

Case-sensitive URLs are not mandatory in the HTML specification, but they can improve search engine optimization. If a URL is case insensitive, search engines may determine that www.example.com/about and www.example.com/About are two different pages, which would cause each version of the URL to have a lower search engine ranking that a single, case-sensitive URL would have.

To enable case-sensitive URLs

In OrchestraCMS Setup, under Site, click Details.
Under URL Options, click to select the Enable Case-sensitive URLs check box.
Click Save.

Disable superfluous span tags

By default, span tags are added to the HTML markup of pages created in OrchestraCMS wherever the platform deems them to be necessary. You can now prevent these additional span tags from generating, which can simplify the development of page and content templates.

It is not recommended that you disable these span tags on an existing site. Your pages may already rely on the span tags being there. We recommend that you always consult your page template developer before selecting this option.

To disable superfluous span tags

In OrchestraCMS Setup, under Site, click Details.
On the Site Details page, click Edit.
Under Markup Options, click to select the Disable Superfluous Span Tags check box.
Click Save.

Enable server-side cache injection

When an OrchestraCMS page includes dynamically rendered content, the page cache includes dynamic load tags that indicate dynamic content needs to be loaded after the initial page load. Although this results in a fast page load time, it means that search engines can’t detect any of the dynamic content. The experimental option to enable server-side cache injection solves this problem. Server-side cache injection post-processes the cache before returning it to the browser, which makes dynamic content visible to search engines. The page load time might be increased with this option enabled, but it will still be significantly faster than a full-page render.

To enable server-side cache injection

In OrchestraCMS Setup, under Site, click Details.
Under Search Engine Options, click to select the Enable Server Side Cache Injection (Experimental) check box.
Click Save.