Re-audit after a site change
Refresh the audit after a redesign, a batch of fixes, or a winning test, and check what moved.
After you ship something big, a fresh audit tells you whether the problems it targeted are gone and whether anything new showed up.
When it's worth re-auditing
- After a theme change or redesign.
- After shipping a batch of fixes from the Board.
- After a winning variation goes live for all traffic.
- After connecting a new integration, such as GA4 for the first time.
- On a regular cadence if the store changes often. Monthly is a reasonable default.
Depending on your plan, audits can count against a monthly limit, so save them for changes you expect to matter.
1. Refresh the audit
- Open Home and click Refresh audit in the top-right.
- Check Data sources for this audit and connect anything new.
- Click Start audit. The dialog shows how many audits your plan has left this month.

The audit runs in the background and Home updates when it's done. Make sure your change is live on the store before you start, or the audit will see the old version.
2. Compare the journey scores
Open Buyer journey and look at the stages your change was meant to improve. Click a stage to read its updated summary and recommendations.
3. Check the observations
Open Pages and pick the page type you changed. If an observation you expected to clear is still there, open it to see what Spar is still seeing on the page.
4. Triage what's new
A change can create new problems as well as fix old ones. New findings land on the New tab of Opportunities. Work through them the same way as your first audit: see Triage your first audit.
5. Record the result
If a shipped change moved the numbers, note it where your team will see it, for example in a Notebook next to the related test, or in the next report you send.
Last updated on