Get started today!◦ Full contract buyout ◦ Up to $1,000 credit ◦ Free migrations

Chat with us

Home » Magento Guide » Magento Admin » How to reindex in Magento 1: admin and command line steps

How to reindex in Magento 1: admin and command line steps

Key takeaways

Magento 1 reindexing updates indexes so product, price, category, and catalog changes display correctly.
The admin panel is the easiest method for smaller updates.
Command line reindexing works better for large catalogs or timeout issues.
Clear cache and check index status after reindexing to confirm changes are live.

How to issue a reindex in Magento 1 from the Admin Panel and from the command line. Method 1 is preferred for most clients; you should use Method 2 only if Method 1 fails, as it requires SSH access and some familiarity with the command line interface (CLI).

If you prefer, you may use your SiteWorx account to automate reindexing as a cron job. For assistance, refer to How to set up cron jobs and use the example provided.

Host Magento at full throttle.

Get secure, reliable Magento hosting so you can scale faster.

Magento hosting

What does reindexing mean in Magento 1?

Magento 1 uses indexes to organize store data so product pages, category pages, prices, search results, and URLs can load correctly on the storefront.

When you update store data, Magento may need to rebuild those indexes. Otherwise, customers may see old prices, outdated category assignments, missing products, or changes that do not appear on the frontend.

Common updates that may require reindexing include:

Product changes
Price updates
Category changes
Catalog imports
Store migrations
URL rewrite changes
Customer group pricing updates

⚠️ Magento 1 has reached end of life, so this guide is for stores still maintaining legacy Magento 1 environments. Reindexing can help keep a Magento 1 store running, but it doesn’t replace a long-term security and migration plan.

Quick answer: How to reindex Magento 1

To reindex Magento 1 from the admin panel, go to System > Index Management, select the indexers you want to update, choose Reindex Data, and click Submit.

To reindex Magento 1 from the command line, log in through SSH, go to your Magento root directory, and run:

Command line reindexing usually works better for large catalogs because it avoids browser timeouts and can show more useful error messages.

Before you reindex Magento 1

Before you start, confirm that you have the access and timing you need.

Confirm you have Magento admin access or SSH access
Back up the store before large updates
Run reindexing during lower-traffic periods when possible
Decide whether you need to reindex one index or all indexes
Plan to clear Magento cache after reindexing
Confirm cron is running if your store depends on scheduled tasks

Admin panel vs. command line reindexing

Method	Best for	Main benefit	Main limitation
Admin panel	Small updates and non-technical users	Easier to use	Can timeout on large catalogs
Command line	Large catalogs and troubleshooting	Faster, more reliable, and better error output	Requires SSH access

Method 1: using the admin panel

Use the Magento Admin Panel for smaller updates. This method is easier for most users, but it may not finish on larger catalogs.

Click System > Index Management.

On the left, select any or all categories to reindex. If you want to reindex all categories, click Select All.

From the Actions drop-down list, select Reindex Data and then click Submit.

Depending on how many categories, and the amount of information that needs to be reindexed, this could take minutes or hours.

If the reindex doesn’t finish, proceed with Method 2 below.

Method 2: using the command line

Use the command line when the admin panel doesn’t finish, the store has a large catalog, or you need more detailed error output.

If you don’t yet have SSH access, refer to How to obtain SSH access from Liquid Web for guidance.

Command line reindexing can show more descriptive errors if something goes wrong.

Navigate to your Magento installation:

From the Magento root directory, you can either run commands that include shell/indexer.php or move into the shell directory first.

After accessing the Magento directory, navigate to the shell directory:

To view the current status of the Magento indexer, enter:

To issue a reindex of all categories, enter:

To run the same command from the Magento root directory, use:

To see available indexer codes, run:

To reindex a specific indexer, run:

Replace [indexer_code] with the indexer you want to update.

Magento 1 reindex command examples

Task	Command
Reindex all indexes	php shell/indexer.php –reindexall
Check index status	php shell/indexer.php –status
View available indexer codes	php shell/indexer.php –info
Reindex one indexer	php shell/indexer.php –reindex [indexer_code]
Reindex product prices	php shell/indexer.php –reindex catalog_product_price
Reindex catalog URLs	php shell/indexer.php –reindex catalog_url
Reindex product flat data	php shell/indexer.php –reindex catalog_product_flat

Clear Magento cache after reindexing

After reindexing, cached pages may still show old product, price, category, or URL data. Clear Magento cache if changes do not appear right away.

To clear cache in Magento 1:

Go to System > Cache Management
Select the cache types you need to refresh
Choose Refresh from the Actions dropdown
Click Submit
Check the storefront to confirm the update appears

Some stores also use external caching, a CDN, or full-page cache tools. Those may need to be cleared separately.

How to check if Magento 1 reindexing worked

After reindexing, review product and category pages on the frontend to confirm changes appear. Run php shell/indexer.php –status to check index status and review command output for errors.

Troubleshooting Magento 1 reindexing issues

Index is stuck in “Processing”

An index may get stuck after an interrupted reindexing task or locked process. You may need to review files inside the var/locks/ folder, but confirm no active indexing process is running before removing lock files.

Command line memory limit errors

If reindexing fails because of a memory limit, you can try increasing the PHP memory limit for the command:

If memory errors continue, the store may need hosting, catalog, or database optimization.

Admin panel times out

Use command line reindexing if the admin panel times out. Large catalogs often need CLI because the browser process may stop before Magento finishes rebuilding indexes.

Wrong directory or missing indexer.php

Run the command from the Magento root directory or move into the shell directory first. Confirm that shell/indexer.php exists before running indexer commands.

Permissions issues

File permissions or SSH user restrictions can prevent commands from running correctly. If the command fails, check permissions or contact support for help with access.

Changes still don’t show on the storefront

Clear Magento cache, check any external cache or CDN, confirm the correct indexer ran, and review index status again.

Automating Magento 1 reindexing with cron

Cron can help stores that run frequent imports, product updates, or catalog changes. It can also reduce manual work if your store needs indexing on a schedule.

If cron doesn’t run correctly, check the command path, permissions, and server access. Hosting support can help when cron setup or SSH access gets in the way.

Magento 1 end-of-life and migration considerations

Magento 1 no longer receives official platform support, which creates security, compatibility, and maintenance risks for stores that still run it.

Reindexing can help maintain product, price, and catalog accuracy, but it doesn’t fix the larger risks of running an outdated platform. Stores that rely on Magento 1 should plan a path to Magento 2, Adobe Commerce, or another ecommerce platform.

If your store is hard to maintain, slow to reindex, or dependent on old extensions, migration planning may be overdue.

Hosting and support considerations for Magento 1 reindexing

Reindexing can put real demand on the server, especially for large catalogs. It can involve database work, file operations, memory usage, and long-running processes.

When reindexing Magento 1, your hosting environment affects SSH access, memory limits, server resources, cron reliability, backups, security controls, and troubleshooting support.

Magento 1 reindexing FAQs

You can reindex Magento 1 from System > Index Management in the admin panel, or through SSH using:

Use the admin panel under System > Index Management, or run:

Run:

Replace [indexer_code] with the correct code from:

Magento 1 reindexing may get stuck because of a browser timeout, locked process, memory limit, permissions issue, server resource limit, or interrupted indexing task.

No. Magento 1 has reached end of life, so stores still using it should plan carefully around security, maintenance, hosting, and migration.

Magento 1 reindexing next steps

Magento 1 reindexing helps keep product, category, price, and catalog data accurate on the storefront. Use the admin panel for small updates, and use command line reindexing when you need a faster, more reliable option for larger catalogs.

Start by checking your index status, then choose the reindexing method that fits your access level and store size. After the process runs, clear cache and review the storefront to confirm the update worked.

Liquid Web’s Magento hosting gives ecommerce teams the performance, support, and control needed to manage complex stores. Explore Magento hosting to see how the right environment can support indexing, traffic, security, and long-term ecommerce growth.

For 24-hour assistance any day of the year, contact our support team by email or through your Client Portal.