Refreshing knowledge

How refreshes are scheduled, what a refresh reads, and when to trigger one by hand.

Refreshing rereads a source and updates the facts that came from it.

Scheduled refreshes#

Each entity carries its own next refresh time. Refreshes are budgeted: a refresh reads far fewer pages than the initial ingest, because it is checking what changed rather than learning the product from scratch.

Refreshing by hand#

Worth doing after:

• a pricing change,
• a launch or a rename,
• rewriting your own positioning pages,
• a competitor doing any of the above.

What a refresh changes#

Facts confirmed against the source become verified again. Facts that no longer appear become superseded rather than vanishing, so an article that cited one can still be traced. Facts you confirmed yourself are not overwritten by a crawl.

What it does not do#

A Knowledge refresh does not rewrite published posts. It re-evaluates the evidence-bound Content freshness review. When a fact really changed, you can generate a separate article refresh draft; the current article stays live until you review and explicitly publish that candidate. The decision stays yours. See freshness and conflicts.