3tej home
Home/Utilities/Meta Tag Analyzer

What is Meta Tag Analyzer?

A Meta Tag Analyzer computes meta tag analyzer from the inputs you provide. It applies the standard formula to the values you enter and returns the result instantly, without sending any data to a server. Paste raw HTML to check title, description, canonical, charset, viewport, OG, Twitter, JSON-LD schema.

Meta Tag Analyzer

Paste your page HTML, get a full audit of title, description, canonical, OG, Twitter, robots, schema, and more, with prioritized fixes.

Browser-only Instant Free forever Works offline No signup
← Utilities

TLDR

Paste your page's raw HTML (View Source or right-click and Save). The analyzer parses the head, checks every important meta tag for presence and length, scans for OG and Twitter tags, validates JSON-LD blocks, and gives you an overall SEO meta score with a prioritized list of fixes. Pure client-side - no URL fetching, no CORS issues.

Runs entirely in your browser. No upload, no signup, no logging. Output is for personal or commercial use; we do not claim any rights to the data you enter.

How to use this tool

  1. Enter your inputs. Each field is labeled with what it expects.
  2. Read the result instantly. Numbers update as you type or change inputs.
  3. Adjust to test sensitivity. Change one input at a time to see what moves the result most.
  4. Cross-check the formula in the section below if you want to verify the math.
  5. Copy or screenshot the result for later. The site does not save anything; close the tab and inputs are gone.

About this tool and how it works

This utility runs 100% in your browser. No data leaves your device. The underlying logic is:

Score = matched_checks / total_checks * 100
Checks include: title present, description present, canonical, charset, viewport, lang,
og:title, og:image, og:description, twitter:card, JSON-LD present,
title length 15-70, description length 50-165.
13 checks total; each passes or fails. Score scales linearly.

You can verify by opening the browser developer tools and watching the Network tab; no requests fire during normal use beyond the initial page and library load.

Real-world scenarios where this tool helps

Pre-publish QA

Before pushing a page live, paste the rendered HTML and check the score. Most teams find at least one missing tag (typically og:image or canonical).

SEO audit of existing pages

Pull a few top pages, run them through, and tackle the most common gaps first.

Competitor research

View source on a competitor's page, paste here, see what they're shipping. Their structure can inform yours.

Teaching juniors

Use as a learning tool. The recommendations explain WHY each tag matters, not just whether it's present.

What this tool does

  • Parses your raw HTML and extracts every meta tag from the <head>.
  • Checks title, description, canonical, charset, viewport, robots, keywords, lang attribute, favicon, theme color.
  • Detects all Open Graph properties (og:title, og:description, og:image, og:url, og:type, og:site_name).
  • Detects all Twitter Card properties (twitter:card, twitter:title, twitter:description, twitter:image).
  • Detects all JSON-LD blocks, validates each as JSON, lists the @type and field count.
  • Computes an overall SEO meta score (0-100) based on 13 weighted checks.
  • Generates a prioritized recommendations list with specific copy-paste fixes.

What it does NOT do

  • Does not fetch URLs (CORS would block it). Paste raw HTML from View Source or browser dev tools.
  • Does not run Google's full rich-results validation - use Google Rich Results Test for that.
  • Does not check for indexability beyond the robots meta tag (does not look at robots.txt, X-Robots-Tag headers, or Google Search Console signals).
  • Does not check page speed, Core Web Vitals, or accessibility. This tool focuses on meta tag completeness.
  • Does not save your HTML. Close the tab and inputs are gone.

Common mistakes and pitfalls

  • Pasting the URL instead of the HTML. The tool cannot fetch URLs (CORS); you must paste raw HTML.
  • Forgetting that the tool only sees the SOURCE HTML. If your page renders meta tags via JavaScript (SPA), use View Source after the JS runs (often via Inspect plus Edit as HTML in the Elements panel).
  • Treating a 100/100 score as proof of SEO success. The tool checks meta tag hygiene. Content quality, backlinks, and technical SEO matter far more.
  • Adding meta keywords. Google has ignored it since 2009. The analyzer warns about it.
  • Setting og:image to a tiny thumbnail. Use 1200x630 PNG/JPG for clean rendering across Facebook, LinkedIn, iMessage.

Frequently asked questions

Why can't I paste a URL?

Browsers block cross-origin fetches (CORS). The tool runs in your browser, so it cannot grab arbitrary URLs. Paste the raw HTML from View Source instead.

How do I get raw HTML?

Open the page, right-click and select View Page Source (or Cmd+U / Ctrl+U). Select all (Cmd+A), copy, and paste here. For SPAs, use Inspect plus Edit as HTML to grab post-render markup.

What counts as 'good' meta description length?

Aim for 140-160 characters. Below 50 the snippet looks thin; above 165 Google truncates it. The analyzer flags both extremes.

Is meta keywords still useful?

No. Google announced it ignored meta keywords in 2009. Bing followed in 2014. Other search engines (Yandex, Naver) may still use it, but it carries near-zero SEO weight in 2026.

Why does the score require og:title and og:description?

Social-share visibility is part of modern SEO. A page that gets shared and clicked builds signals. Missing OG tags means weak social previews and lower share rates.

What if my JSON-LD is invalid?

The analyzer flags JSON parse errors. Common causes: trailing commas, smart quotes (curly quotes instead of straight), unescaped quotes inside strings. Fix in your CMS or template.

How is the SEO score calculated?

13 weighted checks: presence of title, description, canonical, charset, viewport, lang, plus key OG and Twitter tags, plus JSON-LD presence, plus title and description length within ranges. Pass = 1 point. Score = passes / 13 * 100.

Should I have multiple JSON-LD blocks?

Yes - common pattern is one BreadcrumbList plus one Article/Product/FAQPage per page. Each goes in its own <script> tag.

What's the difference between og:image and twitter:image?

OG image is used by Facebook, LinkedIn, iMessage, Slack, Discord, and most modern share unfurlers. Twitter image is used by X/Twitter. If both are missing, Twitter falls back to og:image, so you can usually skip twitter:image.

Does the analyzer check robots.txt?

No - that's a separate file at /robots.txt. This tool only checks the page-level robots meta tag.