Run a Site Audit
Select Run first audit or Run audit on the Site Audit page. Each page crawled costs 1 credit, one audit covers up to 100 pages, and Manage pages lets you choose which pages are included.
Last updated 1 day ago
Site Audit is at Sidebar → Measure → Site Audit. The page describes it as: "Scan your project for content, technical, and pagespeed issues, then track fixes over time."
What you Need
A website on the project. Without one you see "Connect your website to run site audits".
Google Search Console is optional but adds signals. Without it you see "Search Console not connected." with the note that GSC-backed signals will be limited, and a Connect GSC link.
Steps
- Open
Sidebar → Measure → Site Audit. - Select Run first audit, or Run audit if you have run one before.
That is the whole thing. There is no URL to enter, because NarraSEO crawls the project website and discovers pages itself.
What it Costs
1 credit per page crawled, as of 2026-08-30.
A 50 page audit is 50 credits, which makes this one of the cheaper things in the product. The cost is shown before you run.
Page Limits
One audit covers up to 100 pages. On a trial the per-run limit is 50.
There is also a monthly crawl budget, as of 2026-08-30:
For most sites this is not a constraint. It matters if you run a large site or audit frequently.
Choosing Which Pages to Audit
Manage pages, on the Pages audited metric, opens the page picker. It explains: "Choose which pages NarraSEO includes in the next site audit crawl. Each page costs 1 credit."
Pages come from crawl discovery, and you can add one manually.
This matters on a site with more than 100 pages, because the crawl cannot cover everything. Prioritise:
- Your money pages. Services, products, contact, pricing.
- Your highest-traffic pages, which you can find in Performance under Top pages.
- Your important articles.
Auditing 100 tag archives tells you nothing useful.
While it Runs
You see "A site audit is running. Results refresh automatically when it completes.", sometimes with a percentage.
You do not need to stay on the page.
What it Checks
Around 28 checks across seven categories:
Signals come from the crawl, Google Search Console where connected, and PageSpeed Insights.
Health Scores
Three bands: Good, Needs attention, and Critical.
Scores are shown overall and by category, so you can see whether your problem is content, speed, or something structural.
Re-Running
Refresh site audit in the header, or Retry audit after a failure.
Paid plans also get a monthly scheduled audit.
Two things can stop a run:
- "An audit ran recently. Try again in a few minutes."
- "Too many audits are already running for this workspace. Wait for one to finish."
Both are short waits rather than errors.
How Often to Run One
Monthly is plenty for most sites. A site audit finds structural and technical issues, and those do not change day to day.
Worth running after a site redesign, a platform migration, a hosting change, or before a significant content push.
Running weekly mostly spends credits confirming what you already know.
Notes
Audits are per project.
Nothing is changed on your website. The audit reads your pages and reports, it does not fix anything.
"Audit failed" means the scan could not finish, and your previous results were not changed.
The audit engine is enabled in production. On a local or staging environment without the flag, the page shows clearly labelled Sample data described as "Illustrative audit results, not a live crawl for this project", and run actions are disabled.
Related
Working through your site audit issues covers what to do with the findings.