🏗️ Static HTML Audit

Inspect the raw HTML, response headers, and metadata of any public page. Use it to spot crawlability, usability, snippet, sharing, and page-quality issues that are visible without running a browser.

ℹ️ Note: This is a server-side HTML inspection. It does not run Google Lighthouse, execute JavaScript, render the page, measure Core Web Vitals, or perform a complete accessibility audit. For a full browser-based audit, use Lighthouse in Chrome DevTools or PageSpeed Insights.

Run HTML Audit

Enter any public URL to run a server-side HTML inspection. We'll analyze the HTML, headers, and structure across 4 categories.
Quick test:

About This Server-Side HTML Audit

This tool performs a server-side analysis of any public page by reviewing the returned HTML, response headers, and visible metadata. It is best used for checks that can be confirmed without rendering the page in a browser: document structure, metadata completeness, HTTP behavior, sharing tags, and basic page-quality signals.

Important: This audit does not directly influence rankings and does not predict ranking changes. It fetches only the public URL you enter and does not access private Search Console, Analytics, ranking, or backlink data.

Four Analysis Sections

Document Size, Accessibility Markup, Security Headers, and SEO Metadata — each scored 0-100 with a weighted overall score.

Detailed Check Results

Every category has individual checks showing pass/fail/warn status, point deductions, and explanations.

Actionable Recommendations

SEO issues come with specific suggestions and code examples to help you fix problems quickly.

📤
Export & Share

Copy the full report as text or download as JSON to track improvements over time.

Fast Server-Side Check

No browser startup time — results in seconds. Perfect for quick checks during development.

URL Parameter Support

Pre-fill via ?url=https://example.com for easy bookmarking and automation.

Why Server-Returned HTML Still Matters

  • Meta tags — Title tags and meta descriptions shape how a page can be understood and previewed in search snippets.
  • Mobile usability — A correct viewport tag helps pages render properly on phones and other small screens.
  • Structured content — A logical heading hierarchy helps crawlers and people understand how the page is organized.
  • Accessibility signals — Alt text, language declarations, and semantic HTML support screen readers and clearer page structure.
  • Technical fundamentals — HTTPS, correct HTTP status codes, and consistent content types help pages load and behave as expected.
  • Social sharing — Open Graph and Twitter Card tags help control how shared links are previewed across social platforms and messaging apps.

Regular server-side HTML inspections help you catch issues early, compare templates, and validate markup before you move on to browser-based QA.

Frequently Asked Questions

A Static HTML Audit checks a web page against server-side inspection criteria. It reports on document size, resource count, metadata, document structure, basic accessibility markup, and security headers — giving each a score out of 100. Our tool does this server-side, analyzing the actual HTML, headers, and structure of any public URL you submit. The report covers: HTML Document Size (page weight, resources, redirects), Basic Accessibility Markup (viewport, alt text, headings), Security & Response Headers (HTTPS, doctype, HTTP status), and SEO Metadata (title, meta description, meta tags, robots directives).
Browser-based audits like Google's Lighthouse run with JavaScript execution, network throttling, and CPU profiling in a real browser. Our tool performs a server-side analysis of the fetched HTML, headers, and metadata. While we cannot execute JavaScript, measure real paint times, or perform network/CPU profiling, we check structural and metadata signals — including viewport meta, title tag, meta description, heading structure, image alt attributes, HTTP status, HTTPS, robots directives, and page weight. The scores focus on structural and metadata checks that are verifiable from server-side HTML analysis.
Audit scores are color-coded: 90-100 (green) is considered "Good" — the page looks structurally healthy based on the checks we can verify from raw HTML and headers. 50-89 (orange) "Needs Improvement" — there are issues worth reviewing. 0-49 (red) "Poor" — the page has significant crawlability, metadata, usability, or sharing problems. Treat the score as a diagnostic summary, not a prediction of search performance.
This audit does not directly influence rankings and does not predict ranking changes. It helps you find technical and metadata issues that may affect crawlability, usability, snippets, sharing, or page quality. Validate important fixes with Search Console, PageSpeed Insights, browser DevTools, and your own crawl data.
Our Document Size analysis examines page weight (total HTML size), the number of external resources (CSS, JS, images, fonts), redirect chains that slow down page load, and transfer size. This is a server-side HTML inspection — it does not execute JavaScript or measure real browser paint times. Research shows that pages under 100KB transfer size with few redirects and minimal external resources consistently load faster. Key recommendations include: reducing redirects, minimizing external resource calls, enabling compression (gzip/brotli), and keeping HTML under 100KB.
Our Accessibility analysis checks for: a viewport meta tag with width=device-width (critical for mobile accessibility and Google's mobile-first indexing), image alt attributes on all images (essential for screen readers and SEO), a proper H1 heading (important for document outline and navigation), heading hierarchy with no skipped levels (H1→H2→H3, not H1→H3), and a doctype declaration (ensures standards mode rendering). These checks align with the WCAG 2.1 accessibility guidelines.
Our Security & Response analysis covers: HTTPS enforcement (is the page served securely), HTTP status code (200 OK is ideal, 4xx/5xx indicate problems), doctype declaration (ensures standards mode), character encoding declaration (UTF-8 recommended), server information disclosure (should be minimal for security), and whether the page uses modern protocols. These align with security and best-practices guidelines which flag HTTPS issues, console errors, deprecated APIs, and security concerns.
Our metadata and structure analysis checks: meta title tag presence and length, meta description presence and length, viewport meta tag (required for mobile-friendliness), meta keywords tag, robots meta tag (noindex/nofollow directives), H1 heading presence and count, image alt attributes, language declaration (html lang attribute), Open Graph tags (og:title, og:description, og:image), Twitter Card tags, favicon presence, and links (internal vs external ratio). Each item has a weighted score that contributes to the final 0-100 structure score.
To improve your scores: (1) Document Size — enable compression, minify CSS/JS/HTML, reduce redirects, use a CDN, optimize images, and eliminate render-blocking resources. (2) Basic Accessibility Markup — add missing alt text to images, ensure proper heading hierarchy, set viewport meta tag, increase color contrast, and add ARIA labels to interactive elements. (3) HTTP and Security Basics — serve over HTTPS, fix broken links, avoid mixed content, and use modern doctypes. (4) Metadata — write unique title tags and meta descriptions for every page, ensure exactly one H1, and set proper OG tags for social sharing.
Currently this tool checks one URL at a time. For bulk checking, you can use our SEO Audit Checker tool which scans entire pages. For automated monitoring, we recommend using server-side tools in your deployment pipeline. The URL can also be passed via query parameter: simply append ?url=https://example.com to auto-load and start an audit.
Tool notes: Review date, data source, and tool-specific limitations

Last reviewed: 2026-06-11 · Reviewed by: Marc LaClear · Version: v1.1

Sources:

Limitations:

  • Checks are based on publicly fetchable HTML, response headers, and browser-side input. They do not use private Google Search Console, analytics, or ranking data.
  • Scores and warnings are diagnostic aids, not guarantees of ranking improvement or Google indexation.
  • Pages blocked by robots.txt, login walls, bot protection, heavy JavaScript, or network timeouts may return incomplete results.
  • Validate critical fixes with official Google tools such as Search Console, Rich Results Test, Lighthouse, and your own crawl data.

Report an issue with this tool