Use the daily audit to regularly review new and recurring issues. After publishing an important fix or launching a new section, choose a manual check of the relevant pages. This way, the results relate to the change you are reviewing.
Suppose a developer fixed the product template in 14:00, but the morning report finished earlier. It still describes the previous version. Check the product pages manually and get a new audit after publication.
What an automated check provides
A connected site is scheduled for a daily audit that crawls up to 100 pages. It provides new technical results without requiring you to start each check yourself. When reviewing the results, check the actual completion date and the URLs covered.
A scheduled frequency does not prove that the results will always be ready at the same time. A check may depend on the queue, site availability, and completion of individual stages. If the data is old or partial, first review the status, then make a decision based on the available results.
Learn more about one-time research and regular monitoring in the article on audits and monitoring. For routine reviews, check the date of the latest results and any changed findings.
Choose the manual scope for the task
Full manual audits have packages covering up to 25, 100, 500, and 1000 pages. The limit also applies to an included run under a paid subscription. If the site has more URLs, plan the audit scope; do not describe a single report as covering any site size.
The number of addresses discovered may differ from the number actually checked. Package limits, page availability, link discovery, and check execution all affect this. After completion, review the actual coverage, not just the name of the selected package.
Check the technical audit page and the run settings to find an appropriate option. A small package may be enough for a small site; for a catalog, it is important to include representative page types. Choosing the largest scope does not by itself guarantee that all required test URLs will be successfully checked.
Compare actions in typical situations
| Situation | What to do | Result needed |
|---|---|---|
| Regular day | Review the new automated audit | Date, new findings, checked addresses |
| A link was fixed | Follow the link again and check the URL | The relevant page opens after publication |
| A catalog template was released | Check different product pages and run an appropriate package | Representative pages were checked |
| A form was changed | Submit an agreed test | The recipient found the submission |
For a new section, first list the important URLs. Choosing the largest package does not guarantee that every required page will be successfully checked. After completion, find those pages in the results.
If a previous audit is still running and fits the task, wait for it. Running the same check again on an unchanged site usually does not help you review a fix sooner.
Account for the queue for manual runs
Manual full audits are limited to no more than three active tasks at a time. Having no monthly quota for included runs does not mean there is no queue or limit on simultaneous execution.
Before starting a new check, review the status of previous ones. Do not create unnecessary tasks if a suitable run is already in progress. Wait for its results or determine what information is actually missing. This saves review time and reduces duplicate reports.
With an active paid subscription, included manual local tools, express audits, and full audits have no monthly run limit. The scope limits for each package still apply. Paid plans include MCP and REST API for technical audits only. Paid AI tools are billed separately; learn more in the article about subscription tools.
Check whether the audit answered your question
Find the original addresses and required checks in the new report. If a page was not checked, run an appropriate check or perform the action manually. “No error in the list” for an unchecked URL leaves the question unanswered.
In the monitoring dashboard, compare the completion date with the publication date. For a link fix, save the destination URL; for a page title, save the new value; for a form, keep confirmation from the recipient. See the separate guide for how to confirm a finding.
Attach these results to the task and schedule follow-up for anything that could not be checked. Choose the next manual run only after identifying the missing addresses or data.