## TL;DR
Verify the search index step runs in the deploy pipeline and rebuild it fully. Check the index artifact contains the new pages before publishing. For Algolia, confirm the crawler config includes the new routes.

## The exact error
```text
docusaurus search index missing new pages
```

## Steps
1. **Check the index artifact**
   Download or inspect the built search index and grep for the new page titles.
   Success check: You know whether the index or the deploy is stale.
2. **Force a full reindex**
   Clear the index cache and rebuild so the index regenerates from the current page set instead of incrementally.
   Success check: The fresh index contains every current page.
3. **Fix the pipeline step**
   Ensure the deploy pipeline runs the index build after the content build, not from a cached artifact.
   Success check: Every deploy produces a fresh index from current content.
4. **Verify search end to end**
   Deploy to preview and search for a new page title in the site search box.
   Success check: New pages are findable through site search.

## When to use
- Use when new docs pages are missing from site search after deploy.
- Use when an agent owns the docs deploy pipeline.

## When not to use
- Not for pages missing from the site entirely (build problem, not index).
- Not for Algolia quota or API key errors (different failure).

## Why it happens
Search indexes are build artifacts with their own caching. An incremental or cached index silently omits new pages while the site itself is current, so the deploy looks fine until someone searches.

## Edge cases
Preview deploys should run the same index pipeline as production; otherwise search is only verified where nobody looks. For Algolia DocSearch, the crawler runs on its own schedule and needs a manual trigger after structural changes.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_0UUF94whHVVEvt-SwxUmXg