Site audit

Check headers, redirects, TLS, SEO, robots and DNS.

Enter a domain or URL. Defaults to https://.

About this scan

Six checks for one page and host, in up to 30 seconds. External sitemaps are not visited. DNS records do not prove correct mail delivery.

Anyone with the result link can view the report. Reports expire after seven days. Query values and sensitive headers are redacted.

A snapshot, not a security guarantee.

From scan to solution

Turn a website audit into a clear next step

SiteAudit brings six checks together for one page and its host. Use the findings to investigate access, metadata, indexing directives and technical configuration. These guides explain how to prioritize the results and where a single-page check needs to be followed by a wider review of your website.

A few useful answers

Frequently asked questions

What does SiteAudit check?

SiteAudit combines six checks for one page and its host: HTTP headers, redirects, TLS, page SEO, robots and sitemaps, and DNS. It works within a 30-second scan budget. Review each module’s evidence to see what was measured and which checks could not complete.

Does SiteAudit crawl my whole website?

No. It checks the URL you submit and supporting information for that host. It does not discover every page or run JavaScript. Audit representative URLs from different templates, such as an article, product page and homepage, to investigate a broader site change.

A practical technical SEO audit checklist
Does a good audit score mean my page will rank higher?

The score summarizes this tool’s technical checks. It does not measure search rankings, content quality, backlinks or whether Google has indexed the page. Use individual findings to plan fixes and Search Console to investigate search visibility.

Why is part of my audit marked incomplete or not checked?

A module may lack usable evidence because of a timeout, response-size limit, connection failure or unsupported response. That is not the same as a confirmed problem with your site. Review the explanation, resolve any access issue and run the audit again.

Can robots.txt stop a page appearing in Google?

A robots.txt crawl block alone does not reliably prevent indexing. Google must be able to read a noindex instruction to apply it. SiteAudit shows relevant evidence, but does not confirm Google’s indexed state or fully simulate its crawler.

robots.txt vs noindex: which one should you use?