VoriTools

Technical SEO HTML Inspector

Load the page’s HTML source and review the findings. This source-level report cannot confirm live headers, rendered content or search indexing.

Runs locally in your browser
View category: SEO & Website Audits (7)
This checker analyzes pasted source or a selected local HTML file. It does not crawl, fetch, render, or send the page to a server.

This is a source-level check. It cannot confirm rendered content, index coverage, crawlability, link destinations, live HTTP headers, or search engine decisions.

On-page signal summary
  • Paste HTML source to check visible on-page technical signals.

Use the page’s actual content to guide its metadata

Useful metadata describes the specific page task; it is not a keyword list. Keep localized equivalents genuinely equivalent, then validate their canonical and hreflang relationships in the final HTML.

How to inspect HTML source for technical SEO signals

Paste the HTML source of a page, or open a local .html or .htm file, and press Inspect HTML. The run reads the elements a crawler reads from the source: title, meta description, canonical, hreflang alternates, headings, image alt attributes, Open Graph tags, robots directives and JSON-LD.

Everything happens in this browser. The page is never requested, the source is not uploaded, and the tool keeps working with the network off.

  1. Paste the page source into the field, or choose a local HTML file; the file is read on your device.
  2. Press Inspect HTML.
  3. Read the five counters first: title characters, description characters, H1 headings, hreflang links and action items.
  4. Read the list underneath: every line names the element it refers to, then what was found.
  5. Press Copy report to take the list out of the page, or Clear to empty the field and the report.
  6. Press Load example to see a short page that passes every check.

What each counter means, what is read, and what the report cannot confirm

What the five counters mean

The title counter turns green between 30 and 65 characters and the description counter between 70 and 165. Those are the ranges this check treats as practical for a search snippet; they are not a Google rule, and a page can rank with a title outside them.

The H1 counter turns green at exactly one heading. The hreflang counter only counts alternates and stays neutral. Action items counts warnings and problems: informational lines such as a missing og:image are listed but not counted. Characters are counted as code points, so an emoji is one character.

What is read from the source

The checks look for a lang attribute on <html>; a charset declaration in either form, the modern meta charset or the older http-equiv Content-Type; a viewport tag; one absolute HTTPS canonical URL; one H1; a heading order without jumps; alt attributes on images that are not marked decorative; and an Open Graph title, description and image.

Meta names are matched without case, so Description and ROBOTS are read like description and robots. Every robots tag is inspected: any noindex is reported, and a second robots or description tag is listed as a duplicate. hreflang values are compared without case, so EN and en count as the same language.

What the report cannot confirm

This is a source check. The page is never requested, so live HTTP headers, redirects, cookies, compression and TLS are out of scope, and so is anything the browser adds while rendering: script-generated markup, lazy-loaded images, or canonical and hreflang tags injected at runtime.

The report also says nothing about crawling, indexing, ranking or traffic, and it does not resolve links: a relative canonical is flagged, but a link that returns 404 is not. JSON-LD is only checked for valid JSON and the declared @type list, not against the requirements of schema.org, and the wording of a parse error comes from the browser, in the browser language.

Recent tools: