Site Audit and Site Health

How an audit works

An audit starts at your home page and follows the internal links it finds, reading at most 50 pages and going at most four links deep. It honors robots.txt and reads pages only: it never submits forms or signs in.

Audits run in the background between other work, so a larger site takes longer. The project shows the audit's progress, and you can leave the page while it runs.

What it checks

Status codes and redirects; whether each page can be indexed (noindex, canonical tags, robots.txt); titles, meta descriptions and headings; internal and broken links; your XML sitemaps; and content signals such as near-empty or duplicated pages.

Reading the results

Site Health lists issues by priority, with the affected pages. Open an issue to see every page it affects, or open a page to see everything found on it.

When audits repeat, Site Health compares each one with the last, so you can see what is new, what got worse and what you fixed.

When an audit fails

The most common causes are a site that refuses the crawler, a robots.txt that disallows it, an address that does not resolve, or a site behind a sign-in. The audit says which; fix the cause and start a new one.