How app search indexes differ
Core Spotlight gives apps APIs to index items they manage and maintain those indexes as content changes. Apple says those indexes remain on the device and are private to its owner. App updates, a large content change, or an app rebuilding its searchable records may lead to background index work; that is separate from guessing that every CPU sample means a global Spotlight failure.
First check whether a recently used app has changed a large library or completed an update. Keep macOS and that app current, then allow a quiet idle period. The relevant question is whether activity declines when the source content stops changing, not whether a short spike exists.
Respond to persistent trouble
If CPU use returns repeatedly when the Mac is idle, search results from one app are wrong, or the associated app has errors, document the app, timing, and symptom. Contact that app’s developer when the pattern is app-specific. For system-wide search problems, Apple documents supported Spotlight settings and reindexing through System Settings.
Avoid deleting indexes or force-quitting daemons as routine maintenance. That can remove useful evidence and force more indexing. A support path is appropriate when updates and the documented settings do not resolve a reproducible failure.
Compare, do not over-attribute
WattGuard shows this process family’s current CPU, wakeups and disk activity. Where macOS provides the data, it also shows current power and accumulated energy for the selected period. You can observe changes manually over time and compare them with the separate sleep analysis. It cannot reveal an app’s private indexed content, repair a Core Spotlight index, or establish that corespotlightd alone caused battery drain. Treat its measurements as diagnostic context. For process monitoring in the Store edition, complete the setup wizard and install its companion files first; see the Energy Hogs feature page for setup.