Audits and results

How do rescans and fix verification work?

A rescan is a fully-fledged audit stored as a new history entry: comparison with the previous result, good practices (after deployments, periodically) and how limits apply.

2 min read

A rescan is a repeat, full examination of the same property - the heart of the "audit → fix → verify" cycle, the reason audits in GA4audit are unlimited.

What a rescan actually does

Technically, a rescan is a fully-fledged audit: it runs all checkpoints from scratch (configuration via API + the live site scan) and stores the result as a new entry in the project history. Nothing is overwritten - previous reports remain untouched.

What sets it apart from the first audit is context: since a previous result exists, you get a comparison:

•the Quality score change versus the previous audit - in the History view every scan carries a delta (e.g. +7),
•a fresh checkpoint balance: what moved from error to pass, what remained, what got worse - new problems land straight at the top of the Action plan.

How to run one

•from the report - the Re-scan button,
•from the home screen - the rescan icon next to the project.

If the GA4 connection session has expired (the token lives ~1 hour), you'll first be asked to reconnect - that's normal: "Your GA4 connection session has expired".

When to rescan - good practices

•After every batch of implemented fixes - short verification loops instead of one big one.
•After every major website deployment - a redesign, a new checkout, a consent banner change, a CMS migration: the classic moments when measurement silently breaks.
•Periodically, even without changes - e.g. monthly. Some problems arrive "from outside" (GA4 changes, expiring integrations) and only a regular scan catches them.
•1-2 weeks after fixing "data" problems - 30-day checkpoints need the analysis window to fill with post-fix data (why - see the article on fixes).

Rescans and limits

On paid plans, a rescan of an existing project is never restricted by the project limit - even when your plan's limit is fully used; only the soft fair-use rule against automated abuse applies (Fair Usage Policy). The exception is the Free plan, which includes one audit in total - rescans unlock from the Pro plan onward (details - project and audit).

Related articles:

•I fixed an error - why do I still see it in the report?
•What's the relationship between a project and an audit?

More in Audits and results

Didn't find your answer?

Write to us - we respond fast, implementation questions included.

Write to us