URL Keys and URL Rewriting in Magento EE 1.13.0.0 and 1.13.0.1

Magento EE 1.13 includes significant performance enhancements for indexing:

  • Full reindexing is now required in very limited situations.
  • Most indexing processes now run only to update products, categories, URL redirects, and so on that have changed—eliminating the need for manual full reindexing.
  • During the time reindexing is in progress, your web store is accessible (that is, your web store is not locked).
  • Reindexing time has been dramatically reduced.
    For performance metrics, see Magento Enterprise Edition 1.13 Benchmarking.
  • Reindexing is now a background process.
  • Magento uses Materialized Views for database access, which reduces processing time and overhead.

See one of the following sections for more information:

How Reindexing Works in EE 1.13

See one of the following sections:

About URL Keys and URL Rewriting Improvements in Magento EE 1.13.0.0 and EE 1.13.0.1

One of the results of the performance improvements made to URL rewrites in EE 1.13.0.0 and 1.13.0.1 is that URL keys must be globally unique—meaning, among all webstores and store views. There are several things for you to be aware of—whether you're installing EE 1.13.0.0 and 1.13.0.1 for the first time or whether you're upgrading from an earlier EE release.

How URL Keys Work in New Magento EE 1.13.0.1 Installations

To facilitate URL key uniqueness, Magento EE 1.13.0.1 and 1.13.0.1 create a unique key for you when you add a product or category with the same name as an existing product or category. (EE 1.13.0.0 does not allow you to create a product or category that has a duplicate URL key.)

For example, if you already have a category named Apparel/Shoes and you create a category named Specials/Shoes, the second category's URL key is the category name separated from its ID by a dash character (for example, shoes-42). Duplicate URL keys for products work the same way.

By default, URLs for products assigned to same-named categories are:

  • Original category: http://www.example.com/apparel/shoes/kenneth-cole-new-york-men-s-con-verge-slip-on.html
  • New duplicate category: http://www.example.com/shoes-42/kenneth-cole-new-york-men-s-con-verge-slip-on.html

Note: To optionally create additional URLs to access a product (for example, a URL that doesn't contain the category name), see the documentation on URL redirects.

Additional Information About URL Keys After an Upgrade

During the upgrade process, Magento moves your existing URL keys as-is and also creates new URL keys. All URLs are rendered in the top navigation bar in your web store.

For example, suppose that before the upgrade you had a category named Women's/Shoes with the URL http://www.example.com/womens/shoes.html. After upgrading, you will have two URLs:

  • Original URL: http://www.example.com/womens/shoes.html
  • New URL: http://www.example.com/shoes.html

The new URLs have minimal to no impact on search engines because all URLs can be used to access categories and products. In addition, there are fewer total URLs created for products and categories, which maximizes search engine optimization.

Note: URLs like the preceding examples are available after the indexers run following an upgrade. In EE 1.13.0.0 and 1.13.0.1, most indexers run automatically according to the schedule set in your Magento cron job. Make sure you configure the cron job immediately after your upgrade. In most cases, you must also refresh the page cache and flush the Magento cache as well.

Discussion:

RSS: New Article posts

Explore the Knowledge Base