Skip to main content

Meta Tags Analyzer

Parses pasted HTML and rates its title, meta description, Open Graph, X Card, viewport, charset, robots, and canonical tags. Titles of 30 to 60 characters and descriptions of 70 to 160 pass as common guidance, counted by code point. A missing twitter:title, description, or image is not flagged when the matching og tag exists, since X falls back to it.

Runs entirely in your browser

This tool sends nothing over the network. Everything you enter is processed on your device and never reaches our servers.

Marketing
Web
Loading the tool
Reference

Documentation

A meta tags analyzer reads the head of an HTML document and reports the tags that search engines and social platforms use to describe a page: the title element, the meta description, Open Graph properties, X (Twitter) Card tags, and technical tags such as viewport, charset, robots, and the canonical link. The source is parsed with the browser's own HTML parser, and attribute values such as name="Description" are matched without regard to letter case, as Google does for meta tags other than google-site-verification.

Only HTML pasted into the tool is analyzed. A web page cannot request another site's source because browsers block cross-site reads, so the source comes from View Page Source (Ctrl+U, or Cmd+Option+U on a Mac). View Page Source shows the HTML the server sent. Tags that a script inserts after the page loads, which is common on single-page applications, appear only in the rendered page, and the browser's developer tools can copy that version as HTML.

A title of 30 to 60 characters and a meta description of 70 to 160 characters pass, and shorter or longer ones receive a warning. These ranges are common guidance rather than rules: Google states that there is no limit on the length of either element and that it shortens title links and snippets as needed to fit the device width. Characters are counted as Unicode code points, so an emoji counts once rather than twice. The Open Graph check looks for og:title, og:description, og:image, og:url and og:type. For X, twitter:card has no substitute, while a missing twitter:title, twitter:description or twitter:image is reported as covered when the matching Open Graph tag exists, because the X card processor falls back to it.

A viewport that sets user-scalable=no or a maximum-scale below 2 is flagged, since it stops readers from zooming to the 200 percent that WCAG 1.4.4 (Resize Text) expects. A charset other than UTF-8 is flagged because the HTML standard requires UTF-8. A missing robots tag is informational, as Google treats its absence as index, follow, and a missing canonical link is a warning because search engines then choose the canonical URL themselves. Any remaining meta tags, such as author, theme-color or site verification codes, are listed as found.

The summary counts tags analyzed, tags that passed, and issues. Each missing Open Graph tag counts as one issue, so a page with no social tags at all shows several issues even when its search tags are sound. A passing length does not guarantee that the text is shown: Google builds snippets primarily from page content and uses the meta description when it judges that description more accurate.

A page whose title is Trail Running Shoes for Wet Weather | Example Store (51 characters), with a 120-character description, all five Open Graph tags, twitter:card set to summary, a plain viewport and a UTF-8 charset, but no canonical link, reads 10 tags analyzed, 10 passed and 1 issue. Its twitter:title, twitter:description and twitter:image are reported as covered by the Open Graph tags rather than missing, and the absent robots tag is informational.

Validating meta tags before publishing a page prevents search engines from displaying truncated titles, missing descriptions, or broken social previews. The following scenarios illustrate where tag analysis fits into common workflows.

  • Pre-launch auditing: Run every page of a new website through the analyzer before going live. Catch missing Open Graph images, absent X card tags, or meta descriptions long enough to be cut off in search results.
  • Content migration: When moving content between platforms or CMS systems, paste the source of migrated pages to confirm that title tags, canonical links, and robots directives transferred correctly. Flag any pages where the migration stripped or duplicated meta elements.
  • Competitor research: The page source of competitor landing pages shows which Open Graph properties and X card types they use, how long their titles and descriptions are, and whether they set specific robots directives.
  • Social media optimization: Verify that og:image, og:title, and og:description are present and contain the intended content before sharing a link on social platforms. Missing or incorrect Open Graph tags cause generic or blank previews when links are posted.
  • Technical SEO reviews: A technical review confirms that the viewport tag is present and allows zoom, the charset is UTF-8, the canonical link points to the intended URL, and the robots tag permits indexing where it should.
  • Template validation: Test CMS or static site generator templates by pasting a rendered page and confirming that dynamic title and description fields populated correctly. Identify templates that output empty or placeholder meta tag content.
  • Client reporting: Summary counts and status ratings for a client's page source produce a clear list of meta tag issues and recommendations for on-page SEO improvements.
  • Accessibility compliance: Viewport tags that set user-scalable=no or a maximum-scale below 2 are flagged, which catches a common mobile zoom barrier before a full accessibility audit does.
Inputs, outputs, and what the Meta Tags Analyzer computes

What the Meta Tags Analyzer asks for and what it returns, as a plain list. Defaults, units, and ranges are the ones the form loads with.

Inputs

  • Paste HTML source code to analyze

Controls

Analyze · Reset

Example

A page whose title is Trail Running Shoes for Wet Weather | Example Store (51 characters), with a 120-character description, all five Open Graph tags, twitter:card set to summary, a plain viewport and a UTF-8 charset, but no canonical link, reads 10 tags analyzed, 10 passed and 1 issue.