ssossossosso
Documentation Home »SEO Configuration Guide »Website Configuration
current version

Website Configuration

This section guides you through the OroCommerce Front Store website-related system configuration options.

Routing

You can control the way OroCommerce routes the HTTP requests to the components that service these requests. Some of these options may be configured only globally, on a system level, and some are applicable to the individual websites.

Sitemap

A sitemap is a file that explains the structure of your site to the search engines. Sitemap helps improve indexing the site contents by the search engine (e.g. by providing metrics like page priority, update frequency and content uniqueness).

OroCommerce automatically generates the sitemap files for every website based on the routing configuration (e.g. secure vs insecure website URL, direct vs system canonical URLs, page priority configuration, etc). Sitemap files for the default website are stored in the web/sitemaps/actual/ folder. To communicate the sitemap location to the external search engines, the sitemap files generated for the default website are mentioned in the robots.txt file in the OroCommerce root folder.

Note

Only one sitemap may be included in the robots.txt file. To help search engines index the websites other than the default one, a webmaster can manually upload the automatically generated sitemap files using dedicated webmaster tools exposed by the search engine provider.

The frequency of the sitemap files generation (e.g. daily) depend on the system configuration.

You can launch the sitemap generation manually using the following command:

oro:cron:sitemap:generate

Routing and Sitemap Configuration

OroCommerce groups website configuration options into the following categories:

Global Routing Configuration

Global routing configuration includes the following information:

  • Global website URL when reached using secure (https) and insecure (http) connection
  • Options that impact the way metadata for the search engine is generated
  • Pretty URL support (e.g. /product/view/4 vs /500-watt-work-light)

Note

The website level configuration has higher priority and overrides this configuration settings.

To change the default global routing settings:

  1. Navigate to the system configuration (click System > Configuration in the main menu).

  2. Select System Configuration > Websites > Routing in the menu to the left.

    The Routing configuration page opens with the following options:

    • URL – Internal links and canonical URLs (meta keywords) on the OroCommerce Front Store pages may contain this value as the website base URL. This option value is used in internal links when a customer uses insecure (HTTP) connection. In the canonical links, it is used when the Canonical URL Security Type is set to Secure.

    • Secure URL – Internal links and canonical URLs (meta keywords) on the OroCommerce Front Store pages may contain this value as the website base URL. This option value is used in internal links when a customer uses secure (HTTPS) connection. In the canonical links, it is used when the Canonical URL Security Type is set to Insecure.

    • Canonical URL Type – this option defines whether the System URL or Direct URL should be used as a canonical link in the meta keywords in the page source code.

      Note

      Canonical link is used to help search engines identify the unique content that should be indexed.

      When System URL is selected, the page URL is built using the system path to the item and its ID (e.g. /product/view/4).

      When Direct URL is selected, the page URL is built using the page title (e.g. /500-watt-work-light).

    • Canonical URL Security Type – this option defines which value should be used as a website base URL in the canonical link in the page meta keywords. Supported options: Insecure and Secure.

      When Insecure is selected, the website base URL in the canonical link matches the URL value.

      When Secure is selected, the Secure URL value is used instead.

    • Create Redirects – this option defines a strategy for creating redirects when the URL building rules change. Supported options: Ask, Never, Always.

      When Ask is selected, OroCommerce prompts to confirm redirect creation on every change.

      When Never is selected, OroCommerce does not create any redirects.

      When Always is selected, the redirects are created by default.

    • Web Catalog – when a Web Catalog is selected, it populates the main menu and sub-menus on the OroCommerce Front Store. If there is no Web Catalog in OroCommerce, the Master Catalog structure is mimicked.

    • Website Matchers – with this option, you can define the way OroCommerce will identify the website customer uses. It is recommended to select at least one option. Supported options: ENV Variable Based, Cookie Based, URL Based. When more than one option is selected, set the method priority in the sort order column to define the most reliable and trusted one.
    • Enable Redirect – indicates whether the customer should be automatically redirected to the website that was identified using one of the website matching methods (e.g. user navigated to the us-store.com but their cookies indicate that they are visiting the uk-store.com).
    • Cookie Name – the name of the cookie that stores information about the current website in the customer’s browser.
    • Enable Direct URLs – when enabled, the page URL is built using the page title (e.g. /500-watt-work-light). When disabled, the system path to the item and its ID is used (e.g. /product/view/4).
    • Product URL Prefix – the prefix that is appended to the product slug in the URL.
    • Category URL Prefix – the prefix that is appended to the category slug in the URL.
    • Landing Page URL Prefix – The prefix that is appended to the landing page slug in the URL.
  3. To customize any of these options:

    1. Clear the Use Default box next to the option.
    2. Select the new option.
  4. Click Save.

Routing Configuration Per Website

To control the way OroCommerce routes HTTP requests to the components when a customer uses particular website, you may provide the following website-specific information:

  • Global website URL when reached using secure (https) and insecure (http) connection
  • Options that impact the way metadata for the search engine is generated
  • Information for the website identification (cookie value and/or environment variable).

Note

The website level configuration overrides global routing configuration, when Use System box is cleared.

To change the default routing settings for the website:

  1. Navigate to System > Websites in the main menu.

  2. For the necessary website, hover over the more actions menu to the right of the necessary website and click to start editing the configuration.

  3. Select System Configuration > Websites > Routing in the menu to the left.

    The following page opens.

    • URL – Internal links and canonical URLs (meta keywords) on the OroCommerce Front Store pages may contain this value as the website base URL. This option value is used in internal links when a customer uses insecure (HTTP) connection. In the canonical links, it is used when the Canonical URL Security Type is set to Insecure.

    • Secure URL – Internal links and canonical URLs (meta keywords) on the OroCommerce Front Store pages may contain this value as the website base URL. This option value is used in internal links when a customer uses secure (HTTPS) connection. In the canonical links, it is used when the Canonical URL Security Type is set to Secure.

    • Canonical URL Type – this option defines whether the System URL or Direct URL should be used as a canonical link in the meta keywords in the page source code.

      Note

      Canonical link is used to help search engines identify the unique content that should be indexed.

      When System URL is selected, the page URL is built using the system path to the item and its ID (e.g. /product/view/4).

      When Direct URL is selected, the page URL is built using the page title (e.g. /500-watt-work-light).

    • Canonical URL Security Type – this option defines which value should be used as a website base URL in the canonical link in the page meta keywords. Supported options: Insecure and Secure.

      When Insecure is selected, the website base URL in the canonical link matches the URL value.

      When Secure is selected, the Secure URL value is used instead.

    • Web Catalog – when a Web Catalog is selected, it populates the main menu and sub-menus on the OroCommerce Front Store. If there is no Web Catalog in OroCommerce, the Master Catalog structure is mimicked.

    • Cookie Value – a unique website ID that is saved in the cookies and is later used by a website matcher to identify the website customer is on. The cookie name is configured on the system level.

    • ENV Variable Name – an environment variable that is used to store the unique website ID that is later used by a website matcher to identify the website customer is on.

    • ENV Variable Value – a unique website ID that is saved to the environment variable with the name defined in the option above.

  4. To customize any of these options:

    1. Clear the Use System box next to the option.
    2. Select the new option.
  5. Click Save.

Global Sitemap Configuration

You can control the way sitemap is generated for all website in OroCommerce.

Note

The website level configuration has higher priority and overrides this configuration settings.

To change the default global sitemap settings:

  1. Navigate to the system configuration (click System > Configuration in the main menu).

  2. Select System Configuration > Websites > Sitemap in the menu to the left.

    The following page opens.

    The frequency and priority options may be configured globally or specifically for product, category and the cms page level.

  3. To customize any of these options:

    1. Clear the Use Default box next to the option.
    2. Select the new option.
  4. Click Save.

Sitemap Configuration Per Website

You can control the way sitemap is generate for the specific website in OroCommerce.

Note

The website level configuration overrides global sitemap configuration.

To change the default sitemap settings for the website:

  1. Navigate to the system configuration (click System > Websites in the main menu).

  2. For the necessary website, hover over the more actions menu to the right of the necessary website and click to start editing the configuration.

  3. Select System Configuration > Websites > Sitemap in the menu to the left.

    The following page opens.

    The frequency and priority options may be configured globally or specifically for product, category and the cms page level.

  4. To customize any of these options:

    1. Clear the Use System box next to the option.
    2. Select the new option.
  5. Click Save.