WP Search with Algolia indexes WordPress content into Algolia's cloud and stores sync metadata locally so it knows what has been pushed: object IDs, last-sync timestamps, queue state, and per-index assignments. The plugin's settings page shows aggregate index counts and connection status, but per-record sync state, queue progress, and failed pushes only fully surface inside Algolia's own dashboard at algolia.com - one cloud over from the WP Admin you already work in.

SleekView reads the local sync metadata the plugin already maintains and turns it into one grid: post ID, title, Algolia index name (products, posts, pages), last sync timestamp, object ID, sync state. The same dataset the plugin uses to know what it has pushed; presented as the dataset it is. A Returns Policy page that landed in the pages index at 14:01 yesterday and a Discontinued Product that has been Failed since March are both visible in the same grid, sorted by sync state, in the same admin.

The State column is the one that closes the cloud-to-WordPress gap. Algolia's dashboard knows what is in the index; only the WordPress side knows what was supposed to be in the index but failed to push. A Failed row with a March 30 last-sync against a product that should have been re-pushed in April is the exact kind of orphan that breaks the search experience without ever reaching the cloud-side dashboard. The grid makes those rows the first thing a re-push or hygiene sweep targets.

Algolia is one of the few WordPress search backends that lives entirely off-site. The benefit is huge: blazing-fast hosted search with native typo tolerance, faceting, and analytics. The cost is that the system of truth for what is searchable is on a different cloud than the system of truth for what is published.

WP Search with Algolia bridges them by maintaining sync metadata in WordPress that mirrors what should be in Algolia, and that bridge is exactly where things go wrong. A deploy that timed out mid-sync leaves orphan postmeta with no matching object in Algolia. A migration that brought in old posts without re-running the sync leaves Algolia missing rows.

A WooCommerce price update that did not trigger the sync hook leaves the Algolia index showing yesterday's price. None of those are visible from Algolia's dashboard alone because the dashboard only sees what made it across. SleekView is the WordPress-side mirror that completes the picture.

By surfacing per-record sync state in WP Admin, it lets the team that owns the publish path also own the index hygiene path, which is the only place the discrepancies actually get fixed.