Start researching

Site audit

Crawl a website to find technical and on-page problems, ranked by how much they matter.

5 min read

A site audit visits your pages the way a search engine would and reports what could hold them back: missing titles, duplicate content, broken links, redirect chains, slow pages and more. Every crawl is kept, so you can see whether your fixes are working.

Run an audit

  1. Open Site Audit

    Choose it in the left sidebar.

  2. Enter the website

    A domain such as example.com, or a section such as example.com/blog to audit only that part of the site.

  3. Pick a size

    Quick check (100 pages), Standard (500 pages, with images, CSS and scripts) or Deep audit (2,000 pages with JavaScript rendering, spelling and structured-data checks). The price is shown on the button before you spend anything.

  4. Adjust the crawl settings if you need to

    Open Crawl settings to set the page limit (25 to 10,000), a section to start from, link depth, desktop or mobile, JavaScript rendering, subdomains, the sitemap, spelling and schema checks. JavaScript rendering costs about ten times the base price per page and checking images, CSS and scripts about three times; the other options cost nothing extra.

  5. Confirm and start

    The app confirms the price and that this is a live crawl that uses credit. The price is for the page limit you chose and is taken when the crawl starts (a site with fewer pages than the limit is not cheaper, and stopping early does not refund it), so pick a limit close to your site size. If your balance is too low for the size you chose, it will ask you to pick fewer pages.

Read the results

Illustration with sample data

A finished audit opens on the Overview: a site health score out of 100, how it changed since the last crawl, pages with critical issues, broken links, duplicate and non-indexable pages, average load time, charts for issue severity and response codes, and the top issues to fix. The other tabs go deeper:

TabWhat it shows
IssuesEvery kind of problem found across the site, by severity and how many pages each affects. Open one to see exactly which pages.
PagesEvery crawled URL with its status, title, issues, score, load time and word count. Quick filters find critical issues, errors, redirects, slow and thin pages.
LinksInternal and external links, with quick filters for broken and nofollow links.
ResourcesImages, scripts and styles the pages load.
Duplicate contentPages that repeat each other's content or titles.
Non-indexablePages search engines are told to skip, on purpose or by mistake.
Redirect chainsURLs that bounce through several redirects before landing.
PerformanceCore Web Vitals and Lighthouse scores for pages you choose (optional, charged per page and device). Lighthouse loads each page in a real browser from the provider's data centre. If your site's firewall or CDN refuses that browser (HTTP 403), the audit fails with that reason, and the provider still bills it, so allow the request or skip that page. Pages the crawl saw redirect or return an error are refused before anything is charged.
HistoryEvery crawl of the site, the score over time, and a side-by-side comparison of any two crawls.

Every table can be searched, sorted (Shift-click a column to add a second sort), filtered with rules, trimmed to the columns you want and exported to CSV. Click any row to open its detail. For a page, that shows its issues grouped as Critical, Warning and Notice, its content, and the checks it passed.

Re-run, compare and schedule

  • Opening a site you have already audited with the same settings shows the finished audit again, free.
  • Choose Run again when you have made fixes. This starts a new crawl and uses credit. The earlier crawl is kept, so the History tab can show what got better or worse.
  • Schedule re-crawls a site every week or month. It is off until you turn it on, each run is charged like a manual audit up to a spending limit you set, and you can get an email when the score drops or new critical issues appear. A schedule pauses itself if you run out of credit or it fails three times in a row.
  • If an audit stops part-way, for example because your balance ran out while the results were being saved, choose Resume: it continues without starting a new crawl.
  • Your audits lists every site you have audited. Remove one to hide it and switch off its schedule; its crawls stay saved.

Use it from an AI assistant

Your connected AI assistant can read your audits (scores, issues, rows, comparisons, trends, Lighthouse results), start and re-run audits, resume or stop them, run Lighthouse on pages, re-check a page, and remove an audit. Stopping or removing something only happens when you ask for it.