Type at least two letters.

    ↑ ↓ to moveEnter to open

    Run and schedule audits

    Choose what an audit checks, run it now, schedule it for later, or repeat it every week or month.

    Updated

    Every audit, however it is started, goes into a queue and runs in the background. Starting one only takes a moment; the result follows, usually within a minute.

    Run an audit now

    • Overview → Run audit: for a new or an existing address.
    • Sites → Run audit…: for a site on your list. You choose what it checks before it starts.
    • Audit report → Run again: repeats the audit you are looking at.

    You are taken to the report, which fills in when the audit has finished. You can leave the page; the run is listed under Audits.

    Choose what an audit checks

    Sites → Run audit… opens a window with one card per area, such as security, email or search and sharing.

    • Tick an area to run all of its checks, or untick it to leave the area out.
    • Open Choose checks on a card to switch single checks on or off.
    • Everything and Nothing set all checks at once.
    • The line under the cards shows how many checks are selected and how many credits the audit uses.

    To keep a selection, open Save this selection for next time, give it a name and press Save as scope. Saved scopes are listed at the top of the window.

    Checks marked verified owner ask the site for more than a visitor would. They are switched off until you have verified that the site is yours: press Verify ownership… in the window, or Verify… on the site’s row. Every other check runs on any public website. A verified-owner check runs as part of a deep audit, which you buy once per site under Plan & billing (Plans and billing).

    The report covers what you selected. Areas you left out are not judged.

    Schedule one audit for later

    In the same window, pick a date and a time in your local time next to or start at, and press Schedule. The audit starts within five minutes of that time. You can schedule up to 90 days ahead.

    The run appears under Audits at once, with the status queued, and stays there until its time.

    Repeat audits

    On Sites, set Repeat on a site:

    Setting What happens
    Do not repeat No repeated audits. Manual and one-off scheduled audits still work.
    Every week An audit every week. The first one runs one week after you set it.
    Every month An audit every month. The first one runs one month after you set it.

    The next planned time is shown under the setting (Next: …). Repeated audits count towards the hourly limit like any other.

    One audit at a time per site

    A site can have one waiting or running audit at a time. If you start another while one is queued or running, you get a message that an audit is already waiting or running, and the existing run is kept. This also covers a scheduled run that has not started yet.

    When an audit fails

    What you see Why What to do
    The run is failed with url_policy_denied The address, or an address it redirected to, is not public.
    The run is failed with too_many_redirects The site redirected more than five times. Audit the final address instead.
    The run is failed with timed_out or internal_error The run did not finish after three attempts. Run it again later. If it repeats, report a problem.
    The run is partial Some checks could not be measured, for example the site was slow. The other results are valid. Run again later for the rest.
    You cannot start an audit You reached 20 audits in the last hour. Wait; the message says for how long.

    Over the API

    The same actions over the API: POST /audit-runs (now, or later with scheduledFor; a saved scope or your own ruleIds) and PATCH /sites/{siteId} with a schedule (repeat). See Asynchronous audits.