Skip to content
Browse documentation

Content freshness

Where it is: Settings → Knowledge & Sync → Content Freshness.

Live sync catches the edits WordPress announces. It cannot see everything: a price changed by an import script, a plugin writing custom fields, a sale that starts by itself at midnight, a row deleted straight from the database. The daily freshness check is the safety net under all of that.

What each setting does

SettingWhat it doesDefault
Daily freshness checkOnce a day, compares a fingerprint of every synced page, post and product against what was indexed, and re-indexes anything that changed or vanished.On
Scheduled website re-crawlRepeats your most recent website crawl unattended — same URL, same limits — daily or weekly. Run one crawl manually first, so there is something to repeat.Never
Last checkThe previous run in one line: how many items were checked, re-indexed, removed and retried.

What it costs

Comparing fingerprints is local database work, and free. Embeddings are only paid for items that actually changed, which on a stable site is none of them. A nightly sweep of a thousand pages typically costs nothing at all.

Items that keep failing

A page that fails to index — a timeout, a provider error — is retried on later runs with a growing gap between attempts. After three failures it is marked stale and raised in an admin notice, rather than rotting silently in the queue.

All of this runs on WordPress scheduled tasks. On a very low-traffic site those only fire when someone visits, and if DISABLE_WP_CRON is set on your server, a real cron job has to call wp-cron.php. System Health lists each task and when it next runs.

Still stuck? Ask the assistant in the corner of this page — it has read all of this — or send us a message.

Last updated September 18, 2026