Bit of a process question. I'm tempted to run /full-site-audit every few days because watching the health score is oddly satisfying, but that feels like a waste of credits and probably not how it's meant to be used. What's a sensible cadence for a site that isn't publishing daily?
The health score won't move meaningfully every few days unless you're actively changing things, so daily runs mostly just spend credits. A cadence that works for most sites:
Because every run is saved and dated, the value is in the comparison over time, not the raw number on any single day. Monthly plus event-driven gives you a clean trend line without burning credits watching a number that hasn't changed.
I run mine on the 1st of every month and after any big deploy. The dated compare view showing what changed between two runs is the actually useful part, not the live score.
