Reindex Pages

Reindex Pages refreshes the page metadata cache and rebuilds the search structure from the persisted search document cache. It is the fast, routine maintenance action.

Important: Reindex rebuilds from the cached documents, not from a clean disk scan. A page that was deleted but whose entry lingers in the cache (a "ghost" still showing in search/listings) is not removed by Reindex. To purge those, use Rebuild Pages, which clears the cache and re-scans every page from disk.

When to Reindex

Reindexing is rarely needed under normal operation. The system keeps the index updated automatically as pages are created, edited, or deleted. Reindex when:

• Pages appear missing from search results after a bulk file operation
• The server was stopped while pages were being written
• After restoring a backup or importing pages

For pages that were removed or renamed directly on disk (or deleted pages still showing in search), use Rebuild Pages instead — Reindex will not drop those stale entries.

How to Reindex

1. Go to Admin → Reindex Pages
2. Confirm the action when prompted
3. The server rebuilds both the page index and the search index
4. A confirmation message shows the page count and search document count when complete

On a large instance (10,000+ pages), reindexing may take a minute and will temporarily cause higher memory usage while the search index is built.

What Is Rebuilt

• Page index (page-index.json) — metadata for all pages (title, slug, author, dates, location)
• Search index — the full-text search structure, rebuilt from the persisted document cache (not a clean disk re-scan; see the note above and Rebuild Pages)

User sessions, attachments, and media are not affected.