My Site Audit Will Not Run

Check the project has a website set, that you have credits since each page costs 1 credit, and whether a recent audit triggered the cooldown message. Audit failed means the scan could not finish and previous results are unchanged.

Last updated 1 day ago

The run button does nothing, the audit fails, or you cannot start one.

Cause 1: No Website on the Project

You will see "Connect your website to run site audits" with a Connect website button.

The audit crawls your project's website, so it needs one. Set it in Brand Profile → Business under Website.

Cause 2: You are Being Asked to Wait

Two messages mean wait rather than fix:

"An audit ran recently. Try again in a few minutes." A cooldown, to stop repeat crawls of the same site.

"Too many audits are already running for this workspace. Wait for one to finish." You have other audits in progress, which is easy to hit if you run several projects at once.

Both clear on their own.

Cause 3: No Credits

Each page crawled costs 1 credit. A 50 page audit needs 50 credits.

Check Settings → Usage. If the balance is empty, buy a credit pack or wait for renewal.

There is also a monthly crawl budget, as of 2026-08-30: Trial 100 pages, Starter 500, Creator 2,000, Pro 5,000, Agency 10,000, and Scale 20,000. If you have audited heavily this month, that is worth checking.

Cause 4: It Already Ran and Failed

"Audit failed" means "The latest scan could not finish. Your previous results were not changed."

Use Retry audit. If it fails again:

Check your site is reachable. Open it in a browser from outside your network. A site behind a maintenance page, a password, or a staging login cannot be crawled.

Check for crawler blocking. A firewall, Cloudflare rule, or bot-protection service can block the crawl. This is the most common repeat cause on sites with aggressive security settings.

Check robots.txt. A rule disallowing everything blocks the crawl.

Try fewer pages. Use Manage pages to reduce the set. A single problematic page can be the cause, and a smaller crawl narrows it down.

Cause 5: The Page Limit

One audit covers up to 100 pages, and 50 per run on a trial.

If your site is larger, the audit does not fail, it covers a subset. Use Manage pages to choose which pages matter rather than accepting whatever the crawl found first.

Cause 6: The Buttons are Disabled

If run actions are disabled with "This action is not available yet. No changes were made." or "Enable the site audit engine to run a live scan.", and the page shows a Sample data banner, you are on an environment where the audit engine is not enabled.

The engine is enabled in production. If you see this on your live workspace, contact support.

Quick Checks in Order

  1. Check the project has a website in Brand Profile → Business.
  2. Read the message. Cooldown and concurrency messages mean wait.
  3. Check Settings → Usage for credits.
  4. Open your site from outside your network to confirm it is reachable.
  5. Reduce the page set with Manage pages and retry.
  6. Check robots.txt and any bot protection.

If the Audit Runs but Finds Almost Nothing

That is a different problem, and usually one of these:

Only a few pages were crawled. Check Pages audited. If the crawl found little, your sitemap may be missing or your pages may not be linked. Set your sitemap URL in Brand Profile → Business.

Search Console is not connected. You will see "Search Console not connected." GSC-backed signals such as indexing coverage and mobile usability are limited without it. Select Connect GSC.

Your site is genuinely in good shape. Possible, though a real site usually has some findings.

Notes

Audits never change your website. They read and report.

A failed audit leaves your previous results intact, so you do not lose history.

Paid plans get a monthly scheduled audit as well as manual runs.

Running a site audit covers the process and limits. Working through your site audit issues covers the findings.