Skip to main content
Toollyz

Search tools

Search for a command to run...

Meta Tag Analyzer

Paste a page's HTML and get an SEO score out of 100, broken down across 7 categories: Title, Description, Technical (charset/viewport/lang/canonical/robots), Open Graph, Twitter Card, International (hreflang + x-default), Structured Data (JSON-LD), and PWA (theme-color + manifest). Granular checks tell you exactly what to fix. 100% offline.

What is the Meta Tag Analyzer?

Meta Tag Analyzer is a holistic SEO meta-tag audit — broader than the Open Graph Preview (which renders social cards) and complementary to the Canonical URL Checker (which focuses on URL normalisation). The audit covers eight scoring categories: **Title** (presence + 30-60 char sweet spot, max 16 pts), **Description** (presence + 70-160 chars, max 14 pts), **Technical** (charset + viewport with width=device-width + html lang + canonical + robots, max 14 pts), **Open Graph** (og:title/description/image/url/type, max 16 pts), **Twitter Card** (twitter:card/title/description/image plus card-type validation, max 10 pts), **International** (hreflang count + x-default, max 8 pts), **Structured Data** (JSON-LD parse + recognised @type values like BreadcrumbList/Article/Product/Organization/WebSite/FAQPage, max 12 pts), and **PWA** (theme-color + manifest link, max 10 pts). Total: 100 points. Each category renders a progress bar so you see at a glance which area is under-served. Individual checks call out specifics: title length warnings, missing og:image, contradictory robots directives, invalid twitter:card values, broken JSON-LD parsing, etc.

How to use it

  1. Paste a page's HTML into the textarea (head is enough).
  2. Read the score at the top — 85+ is excellent, 60-85 has gaps, < 60 needs work.
  3. Use the breakdown bars to spot the weakest category at a glance.
  4. Scroll through Findings — each entry tells you exactly what to fix.
  5. Open the OG / Twitter / metas panels to inspect every individual tag.

Benefits

  • Holistic 0-100 score across 8 weighted categories.
  • Title + description length checks against the actual SERP truncation thresholds.
  • Technical category covers charset, viewport, lang, canonical, robots — the foundations.
  • Open Graph and Twitter Card audited independently with per-tag scoring.
  • Hreflang detection with x-default best-practice check.
  • JSON-LD parsed and `@type` values surfaced (BreadcrumbList, Article, Product, etc.).
  • PWA category checks for theme-color + manifest — required for installable web apps.
  • Score breakdown progress bars colour-coded green/amber/red.
  • Every meta tag (recognised and 'other') shown in a flat list for manual inspection.
  • Runs 100% in your browser — no server, no upload.

Frequently asked questions

How is this different from the Open Graph Preview?

OG Preview renders Facebook/X/LinkedIn card mockups so you can see how a share will look. Meta Tag Analyzer scores the broader SEO health of the page — title length, description length, technical foundations (charset/viewport/canonical), JSON-LD structured data, PWA tags. Use both: this for the score, OG Preview for the visual.

How was the scoring weighted?

Reflects practical SEO impact: Title (16 pts) and Description (14 pts) drive direct SERP appearance. Technical (14) and OG (16) cover the foundations + social. Twitter (10), PWA (10), International (8) and JSON-LD (12) round out the picture. Edit the weights in `lib/tools/text/meta-analyzer.ts` if you disagree.

What's the target score?

85+ is excellent — every essential is set with no length problems. 60-85 means the foundations are right but some categories are under-served (often JSON-LD or PWA). Under 60 has gaps you should close before launch.

Why does title get a warning at 60 chars?

Google truncates SERP titles around 580-600 pixels — roughly 60 characters in a typical font. Anything past 60 risks being chopped mid-word.

Why is meta description in the 70-160 char range?

Google rewrites descriptions on the fly more aggressively than titles, but the 70-160 sweet spot remains. Under 70 leaves SERP real estate empty; over 160 may be truncated on mobile.

Does it score the JSON-LD content?

It checks that the JSON parses and surfaces the `@type` values. Full Schema.org validation (required fields per type, recommended values) is out of scope — use Google's Rich Results Test for that level.

Why is x-default flagged for international sites?

Google recommends `hreflang=x-default` for the fallback when no other locale matches. Multi-locale sites without it can leak the wrong page to users in unmatched regions.

What about robots.txt?

Out of scope for this tool — see the Robots.txt Generator and the Sitemap Validator for crawl control. This tool only audits the on-page `<meta name=robots>` tag.

Why no live preview of how Google would render?

Google's SERP visuals change frequently; rendering a 'pixel-perfect' mock would be misleading. We focus on the underlying signals — Google's rendering follows from those.

Are my pastes saved?

Yes — the textarea content persists in localStorage under `toollyz:meta-analyzer` so a refresh doesn't lose your audit.

Is anything uploaded?

No. Parsing and scoring run entirely in your browser.

Related tools

See all developer tools