About this tool
Replace fragmented manual checkers with one bounded request that distinguishes collected static evidence from JavaScript-rendered behavior it cannot inspect.
- Revalidates public DNS on every redirect, allows only HTTP(S) ports 80 and 443, pins the selected address, and enforces shared rate, concurrency, deadline, body, and redirect limits.
- Uses a standards-compatible HTML parser to inventory source lines, title and description entries, canonical and hreflang links, robots directives, headings, social metadata, JSON-LD syntax, links, image alt attributes, and HTTP resource candidates.
- Separates confirmed response evidence from advisory review, reports redirect loops and truncation as partial evidence, and never assigns an arbitrary SEO score.
- Exports a versioned JSON report only for the current URL while stating that JavaScript, linked targets, indexing, ranking, structured-data eligibility, TLS, and runtime behavior remain unverified.
How to use Technical Audit
Enter one absolute public HTTP or HTTPS URL, run the bounded server audit, confirm the final response and evidence scope, then review findings by metadata, response, and resource view before exporting the versioned JSON report.
When this tool is useful
- Capturing repeatable static response evidence before or after a release.
- Reviewing redirects, canonical and robots declarations, selected security headers, headings, JSON-LD syntax, link counts, image alt coverage, and HTTP resource candidates together.
- Separating source-response facts from checks that still require a rendered browser, Search Console, or a site crawler.
Practical tips
- Treat missing values as not observed in this bounded static response, not proof that rendered HTML or another region lacks them.
- Use URL Inspection or a rendered browser audit for JavaScript-injected metadata and runtime requests.
- Do not enter private, credentialed, or internal URLs; private and non-public destinations are rejected on every hop.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
Audit a public release page
Example input
https://example.com/campaign
Expected output
Redirect chain, final status, selected response headers, static metadata and source lines, heading and resource counts, JSON-LD syntax, findings, and JSON evidence
The endpoint fetches one bounded response chain; it does not crawl the site or execute page JavaScript.
Validation checklist
- Confirm that the final URL, status, content type, and complete or partial scope match the response you intended to inspect.
- Read the exact source line or response-header evidence before acting on a finding.
- Fetch canonical and hreflang targets and validate reciprocal annotations separately.
- Recheck rendered DOM, runtime network activity, structured-data eligibility, index state, and Core Web Vitals with purpose-built tools.