There are two ways to run an audit: Ad-hoc and via the Scheduler.
Use this for one-off audits. For example, testing a setup configuration, or you just need a snapshot of the data quality right now.
Remember that if a spider contains more than 1000 URLs, not all will be tested – that would be wasteful. Instead a random sample is taken with the sample size determined/optimised by the system. Hence you will see a number of options to choose from if an audit has already completed.
Note, a new spider will always start if the previous is older than 30 days. This is important in order to keep the audit reports relevant, AND it allows you to you re-audit the same spider without using your URL allowance. For example, while you adjust the settings such as thresholds, whitelists, weights etc. and get the reports working correctly for you.
Use this when your setup is finalised and you wish to monitor data quality over time. The options you see here depend on the license you have purchased. Typically Monthly is sufficient as you will use the Current Status to check governance issues in near real-time. If you are undergoing major revisions to your website, use a higher audit frequency until the dust settles.
When an audit is running the notification bell turns red. Click on this to see what is happening.
When an audit is completed its status is removed from this section. In addition, if you have Edit or Admin access to this project, you will received an email notification when:
- The spider has completed (if one was required).
- The audit has completed and the report is ready for viewing.
Running Multiple Audits
A project audit can only run if there is no existing audit currently running for the same project. You can always cancel a running project in the Report Log of the same page. It can take a few seconds for all the job queues to be stopped and the status to be refreshed.