What this meta tag analyzer checks
It pulls every SEO-relevant meta tag from any URL in one shot: title, meta description, canonical, viewport, language, charset, robots directives, H1, Open Graph (Facebook, LinkedIn, Slack), Twitter Card, and favicon. For each tag it tells you whether it is present, whether the length is in the optimal range, and what the value is. Three categories: core SEO, technical, social.
Most sites have one or two of these wrong. The classic patterns we see: a title that exceeds the SERP pixel limit, a missing meta description, a canonical tag pointing to the wrong URL, or Open Graph tags that mismatch the rendered title and image.
Title and description: the on-page basics
The title tag is what shows in Google search results. Aim for 30 to 60 characters and approximately 580 pixels or under to avoid truncation. The meta description sits underneath in the SERP. Aim for 120 to 160 characters. Both are critical click-through-rate levers and both get rewritten by Google when poorly matched to the query.
Missing either of these is the most common SEO mistake. The analyzer flags missing or oversized title and description fields in the issue list with severity-graded recommendations.
Canonical, viewport, and indexing directives
Every indexable page should have a self-referencing canonical tag pointing to its preferred URL. This protects against duplicate content from URL parameters, tracking codes, and trailing slash variations. Pages you do not want indexed should use the noindex meta robots tag, not robots.txt.
The viewport meta tag (content="width=device-width, initial-scale=1") is required for mobile-friendly rendering. Without it, mobile devices render the page as if it were 980 pixels wide and zoom out, breaking layout. Google's mobile-friendly test flags this immediately, and Google may demote the page.
Charset and language attributes affect how characters render and which language Google associates with the page. UTF-8 charset has been the standard for over a decade. The lang attribute on the html element (not as a meta tag) drives international SEO targeting.
Open Graph and Twitter Card tags
When users share your link on Facebook, LinkedIn, Slack, Discord, WhatsApp, or any other major platform, those services pull the Open Graph (og:*) tags to render the link preview card. Without og:title, og:description, and og:image, the shared link appears as plain text or worse, falls back to whatever scraped content the platform finds.
og:image is the highest-impact field. The recommended size is 1200x630 pixels for landscape (Facebook, LinkedIn, Slack) and at least 1200px wide for safe scaling across all platforms. Use an absolute https URL.
Twitter Card (twitter:card) is a separate tag for the Twitter/X link card style: summary, summary_large_image, app, or player. Most modern sites use summary_large_image. Twitter falls back to Open Graph when Twitter Card is missing, so og:* coverage usually gets you most of the way.
The H1 tag: technically not a meta tag, but checked here
H1 is not in the head, but it is the most important on-page element after the title. Every page should have exactly one H1 clearly stating the page's primary topic. The analyzer reports the H1 alongside meta tags because diagnosing missing H1s during a meta audit is faster than running a separate heading analysis.
For a deeper heading audit including H2 to H6 hierarchy, use our Heading Structure Analyzer. The meta tag analyzer flags missing H1 only.
How to use the results
Start with the issue list at the top. Anything flagged critical (missing title, noindex set, etc.) needs immediate fixing. Warnings are next priority and usually capture meaningful CTR or rich-result eligibility issues.
Export the JSON or CSV output to share with developers or content teams. The Markdown export works well for a quick audit summary document. Re-run after deploying fixes to confirm the changes landed correctly. Common gotcha: CMS plugins overwriting your manually set tags on save. The analyzer catches that immediately.