New 58+ tools are now available — built to keep your workflow moving.

Meta Tag Analyzer: Check a Page Before You Publish

Paste page source and check title, meta description, canonical, robots, viewport, H1 count and Open Graph tags at once. Runs in your browser.

A Admin 8 min read

A meta tag analyzer reads the HTML you paste and reports on the tags that decide how a page appears in search results and social shares: title, meta description, canonical link, robots directives, viewport, charset, html lang, H1 count, and the Open Graph and Twitter tags. It works from source only. It does not fetch a URL.

That limitation is deliberate. A tool that fetches arbitrary URLs can be pointed at internal addresses, and the page it sees may differ from the source you pasted. Reading source is predictable: what you paste is exactly what is checked. The trade-off is that you have to copy the source yourself, and tags added later by JavaScript will not be visible.

What the analyzer checks

Item What is reported Warning thresholds
Title Presence and character length Empty, under 30, or over 60 characters
Meta description Presence and character length Empty, under 70, or over 160 characters
Canonical link Presence and target Missing
Meta robots Directives found noindex, nofollow
Viewport Presence Missing
Charset Declared encoding Reported for review
html lang Language attribute Reported for review
H1 count Number of H1 tags Zero, or more than one
Open Graph og:title, og:description, og:image, og:url, og:type Missing image or title
Twitter/X twitter:card, twitter:title, twitter:description, twitter:image Missing card

Issues are graded CRITICAL, WARNING or NOTICE, so you can fix the things that actually block a page from appearing before polishing the rest.

How to analyze a page

  1. Open the meta tag analyzer.
  2. In your browser, open the page and view its source (Ctrl + U on Windows and Linux, Cmd + Option + U on macOS).
  3. Copy everything from <head> to </head>. You can also paste a single tag to test it on its own.
  4. Paste it into the box and press Run.
  5. Read the report from the top: fix CRITICAL issues first, then WARNING, then NOTICE.

The parse runs in your browser. Nothing is uploaded and no request is made to the page you are checking.

Reading the report

Title. The title is the headline of the search result and the strongest on-page text signal. Under 30 characters usually wastes space; over 60 is likely to be truncated on desktop. These are display guidelines, not hard limits, and Google may rewrite a title it considers poor.

Meta description. Google may use the description as the snippet, though it often generates one from page text. The 70 to 160 range is a practical target. A missing description is not fatal, but it gives up control over the snippet.

Canonical. A missing canonical is a warning, not an error. It matters most when the same content is reachable through several URLs: with and without www, with tracking parameters, or through different protocols. The canonical tag builder covers those variants.

Meta robots. noindex is critical: the page cannot appear in search at all. nofollow is a warning: links on the page pass no authority. An empty robots tag means indexable and followable by default.

Viewport. Without a viewport tag, mobile browsers assume a desktop width and the page is evaluated and displayed accordingly. This is one of the cheapest fixes in the list.

H1 count. Zero H1s is a warning. More than one is a notice, because multiple H1s are legal HTML but a single clear heading is easier to read and reason about.

Open Graph and Twitter tags. These do not affect search ranking, but they decide whether a shared link shows a title, description and image or a bare URL. og:image is the one to prioritise: without it, most platforms show no preview image.

Common problems and fixes

The analyzer says there is no title, but the page has one. The title may be injected by JavaScript after load. View-source shows the server response, not the rendered DOM. Copy the rendered HTML from the browser's element inspector if you need to check client-side tags — but remember that crawlers may not see them either.

The title is the wrong length because the site name is appended. Many CMSs add | Site Name. Either shorten the page title or configure the separator and site name so the total stays within range. The analyzer counts characters, including spaces and punctuation.

The meta description is empty. Some themes only output a description on certain templates. Add one per page or set a sensible fallback, but avoid duplicating the same description across every page.

Canonical points at a different domain. A staging canonical accidentally left in production tells search engines to index the staging URL instead. Check the host, not just the path.

The page is noindex and should not be. Check for a stray noindex in the CMS, a plugin, or a header set by the server. The meta tag analyzer sees only tags in the pasted source; an X-Robots-Tag HTTP header is invisible here.

There are two H1s because the logo is an H1. Change the logo to a link or a div and keep one H1 for the page title. Multiple H1s will not break anything, but a clean heading outline is easier to maintain.

The social preview is blank. Check og:image. It needs an absolute URL, a sensible aspect ratio and a file the platform can fetch publicly. A relative path will not work on most platforms.

The analyzer misses a tag added by JavaScript. That is expected. It parses the source you pasted. For tags that only exist after rendering, inspect the live DOM and accept that some crawlers will not see them.

Tips for cleaner tags

  • Fix the critical issues first. A noindex on a page you want indexed outweighs every character-count warning.
  • Write the title for a person, then check the length. Keyword-stuffed titles read badly and are more likely to be rewritten by search engines.
  • Write one description per page. A template fallback is better than nothing, but a unique description is better than a fallback.
  • Use absolute URLs for canonical and social images. Relative URLs are interpreted differently by different consumers, and some reject them.
  • Keep one canonical per page. Two canonical tags pointing at different URLs leave the crawler to choose.
  • Check the tags after a deploy, not only in the editor. A theme or plugin can remove them at render time.
  • Remember the header. Robots directives can also arrive as an X-Robots-Tag header, which this source-based tool cannot see.

Tags, robots.txt and sitemaps

The analyzer covers the page itself. Two other files cover the site around it:

  • The robots.txt generator builds crawl rules. Keep noindex pages crawlable if you want the directive to be seen.
  • The XML sitemap generator lists the URLs you want indexed. Only include pages that return 200, are canonical and are not noindex.
  • The canonical tag builder decides which URL variant should be indexed when several serve the same content.

Used together, they answer three separate questions: what may be crawled, what should be indexed, and how each page describes itself.

Frequently asked questions

Is the meta tag analyzer free?

Yes. It is free and requires no account.

Does it fetch my URL?

No. It reads the source you paste. It never requests a URL, which also means it cannot be used to reach an internal address.

Why is a tag missing that I can see in the browser?

The tag was probably added by JavaScript after the page loaded. The analyzer sees the source you pasted, not the rendered DOM. Some crawlers also miss client-side tags.

What is a good title length?

Around 30 to 60 characters. Under 30 often leaves space unused; over 60 is likely to be truncated in search results. Google may rewrite titles it considers low quality, so clarity matters more than hitting an exact count.

What is a good meta description length?

Around 70 to 160 characters. Google may ignore it and generate a snippet from page text, but a well-written description is still used often enough to be worth writing.

Does it check Open Graph and Twitter tags?

Yes. It checks og:title, og:description, og:image, og:url, og:type, and the four common Twitter card tags.

Bottom line

Most meta tag problems are invisible until a page is shared or a result looks wrong. Pasting the source into an analyzer catches the missing description, the stray noindex, the truncated title and the absent social image before anyone else sees them. Start with the meta tag analyzer, then use the canonical tag builder and the robots.txt generator to settle the site-level rules.

Was this helpful? Leave a like or tell us below.

Comments (0)

Be the first to share feedback on this post.

Related posts

View all