SEO HTML Inspector

Paste page-source HTML to review common on-page SEO signals locally without fetching or crawling the live URL.

Inspect source HTML for common SEO signals

Paste source HTML. This analyzes supplied markup only; it does not fetch a live URL, render JavaScript, inspect HTTP status, or determine what a search engine indexed.

Page-source HTML

—Title chars

—Canonical links

—H1 elements

—JSON-LD blocks

Title	—
Description	—
Canonical	—
Robots	—
Hreflang	—
Structured data	—
Images	—

Use this as pre-publish QA. Indexing also depends on the live response, crawlability, rendered content, canonical evaluation and search-engine systems outside this browser.

Search-engine boundaries

Local markup checks cannot know what a crawler fetched, rendered, indexed or selected as canonical. Search engines may rewrite title links/snippets, choose different canonicals, ignore invalid or ineligible structured data, and apply live HTTP/robots conditions that are not present in pasted text. Treat these tools as pre-publish QA, then verify live behavior with the relevant search-engine tools.

Publication preflight, not an SEO score

Generated or pasted SEO data is checked for concrete structural conflicts, malformed values and handoff risks. The tool does not predict rankings, indexing certainty or rich-result eligibility.

Use this result with confidence

Static HTML inspection is not the same as a live crawl

Pasted source can reveal title, meta description, canonical, robots directives, headings, links, images, and structured data that are present in the markup. It cannot prove the final rendered DOM, HTTP status, redirect chain, response headers, robots.txt availability, or JavaScript-injected content unless those artifacts are supplied separately. Keep that boundary explicit when diagnosing an indexing problem.

Treat every check as evidence rather than a score

A missing title is clearly actionable, but many SEO signals are contextual rather than pass/fail rules. Description length, heading count, canonical choice, and link attributes should be interpreted against the page purpose. Avoid inventing a single numeric score that hides which evidence was found. A publication preflight is more useful when each warning maps to a specific source element.

Canonical and robots directives can conflict

A page may declare a canonical URL while also containing noindex, a conflicting header directive, or a canonical that redirects elsewhere. Inspecting one tag in isolation can therefore give false confidence. When a page matters for search, compare the HTML result with the live response, sitemap entry, and Search Console inspection rather than assuming one self-referential canonical guarantees indexing.

Structured data needs syntax and semantic validation

Finding a JSON-LD block does not prove that it is valid for a rich-result feature. Parse the JSON, identify the schema types, and then use the relevant validator for required properties and current search-engine eligibility. The same principle applies to hreflang and social metadata: presence is a useful first check, but destination-specific validation is the final handoff.