How to Use Indexing Improvements in Magento Enterprise Edition (EE) 1.13 and Later

Table of Contents

Note: The information in this article applies to Magento Enterprise Edition 1.13 and later only—including Magento Enterprise Edition 1.14.

Overview

Indexing is how Magento transforms data such as products, categories, and so on, to improve the performance of your web store. As data changes, the transformed data must be updated—or reindexed. Magento has a very sophisticated architecture that stores lots of merchant data (including catalog data, prices, users, stores, and so on) in many database tables. To optimize web store performance, Magento accumulates data into special tables using indexers.

For example, suppose you change the price of an item from $4.99 to $3.99. Magento must reindex the price change to display it on your web store.

Without indexing, Magento would have to calculate the price of every product on the fly—taking into account shopping cart price rules, bundle pricing, discounts, tier pricing, and so on. Loading the price for a product would take a long time, possibly resulting in cart abandonment.

See one of the following sections for more information:

How Reindexing Works in EE 1.13.0.0 and 1.13.0.1

For details, see URL Keys and URL Rewriting in Magento EE 1.13.0.0 and 1.13.0.1.

Search Engine Optimization (SEO) in EE 1.13.0.2

For details, see Search Engine Optimization (SEO) Changes in Magento Enterprise Edition (EE) 1.13.0.2.

What Causes Reindexing

In the Magento EE 1.13 release, Magento changed what causes reindexing:

Type of indexing Magento method name What causes reindexing
Product prices catalog_product_price
  • Add customer group
  • Change configuration settings
Flat catalog product data† catalog_product_flat
  • Add store
  • Add store group
  • Add, edit, or delete attribute (for searching and filtering)
Flat catalog category data† catalog_category_flat
  • Add store
  • Add store group
  • Add, edit, or delete attribute (for searching and filtering)
Catalog category/product index catalog_category_product
  • Add, edit, or delete products (single, mass and import)
  • Change product-to-category relations
  • Add, edit, or delete categories
  • Add or delete stores
  • Delete store groups
  • Delete websites
Catalog search index catalogsearch_fulltext
  • Add, edit, or delete products (single, mass and import)
  • Add or delete stores
  • Delete store groups
  • Delete websites
Stock status index cataloginventory_stock Change configuration settings (in the Admin Panel, System > Configuration. In the CATALOG group, click Inventory.)
Category permissions index catalogpermissions Add store, store group, add or delete or update attribute (for searching and filtering)
† — The flat product and category indexers also influence how catalog and shopping cart price rules are indexed. If you have a large number of SKUs (about 500,000 or more), you'll notice a dramatic improvement in indexing time for price rules. To take advantage of this improvement, you must enable flat catalog product option as discussed in Flat Catalog Prerequisite: Enabling Frontend Options.

Details About EE 1.13 Reindexing

The following table provides more detail about how items are reindexed in EE 1.13.

Action that triggers reindexing Type of reindexing that results How you control when reindexing occurs
A variety of things, including (for most indexers) creating a new web store or new customer group. For complete details, see List of Actions that Cause a Full Reindex. Full reindex Full reindexing is performed on the schedule determined by your Magento cron job. (In a few cases, full reindexing must be performed manually. See the next section.)
  • Bulk loading of items in any of the following ways:
    • Magento import/export
    • Direct SQL query
    • Other methods that add, change, or delete data in the database directly
  • Changing scope (for example, from global to website)
Partial reindex (that is, only changed items are reindexed) At the frequency determined by your Magento cron job.
All other actions (for example, changing a single product attribute or price using the Admin Panel). Partial reindex (that is, only changed items are reindexed) Scheduled by your cron job. (In a few cases, full reindexing must be performed manually. See the next section.)

Understanding the Updated Index Management Page

Because of changes to the way indexing works, the Index Management page in the Admin Panel has changed. The following sections discuss how you use the information on this page:

Viewing the Index Management Page

First, log in to the Admin Panel as an administrator and click System > Index Management. The following page displays:

The page displays differently if you:

  • Enabled the Solr search engine for full-text catalog search
    (In the Admin Panel, click System > Configuration > CATALOG > Catalog. In the right pane, expand Catalog Search and, from the Search Engine list, click Solr.)
    More information about Solr
  • Enabled flat the catalog product option
    (In the Admin Panel, click System > Configuration > CATALOG > Catalog. In the right pane, expand Frontend and, from the Use Flat Catalog Category and Use Flat Catalog Category lists, click Yes.)
    More information about these options

The following figure shows an example of all of those options enabled.

Note: The indexers with check boxes next to their names must be managed manually as discussed in this section. The other indexers update automatically according to the schedule set in your Magento cron job.

Following is how the page looks with all indexers updated—either by cron or manually:

Understanding the Columns on the Index Management Page

The following table discusses the meaning of the columns on this page.

Column name Description
Index Name of the indexer.
Description Description of the indexer.
Mode Applies only to the indicated indexers. In the preceding figures, most of the indicated indexers are set to Update on Save, which means a reindex is required when a change is saved in the Admin Panel. To change this option, see How to Manually Reindex.
Status

Displays one of the following:

  • Reindex Required if a change has been made that requires reindexing. If a check box and Reindex Required link displays in that row, you can manually reindex as discussed in How to Manually Reindex.
  • Ready if the index is up-to-date.

The following options apply only to the automatic indexers; that is, the indexers you don't have to update manually.

  • Scheduled if reindexing is required but hasn't run yet according to your Magento cron job.
  • Running if reindexing required and is either running now or is waiting in queue.
  • Outdated indicates reindexing is required but there is an issue preventing it from running. If this state persists, submit a bug report.
Update Required Applies only to the indicated indexers. Indicates whether or not you must manually reindex. (The value in the Mode column indicates whether the index must be manually updated.)
Updated At Displays the date and time an index was last manually updated, or Never if the index has never been manually updated.
Action Indexers that require manual updating display a Reindex Data link. Click the link to reindex that option only.

Understanding Manual Reindexing Options

If the Status column displays Reindex Required and the Update Required column displays No, when you manually reindex, the result is a partial reindex.

If the Status column displays Reindex Required and the Update Required column displays Yes, when you manually reindex, the result is a full reindex.

The following figure shows an example of one index that requires a full manual reindex (Product Attributes), partial manual reindex (Catalog Search), and an index that is up-to-date (Tag Aggregation Data).

How to Manually Reindex

For the indexers that require manual updates, you have the following options on this page. None of the following options are available for the indexers that update automatically.

The indexers that require manual updates display with a check box next to their name (Product Attributes, Tag Aggregation Data, and, optionally, Catalog Search Index).

Task Steps to perform task
Manually reindex

To manually update one or more indexers:

  • To update more than one indexer at a time, select the check box next to its name. From the Action list, click Reindex Data and click Submit.
  • To update one index only, click the Reindex Data link in the Action column on the right.
Change the indexing mode

By default, indexers that require manual updating are set to Update on Save which means reindexing occurs after a change is made in the Admin Panel.

The other option is to manually reindex every time a change is made. (For example, if you change product attributes in the Admin Panel, you must manually update the Product Attributes index.)

To change the indexing mode:

  1. Select the check box next to one or more indexers to change.
  2. From the Actions list, click Change Index Mode.
    This causes the Index Mode list to display.
  3. From the Index Mode list, click the desired option.
  4. Click Submit. The value in the Mode column updates to indicate your choice.

Understanding SEO Configuration Options (EE 1.13.0.2 and Later Only)

Because of the SEO changes in EE 1.13.0.2, you have new and recommended options for improving SEO on your web store:

New Option: Priority for Duplicated URL Keys

This option determines which URL "wins" if a user chooses a link to an allowed duplicate URL key. For example, a category and product can both have a URL key of shoes; this setting enables you to choose which URL you prefer the user to see.

For details, see Prioritizing URL Resolution.

Using Canonical Links for Categories and Products

Magento recommends you enable both of the following options, which are located in the right pane by going to System > Configuration > CATALOG > Catalog > Search Engine Optimizations:

  • Use Canonical Link Meta Tag For Categories
  • Use Canonical Link Meta Tag For Products

These settings put a canonical link in the <head> block on a product or category page. This link is a hint to search engines as to what your preferred URL is, and tends to give that link greater weighting.

For example, if a product is associated with multiple categories, a canonical URL enables you to specify which product link you want search engines to index.

Note the following:

  • If Use Canonical Meta Tag for Categories is enabled, the category page on your web store includes a canonical URL to the full category URL. For example, http://www.example.com/mens/shoes
  • If Use Canonical Meta Tag for Products is enabled, the product page includes a canonical URL to domain-name/product-url-key because product URL keys must be globally unique.
    If you also enable the option Use Categories Path for Product URLs, the canonical URL is still domain-name/product-url-key but the product can also be accessed using its full URL (including the category hierarchy). Examples:
    If the product URL key is producturlkey and it's assigned to the Apparel > Womens > Purses category, the product can be accessed using both of the following URLs:
    http://www.example.com/producturlkey
    http://www.example.com/apparel/womens/purses/producturlkey
The following figure shows an example of enabling the canonical link options.

Understanding Reindexing Configuration Options

This section discusses the following topics:

Configuring Partial Reindexing Options

Most indexers enable you to select one of the following scheduling methods:

  • Schedule the partial reindex immediately.
    This option enables the results of the reindex to display immediately on your Magento web store.
  • Scheduled by your Magento cron job.
    This option is appropriate for web stores that are experiencing high traffic load and in cases where many items are being updated at the same time by multiple users.

    Note: If multiple users are updating objects like products and attributes that cause reindexing, set all indexers to run as scheduled by your cron job. Otherwise, if you set indexers to run every time an object like a product is saved, Magento immediately reindexes all affected records. When multiple objects with interdepenncies are reindexed, deadlocks might occur. Symptoms of deadlocks include high CPU usage and MySQL errors. Scheduling indexing with your cron job prevents these deadlocks from occurring.

To set partial reindexing options:

  1. Log in to the Admin Panel as an administrator.
  2. Click System > Configuration.
  3. In the left navigation bar, from the ADVANCED group, click Index Management.
  4. Expand Indexing Options.
    The following figure shows an example.
  5. For the type of index, click one of the following:
    • Update on Save to immediately perform a partial reindex as soon as a change is made to an item.
    • Update when scheduled to schedule reindexing using your Magento cron job.
  6. For example, to schedule the category flat catalog and the category flat product index using your Magento cron job and to immediately reindex everything else, choose the following options.

  7. Click Save Config at the top of the page.

Configuring Other Reindexing Options

The following table shows which types of indexing require further configuration and which types require you only to configure the partial reindexing frequency.

Type of indexing Configurable?
Category and product indexer No, only configure the partial reindexing frequency.
Category URL redirect Yes and also configure the partial reindexing frequency.
Product URL redirect indexer Yes and also configure the partial reindexing frequency.
Redirect URL rewrite indexer No, only configure the partial reindexing frequency.
Category flat data indexer Yes and also configure the partial reindexing frequency.
Product flat data indexer Yes and also configure the partial reindexing frequency.
Price and stock indexer No, only configure the partial reindexing frequency.
Category permissions

No. Category permissions indexing occurs automatically; it is not configurable.

To enable category permissions in the Admin Panel, click System > Configuration. In the CATALOG group, click Catalog. In the right pane, expand Category Permissions.

Using URL Redirect Reindexing Improvements

URL redirecting (referred to in earlier Magento EE releases as URL rewriting and sometimes referred to as request rewriting) enables you to access resources such as product pages, categories, and so on, by additional uniform resource identifiers (URIs).

For example, suppose your web store has a product named Microsoft Natural Ergonomic Keyboard 4000 assigned to the Computer Peripherals category. By default, the product can be accessed using a URL like http://www.example.com/peripherals/microsoft-natural-ergonomic-keyboard-4000.html. URL redirect enables you to create an additional URL like http://www.example.com/great-keyboard.html

Using URL rewriting, you can choose a combination of:

  • Custom, category, or product URL redirect type
  • Request path which can be any valid URI (for example, for a seasonal promotion, you might want a product URL to end with best-valenties-gift.html)
  • Note: The request path has different requirements for EE versions 1.13.0.0 and 1.13.0.1, compared to EE 1.13.0.2 and later (including EE 1.14).

    • Starting in EE 1.13.0.2, every product request path must be globally unique. However, category request paths do not have to be unique.
    • In EE 1.13.0.0 and 1.13.0.1, every product and category request path must be globally unique.
  • Target path which specifies the actual path to the product or category (for example, for a promotion, you might want a category named spring-sale)
    Note: The custom and target path options enable you to redirect to a custom path, such as a Content Management System (CMS) path. The target path must be valid; otherwise, the redirect results in a 404 (Not Found) error on your web store.
  • Redirect type (determines how search engines rank the redirect)
    • None (useful if you don't want the customer to have to wait the additional time required to redirect)
    • Temporary (HTTP 302 (Found))
    • Permanent (HTTP 301 (Moved Permanently))
      Note: Magento recommends choosing a permanent redirect because search engines generally preserve the page's ranking. A 302 (Temporary) redirect does not preserve a page's ranking. For more information, consult a resource such as seomoz.org or google.com.

For more information, see one of the following sections:

Sample URL Redirects

Magento enables you to create redirects to add additional URLs for items. You can do this, for example, to make items more attractive to buyers. You can create a redirect to any valid path, including paths you create in your CMS.

For example, you can change the following product URL:

http://www.example.com/peripherals/microsoft-natural-ergonomic-keyboard-4000.html

and add another one such as:

http://www.example.com/best-keyboard.html

or you can create another URL for a category like:

http://www.example.com/all-on-sale.html

To create a category path like the following for a promotion, you must first create a path using the CMS or by other means.

http://www.example.com/save-now/spring-sale

Setting URL Redirect Reindexing Options

To set the options that determine when URL redirect reindexing occurs, see How Reindexing Works in EE 1.13

URL Redirect Option: Setting Category and Product URL Suffixes

By default, Magento enables web store customers to access products and categories with a URL that ends with .html. You can optionally change both the product and category URL suffix to any alphanumeric string.

The examples throughout this section use the default suffix, .html.

To optionally change the product and category URLs:

  1. Log in to the Admin Panel as an administrator.
  2. Click System > Configuration.
  3. In the CATALOG group, click Catalog.
  4. In the right pane, expand Search Engine Optimizations.
  5. Enter valid values in the Product URL Suffix and Category URL Suffix fields.
    Valid values are alphanumeric characters (a-z, A-Z, 0-9) or the underscore character (_).
  6. Click Save Config at the top of the page.

Getting Started with URL Redirects

To get started:

  1. Log in to the Admin Panel as an administrator.
  2. Click Catalog > URL Redirects.
    The following figure shows a sample URL Redirect Management page for EE 1.13.0.0 or 1.13.0.1.

    The following figure shows a sample URL Redirect Management page for EE 1.13.0.2.

    Note: EE 1.13.0.2 enables you to create URL redirects per store view.
    The preceding figure shows the following sample URL redirects:
    • best-keyboard.html, a permanent (HTTP 301) product redirect.
    • on-sale-now.html, a permanent (HTTP 301) category redirect.
      In the EE 1.13.0.2 example, because the redirect is on the French store, the category name is in French.
    • wonder-phone.html, a temporary (HTTP 302) product redirect. Magento recommends you always use a permanent (HTTP 301) redirect.

    The preceding all redirect from system URLs (note the values in the Target Path column). You can redirect to any valid URL, such as a URL you create in the CMS.

    Note: The sample values shown in the figure all have an .html extension, which is optional. You can omit the .html extension or enter a different extension; in either case, Magento redirects the URL properly. However, web store customers must enter the same extension you set up. To avoid confusion, you should either use the category or product URL suffix you set up previously or use no extension.

    The following table discusses the meanings of the columns on this page.

    Column Description
    ID A unique identifier Magento assigns to the URL redirect.
    Store (EE 1.13.0.2 and later only) The store view for which you're creating the URL redirect.
    Request Path

    The unique part of the URI for that redirect. The request path can be any URL-encoded string. For example, great-valentines-gift.html.

    Note: Every request path must be globally unique among all products and categories. In other words, no two products can have the same request path, and no two categories can have the same request path.

    Target Path The URI that identifies the category, CMS page, and so on. The target path you enter must be valid; otherwise, the redirect fails with a 404 (Not Found).
    Options Displays one of the following:
    • R if you chose a temporary (HTTP 302) redirect.
    • RP if you chose a permanent (HTTP 301) redirect.
    • Nothing if you chose to not redirect.
    Description Optional description you added when you created the URL redirect.
    Action Click Edit in this column to edit or delete the redirect. (You can also click the row itself.)

Continue with one of the following sections:

Creating New URL Redirects

This section discusses how to create new custom, product, or category URL redirects.

  1. Complete the tasks discussed in:
  2. Click Add URL Redirect.
  3. From the Type list, click one of the following:
    Option Description
    Custom Redirect to any valid path. To use this option, you must know the exact request and target path.
    Category Redirect to a category page. Magento system category paths use the format catalog/category/view/id/category-string
    You can optionally redirect to a custom CMS path if you have already set one up.
    Product Redirect to a product page. Magento system product paths use the format catalog/product/view/id/string or catalog/product/view/id/product-string/category/category-string
    You can optionally redirect to a custom CMS path if you have already set one up.
  4. Do any of the following:
    • Custom redirect: Enter the required information. For more information, see step 6.
    • Category redirect: Click the name of the category.
    • Product redirect: Click the name of the product.
  5. Product redirect only. Optionally click the name of a category, or click Skip choosing category to let the product remain associated with its original category.
    You need to click a category name only if you want the URL redirect to go to a different category.
  6. Enter the following information:
    Option Description
    Store (EE 1.13.0.2 and later only) From the list, choose a store view for the URL redirect.
    Request Path

    Enter a unique path to identify the product or category. The path can be in any format that uses URL percent encoding. Examples:

    best-valentines-gift.html

    greatest-keyboard.html

    products-on-sale.html

    best/products/on/sale/now.html

    Note: Every request path must be globally unique among all products and categories. In other words, no two products can have the same request path. and no two categories can have the same request path.

    Target Path Enter a request path in one of the following formats:
    • Custom redirect: Any valid path.
    • Category redirect:
      • System path: Unless you set up a custom path using the CMS, you should leave this field unchanged. By default, system category paths have a format like: catalog/category/view/id/category-string
      • Custom path: Any valid path
    • Product redirect:
      • System path: Unless you set up a custom path using the CMS, you should leave this field unchanged. By default, system product paths have a format like:catalog/product/view/id/product-string or catalog/product/view/id/product-string/category/category-string
      • Custom path: Any valid path
    Redirect type From the list, click:
    • No
    • Temporary (302)
    • Permanent (301). Magento recommends choosing this option because search engines retain the page ranking.
    Description Enter an optional description.

    The following figure shows a sample category redirect that permanently adds the URL http://www.example.com/on-sale-now.html for a category in the English store with a category ID of 25. (The option to add URL redirects to store views is available in EE 1.13.0.2 and later only.)
  7. At the top right corner of the page, click Save.

For examples of how to verify URL redirects, see the next section.

Verifying URL Redirects

This section discusses how to verify that a sample product URL redirect displays correctly on your Magento web store.

  1. In the Admin Panel, click Catalog > URL Redirects.
    The URL Redirect Management page displays.
  2. Click a row corresponding to a product redirect.
    The following figure shows the example used in this section.
  3. Open a new browser window or tab page.
  4. In the browser's location or address field, construct the URL to the product as follows:
    • Start with the scheme (http:// or https://, then your web store's domain name, followed by /.
    • Append to it the value of the Target Path field from the Admin Panel, followed by /.
    • Append to it the value of the Request Path field.
    For a Magento web store whose domain is http://www.example.com, the URL should look like the following:
    http://www.example.com/sale-keyboard.html
  5. Press Enter.
    The following figure shows an example of a successful redirect.

    Note: If a 404 (Not Found) displays, verify the target path precedes the request path and that each path is separated by one / character.
  6. Optionally verify category and custom redirects the same way.

Editing or Deleting URL Redirects

To edit or delete a URL redirect:

  1. Log in to the Admin Panel as an administrator.
  2. Click Catalog > URL Redirects.
    The URL Redirect Management page displays.
  3. Click the row of the URL redirect to edit or delete.
    To edit a URL redirect, you can also click Edit in the Action column.
  4. To delete the URL redirect, click Delete. You are required to confirm the action.
    To edit a redirect, edit or change the information displayed on your screen. For additional help, see Creating New URL Redirects.

Using the Flat Catalog and Product Reindexing Improvements

Magento uses the Entity-Attribute-Value (EAV) model for storing customer, product, and category data in its database. Although the EAV model enables you to have a completely extensible attributes for those objects, object attributes are stored in multiple tables rather than one very large table.

Because attributes are stored in many tables—and that includes copies of some of the same attributes—SQL queries are long and complex. The flat catalog feature creates new tables on the fly, where each row contains all necessary data about a product or category.

In earlier Magento releases, you had to rebuild the flat catalog every time you made changes to product attributes or product-category associations. In this release, however, the flat catalog is updated for you—either every minute, or according to your Magento cron job.

See the following sections for more information:

Flat Catalog Prerequisite: Enabling Frontend Options

Flat catalog options not only enable the flat catalog and flat product indexers but also enable indexing for catalog and shopping cart price rules. In earlier Magento versions, shopping cart and catalog price rules failed to reindex in configurations with a large number of SKUs (500,000 or so). In this release, catalog and shopping cart price rules index quickly—provided you enable the Flat Catalog Product option as discussed in this section.

To take advantage of these improvements in this release, you must enable flat products and categories for your web store as follows:

  1. Log in to the Admin Panel as an administrator.
  2. Click System > Configuration.
  3. In the CATALOG group, click Catalog.
  4. In the right pane, click Frontend.
  5. From the Use Flat Catalog Category list, click Yes.
  6. From the Use Flat Catalog Product list, click Yes.
    The following figure shows an example.
  7. In the upper right corner, click Save Config.

Setting Flat Catalog Reindexing Options

To set the options that determine when flat catalog reindexing occurs, see How Reindexing Works in EE 1.13.

Verifying the Results of the Flat Catalog Configuration

With the changes in this release, reindexing is extremely fast whether you make changes to individual products or to multiple products and categories at the same time. This section discusses examples of both.

Note: Magento recommends performing the tasks discussed in this section in a development environment first.

See one of the following sections:

Verifying Flat Catalog Changes for a Single Product

To verify flat catalog changes for one product:

  1. Log in to the Admin Panel as an administrator.
  2. In a different browser tab page or window, open your web store's front page.
  3. In the Admin Panel, click Catalog > Manage Products.
  4. Choose a product to modify.
    This example uses the Nokia 2610 Phone.
  5. Click the name of the product to edit it.
  6. Click the General tab.
  7. Append _DEMO to the value in the Name field.
    The following figure shows an example.
  8. Click Save.
  9. View your web store.
  10. Search for the product you edited or browse to the category that contains it.
  11. If necessary, refresh the page to see the result of the change you made.
    The change occurs either within the minute or according to your cron job schedule.
    The following figure shows an example.

Verifying Flat Catalog Changes for Multiple Products

To verify flat catalog changes for multiple products:

  1. Log in to the Admin Panel as an administrator.
  2. In a different browser tab page or window, open your web store's front page.
  3. In the Admin Panel, click Catalog > Categories > Manage Categories.
  4. From the Choose Store View list, click the name of a store to view categories for that store. (You can also click All Store Views).
  5. In the left pane, click the name of an existing category.
  6. Click Add Subcategory.
  7. In the Name field, enter Demo category.
  8. From the Is active list, click Yes.
  9. Click Save Category.
  10. Click the Category Products tab.
  11. Click Reset Filter to display your products.
  12. Select the check box of several products to add them to the new category.
    The following figure shows an example.
  13. Click Save Category.
  14. View your web store.
  15. Search for or browse to the category you created.
  16. If necessary, refresh the page to see the changes you made.
    The change occurs either within the minute or according to your cron job schedule.
    The following figure shows an example of adding several products to a subcategory of Electronics.

Setting the Index Clean Schedule

The clean schedule specifies the frequency at which temporary database records created by the partial reindexing process are permanently removed.

This process can take anywhere from a few seconds to a few minutes, depending on the number of records. Magento recommends cleaning the index once per day during off-peak hours.

Note: Index cleaning has a negligible effect on server performance and no effect on customers using your web store. Magento recommends cleaning the index at a time when you normally do routine maintenance, which should be during off-peak hours.

To set the index clean schedule:

  1. Log in to the Admin Panel as an administrator.
  2. Click System > Configuration.
  3. In the left navigation bar, in the ADVANCED group, click Index Management.
  4. Expand Index Clean Schedule.
    The following figure shows an example.
  5. Enter the following information.
    Option Description
    Enable Scheduled Cleanup From the list, click Yes.
    Start Time From the hours:minutes:seconds lists, select the time of day you want to clean the index.
    The time of day is based on the Magento server's clock in 24-hour format.
    Frequency

    From the list, click the frequency with which to clean the index:

    • Daily Recommended. Clean the index once per day.
    • Weekly: Clean the index once per week on the first day of the week.
    • Monthly: Clean the index once per month on the first day of the month.
  6. Click Save Config.

List of Actions that Cause a Full Reindex

The following table discusses the complete list of all actions that cause full reindexing for all indexers.

Type of indexer Actions that trigger a full reindex
Catalog Category Flat indexer
  • Create a new web store
  • Create a new web store view
  • Create, or delete an attribute that is any of the following:
    • Searchable or visible in advanced search
    • Filterable
    • Filterable in search
    • Used for sorting
  • Change an existing attribute to be any of the preceding.
  • Enable flat category frontend options as discussed in Flat Catalog Prerequisite: Enabling Frontend Options.
Catalog Product Flat indexer
  • Create a new web store
  • Create a new web store view
  • Create, or delete an attribute that is any of the following:
    • Searchable or visible in advanced search
    • Filterable
    • Filterable in search
    • Used for sorting
  • Change an existing attribute to be any of the preceding.
  • Enable flat product frontend options as discussed in Flat Catalog Prerequisite: Enabling Frontend Options.
Stock status indexer

When any of the following options is changed in the Admin Panel:

  • System > Configuration. In the CATALOG group, click Inventory. In the right pane, expand Stock Options. Option name: Display Out of Stock Products
  • System > Configuration. In the CATALOG group, click Inventory. In the right pane, expand Product Stock Options. Option name: Manage Stock
Price indexer
  • Adding a new customer group.
  • When any of the following options is changed in the Admin Panel:
    • System > Configuration. In the CATALOG group, click Inventory. In the right pane, expand Stock Options. Option name: Display Out of Stock Products
    • System > Configuration. In the CATALOG group, click Inventory. In the right pane, expand Product Stock Options. Option name: Manage Stock
    • System > Configuration. In the CATALOG group, click Catalog. In the right pane, expand Price. Option name: Catalog Price Scope
Category or product indexer
  • Create or delete a store view
  • Delete a store
  • Delete a website

Discussion:

Explore the Knowledge Base