Scan cadence and refresh windows

How often Burnish re-measures

Two different things refresh on two different clocks, so it helps to keep them apart.

  • Your catalog scan — how ready your products are — runs about every 24 hours on every tier, including before you pick a plan. Your whole catalog is read, not a sample.
  • AI answer sampling — actually asking the assistants about you — runs about every 24 hours on a paid plan, and about once a week without one.

Sampling is the part that costs real model time, which is why it is the part that slows down without a plan. Authority and Omnipresence run on a priority queue, so their refreshes are processed first. The interval itself is the same 24 hours.

When your changes show up

When you improve a product or publish a fix, Readiness updates on the next scan, within about a day on a paid plan. Visibility takes a little longer, because Burnish has to re-query the assistants and see your changes reflected in their answers over the following refreshes.

The measurement window

Visibility is measured over a rolling two-week window, so one odd answer from a single assistant will not swing your score. Recent samples count, and older ones roll off.

If you just made a change, give it a refresh cycle or two. Readiness moves first, and visibility follows as the assistants catch up.

Can’t find what you need?

Contact our team