All The Validators logoAll The Validators

web validator

HTML Meta SEO Validator

Validate rendered HTML document basics—charset, html lang, language targeting, and launch-readiness signals that support crawl, accessibility, and snippet QA.

Results

Paste input and validate locally.
Status
Ready when you validate.
Details
Ready when you validate.
Charset
Ready when you validate.
Lang
Ready when you validate.
Issues
Ready when you validate.

How to use this validator

  1. Open the page source, deployed preview, or crawler export for the page you want indexed.
  2. Copy the opening <html> tag plus the <head> block, or paste the full rendered HTML document.
  3. Run the validator and fix missing charset, missing html lang, or template output that does not match the intended page language.
  4. Pair the result with title/description, canonical/hreflang, meta robots, Open Graph, and structured-data checks during final SEO QA.

Rules & checks

Requires a charset meta tag such as <meta charset="utf-8"> or an http-equiv content-type declaration with charset.

Requires lang on the <html> element so crawlers, browsers, translation tools, and assistive technology can identify the page language.

Validates rendered markup, not framework source, because CMS themes and build pipelines can remove or duplicate head tags.

Runs fully client-side on pasted HTML; it does not fetch URLs, render JavaScript, or infer the true content language.

Inputs explained

  • Rendered HTML or <head> snippet

    Paste view-source output, a deployed preview, crawler-exported HTML, or the final head/body shell from your CMS or framework. Include the opening <html> tag and <head> when possible so charset and lang can both be checked.

When to use it

  • QA page templates for accessibility, international SEO, and browser rendering before launch.
  • Check CMS, ecommerce, static-site, or Next.js head output after metadata changes.
  • Verify localized pages before pairing them with canonical/hreflang and sitemap.xml QA.
  • Review crawler exports when Search Console or accessibility audits report missing language or encoding signals.
  • Support teams reviewing user-submitted HTML snippets without uploading markup to a third-party service.

Common errors

  • Missing <meta charset="utf-8"> in the rendered head even though the source component defines it.
  • Missing lang on <html>, especially on CMS pages, landing-page builders, and generated route shells.
  • Language codes that do not match the page content or hreflang alternate set.
  • Duplicate or conflicting charset declarations from theme/plugin overrides.
  • Testing source JSX or template code instead of the final rendered HTML crawlers will see.

Limitations

  • Structural document check only; it does not analyze whether the visible text truly matches the declared language.
  • Does not fetch live URLs, render JavaScript, inspect HTTP headers, or validate title/description quality.
  • Does not replace full accessibility, internationalization, or browser-compatibility testing.

Tips

  • Declare UTF-8 early in the head so browsers determine encoding before parsing visible content.
  • Set html lang to the primary page language, such as en, es, fr-ca, or en-gb, and keep it aligned with hreflang clusters.
  • Validate rendered HTML, not only source components, because frameworks and CMS plugins can rewrite document shells at build or runtime.
  • Use this with the viewport, canonical/hreflang, meta robots, Open Graph, and JSON-LD validators for a complete launch pass.

Examples

Valid English page shell

  • <html lang="en"><head><meta charset="utf-8"><title>Example page</title></head></html> -> Meta set

Missing lang

  • <html><head><meta charset="utf-8"></head></html> -> flagged because the primary page language is not declared

Missing charset

  • <html lang="en"><head></head></html> -> flagged because browsers and crawlers need an explicit character encoding

Localized page mismatch

  • A Spanish page template with <html lang="en"> should be corrected to lang="es" before hreflang and sitemap QA.

Deep dive

Charset and html lang are small document-level signals, but missing them can create noisy accessibility audits, inconsistent rendering, confusing translation prompts, and weaker international SEO QA.

Use this validator as the foundation layer before checking title tags, meta descriptions, canonical URLs, hreflang alternates, meta robots, sitemap.xml inclusion, Open Graph previews, and structured data.

Because validation runs in your browser on pasted HTML, you can inspect private previews, client CMS templates, and crawler exports without sending page markup to a server.

FAQs

Is anything uploaded?
No. Parsing is local in your browser and clears on refresh.
Should every page use UTF-8?
For modern web pages, yes. UTF-8 is the expected default for consistent rendering across browsers, crawlers, feeds, and international content.
Is html lang an SEO ranking factor?
It is primarily an accessibility, browser, and localization signal. It also reduces ambiguity in international SEO QA and should align with hreflang where relevant.
Can I paste a full HTML document?
Yes. Paste the full rendered document or the opening <html> tag plus <head> block; validation stays local.

Related validators

web

JSON-LD SEO Validator & Rich Result Schema Checker

Validate rendered JSON-LD structured data for schema.org syntax, rich-result readiness, visible-content alignment, and crawlable schema blocks before publishing.

All HTML meta validation runs in your browser. Pasted markup is not uploaded, logged, or stored.

Basic structural check only; does not analyze content language, title quality, HTTP headers, or live crawl/indexation status.