Evidence-based multi-page audit

How to Do a Website Audit: Step-by-Step Checklist for Developers

Run a comprehensive technical SEO, on-page, crawlability, performance, security, image, link and structured-data audit.

Public HTTP/HTTPS sites only. Private networks are blocked. The crawler reads source HTML but does not execute page JavaScript.

Connecting to website…

Validating the public host and homepage response.

0/ 100—
AUDIT RESULT

Pages audited0
Checks run0
Passed0
Warnings0
Critical0
Audit time0s
Health breakdown

Category scores

Measured evidence

Audit findings

Crawl sample

Audited pages

PageStatusSEOContentImagesIssues
Accuracy boundary

Not measured or inferred

Accuracy: every reported pass/fail is based on fetched HTTP responses, headers and source HTML. Results can change when a site, CDN or network changes. Metrics requiring a real browser or third-party index are listed separately and never guessed.

Tool guide

About Website Audit

Run Website Audit to check technical SEO signals, page health, crawl readiness, and practical website issues.

How to use Website Audit

  1. Open Website Audit and review the labels, accepted format, and any defaults shown beside the controls.
  2. Enter or select the domain or URL; use valid, complete data rather than placeholder values.
  3. Run the tool and inspect the analysis for warnings, rounding, formatting, or missing information.
  4. Copy or download the Website Audit result only after comparing it with the original input.

Key features

  • Purpose-built controls for the Website Audit workflow.
  • A clear analysis based on the values supplied on this page.
  • Input guidance aligned with this implementation: Run Website Audit to check technical SEO signals, page health, crawl readiness, and practical website issues.
  • Server-rendered Website Audit instructions and direct related-tool links that remain readable without running JavaScript.

Common use cases

  • Use Website Audit during a technical review of a site you manage.
  • Investigate the specific public DNS, URL, server, or search signal exposed by Website Audit.
  • Collect Website Audit evidence before making configuration changes.

Practical example

Enter a domain you control or are authorized to inspect, run Website Audit, and review each returned signal separately rather than treating a single check as a complete audit.

How it works

Website Audit normalizes the submitted domain or URL, requests the public signal needed for this check, and organizes the available response. Missing data can mean that a provider did not return a value; it does not automatically prove that the underlying record or resource does not exist.

Limitations

Website Audit is limited by public availability, network timeouts, provider responses, rate limits, and the exact URL or domain submitted. One result is not a substitute for a full crawl or account-level data.

Privacy and security

Website Audit may send the submitted public domain or URL to this application's server and relevant public lookup providers. Do not submit private intranet addresses, credentials, tokens, or confidential query strings.

Frequently asked questions

What input does Website Audit require?

Use the labeled domain or URL field or selector in Website Audit. The accepted format, range, and required fields are shown beside the relevant control.

How should I verify the Website Audit result?

Test a small known Website Audit example, compare the analysis with the source, and check any current official specification or provider rule that applies to your use case.

Why might Website Audit show an error or different result?

Invalid formatting, unsupported files or syntax, browser limits, rounding, unavailable public data, or different assumptions can change the Website Audit result. Correct the input and review the page limitations before trying again.

Can I use Website Audit for sensitive information?

Use non-sensitive Website Audit samples whenever possible. Follow the privacy note on this page and never paste passwords, private keys, access tokens, or confidential records into a field that does not explicitly require them.