Search is instant because it never queries your content tables directly: everything searchable is extracted into a dedicated index. The index builds on activation, updates live when content is published, rebuilds itself when the search scope changes, and can run on one of two storage engines: MySQL (the default) or SQLite. The engine switch lives under Elevated › Site Search › Settings › Advanced Options › Indexer.

Table of Contents

• How the Index Works
• MySQL vs SQLite
• Switching Engines
• Troubleshooting

How the Index Works

• Built automatically. Activation schedules the first build; you never have to create it by hand.
• Updated live. Publishing or updating content of an indexed post type updates the index immediately.
• Rebuilt on scope changes. Changing post types, custom fields, taxonomies, or comments under Content to Index triggers a rebuild on its own.
• Search keeps working during rebuilds. A rebuild prepares the new index and swaps it in when ready.

MySQL vs SQLite

Both engines power identical features; they differ in where the index lives.

• MySQL (default): the index lives in dedicated tables inside your existing WordPress database. The Indexer status line reads like “MySQL tables ready” with the document count.
• SQLite: the index lives in its own file under wp-content/uploads/elevated_site_search, keeping index churn out of your main database. Requires the PHP SQLite extension, which most hosts ship.

Switching Engines

Click the engine you want under Search Engine, then click Force Index Rebuild: the index builds fresh on the chosen engine and search switches over when it completes. The status line always names the active engine and its document count.

Troubleshooting

The status line says there is no index for the active engine. The engine changed without a rebuild. Click Force Index Rebuild to build it.

Document count looks lower than expected. The count covers published items of the indexed post types only. Check the scope under Content to Index.