What is Refresh velocity?
Refresh velocity is the count of priority-page refreshes an editorial team ships per week, scored against the refresh cadence the engine freshness window requires across the four-tier calendar. The headline metric is whether refresh velocity is sufficient to defend Tier 1 (every 4–6 weeks) and Tier 2 (every 8–12 weeks) on the program's priority page count — most well-engineered mid-2026 programs ship 6–14 refreshes per week against a 40–120 page priority set. Velocity below the cadence threshold guarantees freshness drift on the underserved tier; velocity well above the threshold is usually a signal the editorial team is publishing or refreshing non-priority pages and should refocus. The right operational read on refresh velocity is the ratio: weekly refresh count vs the count required by the tier cadence on the priority set.
How it relates to AI UGC
Image refresh velocity runs separately from text refresh velocity — the multimodal substrate's 4–12 week image freshness window often requires 2–3× the per-page image refresh count of the text refresh count. ppl.studio production cadence supports the higher image refresh velocity without proportionally higher production cost vs traditional shoots.
Key statistics
- Mid-2026 well-engineered refresh programs ship 6–14 refreshes per week against a 40–120 page priority set — the count required to defend Tier 1 + Tier 2 cadence on the priority page count (refresh-velocity cohort, 2026).
- Refresh velocity below the tier-required threshold guarantees freshness drift on the underserved tier; programs running 50% under tier velocity lose 18–32% of priority-page citation share within two quarters (velocity-shortfall audits, 2026).
- Image refresh velocity needs to run 2–3× higher than text refresh velocity on multimodal-surface pages — the image freshness window is materially shorter and the carousel slot decay leads text citation decay by 5–7 weeks (image-velocity cohort, 2026).