# Index Table CLI {% embed url="" %} Index Table CLI commands in action {% endembed %} #### Command synopsis

wp asp index <new|continue|delete|item|info> [--batch=<batch>]
  [--skip-confirm] [--post_id=<post_id>] [--check-responsiveness]
  [--sleep=<milliseconds>] [--separate-process]

To get all the parameters and flags directly in the command line run:

wp help asp index

#### Command flags

Flag	Description
--skip-confirm	Skips the confirmation dialog when creating a new index or when deleting it.
--batch=<batch>	Number of posts (items) to index within an iteration step. Defaults to the number set on the plugin back-end.
--check-responsiveness	Checks the database response time before each batch. If the database response is slow, then incrementally waits until the response is better. Useful when the database is expect to be umder high load.
--sleep=<milliseconds>	When set, the indexer will wait for this many milliseconds after each batch. Useful when the database is expect to be under high load.
--post-id=<post_id>	Used with the `wp asp index item --post-id=123` command. Specifies which post ID should be reindexed.
--separate-process	When present, each batch is executed in a separate PHP process. Highly recommended for larger databases (10 000+ posts), where indexing takes a long time. Reduces memory usage greatly for large databases. On smaller databases has almost no effect.

#### Creating a new index To create a new index run: ``` wp asp index new ``` For larger databases it is recommended to use larger batches and process separation: ``` wp asp index new --batch=200 --separate-process ``` #### Continuing the existing index To continue the indexing: ``` wp asp index continue ``` For larger databases it is recommended to use larger batches and process separation: ``` wp asp index continue --batch=200 --separate-process ``` #### Re-indexing a specific post To reindex a specific post (or post type) by it's id: ``` wp asp index item --post-id=123 ``` This will update the post in the index. #### Emptying the index To remove (delete) all items from the index table: ``` wp asp index delete ``` #### Get information from the index To get the index table size and the indexed items count run: ``` wp asp index info ``` #### Running the index commands as cron jobs It is possible to execute all of the commands in a crontab as well. {% hint style="info" %} If you are not familar with cron jobs, please read [this article first](https://www.geeksforgeeks.org/linux-unix/crontab-in-linux-with-examples/). {% endhint %} To add a server side cron command, you need to edit the server crontab: ``` crontab -e ``` Crontab command synopsis: ``` * * * * * wp asp index --skip-confirm --path= ``` * ***--skip-confirm*** flag ensures that no confirmation message is shown, otherwise the command will stuck * **--path** is very important, it must point to the wordpress installation path, otherwise the command will be executed in the home directory For example, to create a new index every day at midnight assuming wordpress is installed in the "/var/www/public\_html" directory: ``` 0 0 * * * wp asp index new --skip-confirm --path=/var/www/public_html ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://knowledgebase.ajaxsearchpro.com/api/wp-cli-commands/index-table-cli.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.