Vutral
How to use this tool

Bulk Meta Tag Analyzer for Title & Description

How to use the bulk meta tag analyzer

Back to the tool

Each URL is fetched once, and the two tags that write your search result come back measured in characters and in pixels.

  1. 01

    Enter the URLs to check

    Single mode checks one address and runs on Enter. Switch to Bulk to paste a list, one URL per line, up to 30 per run. Put pages that compete with each other in the same run: a repeated title is only found among the URLs checked together, so five sibling category pages tell you what no single URL can.

  2. 02

    Select which tags to read in Data checked

    The two are the two lines of one search result: Title is the blue heading, Meta description the grey paragraph under it, and All ticks both. Each tag brings three columns rather than one: the text it declares, then that text in characters and in pixels. They arrive together because a column that only copies the line back answers nothing.

  3. 03

    Read the two lengths beside each tag

    Every number is judged against its own range, so the two can disagree, and that disagreement is why the pixel column exists. A 50-character title sits inside ⁦30–60⁩ and can still be 610 px wide, past the point Google trims. Green is inside the range; an arrow means outside. — means nothing was measured, never a length of zero.

  4. 04

    Inspect a row and export the results

    View draws each range around its value and adds what the table has no room for: a second tag on the page, and a title another URL in this run already uses. Copy table copies the rows tab-separated; Export CSV writes them to a file. Both keep the four numbers sortable and name the range in the heading, chars (⁦30–60⁩).

How to read the title and meta description report

A row reads left to right: the address checked, where it landed, then each tag and its two measurements.

Result table columns

URL
The address exactly as it was checked — after normalization, not always what you typed.
Resolved URL
Where the request ended. Redirects are followed first and the tags are read from that final page, so a row can report a title you never wrote for the address you gave.
Title
The <title> text, exactly as declared. Every tag is kept but only the first is measured, because only the first is read. declared but empty means a tag with nothing inside, a different fault from having no tag at all.
Meta description
The text of <meta name="description">, under the same rules. Having none is not an error: Google then builds the snippet from the page, and often that matches the query better.
chars
Length in characters, counted as a person counts them: an emoji or an accented letter is one. One such column per tag; in the export the heading tells them apart by naming the range, chars (⁦30–60⁩) for the title.
px
Width in Google desktop results, measured in a fixed font rather than your site’s. Google cuts by width, not by count, so this is the closer estimate, and the only one that notices WWW is four times wider than iii.
Result
Whether the row finished, is still running, or stopped on an error. It says nothing about the tags themselves.
Actions
View opens the detail panel for that row; Retry appears instead when the request never got through.

Detail panel verdicts

No <title> — Google writes the result heading itself.
The most serious finding here. Without a title tag the first line of your result is written for you from whatever page text fits the query, so the one line everyone sees is the one you did not choose.
The title tag holds no text — Google writes the heading itself.
The tag exists with nothing between its halves, usually a template that rendered before its content arrived. Counted as no title, and no length is measured for it.
No meta description — Google builds the snippet from the page text.
A note, not an error, and deliberately so. Leaving it out is legitimate on pages whose content answers many different queries, and the snippet Google writes then follows the query instead of a fixed sentence.
2 title tags — only the first is read.
Every tag found is listed so you can see which one wins. Only the first is read by browsers and by Google, so only the first is measured.
64 characters — Google cuts past about 60, measured in pixels, so treat this as an estimate.
Counted in characters as an approximation of the cut Google makes in pixels. Treat the pixel line beside it as the closer answer.
29 characters — under 30 leaves no room for both keyword and context.
Not a penalty. Below this mark a title lacks room for both the page’s subject and the context that identifies it as the right page.
610 px wide — Google cuts past about 580 px, so the tail is likely trimmed.
The sentence the pixel column exists for: a title inside the character range can still be trimmed. The description uses the same sentence with its own wider threshold.
240 px wide — under 285 px it uses less room than the result gives it.
Nothing is wrong with the page; the result simply uses less of the row than it was given. Worth a look on pages whose titles are all short by template.
Another URL in this run has the same title.
Compared only against the other URLs in this run, so the run you assemble decides what this can find. Two pages sharing a title are two pages asking to be told apart.
One title tag, length in range.
One tag, every measurement inside its range, and no duplicate in the run. Never shown alongside a warning.

Dedicated single-tag checkers

Both tags above are also tools of their own: the same fetch, one tag, and a guide that goes further than this page does.