Meta Title and Description

Write metadata that fits, with the character count live as you type. No account, no payment, and nothing leaves your browser.

Your metadata

Nothing leaves your browser. There is nothing to submit.

Page title

0 of 30 to 60 characters0 px of 580

Meta description

0 of 70 to 155 characters0 px of 920

Page URL, optionalOnly drawn above the title in the preview. It is not measured and it is not sent anywhere.

How this looks in a result

Cut where the estimate says a desktop result stops drawing it

nicklaunches.com

Nick Launches: a weekly launch directory for indie builders

Submit your product, get reviewed by a human, and launch in a weekly cycle where builders find and upvote it.

Estimated against Arial, the face a desktop result is set in, at 580 px for a title and 920 pxfor a two line description. Both are measurements of Google's desktop layout, not numbers it publishes, and a phone is narrower.

What the numbers mean

Two readings of the same line, and they can disagree

The character target is 30 to 60 for a title and 70 to 155 for a description. Those are the same two bands our Site Audit fails a page against, so a title you write here is a title that audit passes. Under the floor a title is usually one word that ranks for nothing, and a description under it is one Google rewrites out of your page body, which is the real loss: not the tag, but control of what the result says.

The pixel figure is the other reading. A result page cuts by width, not by characters, and sixty is and sixty Ws are not the same object. We estimate against Arial, the face a desktop result is set in, and cut at 580 px for a title and 920 px for a two line description. Both are measurements of Google's desktop layout rather than numbers it publishes, and a phone is narrower.

So a wide description can sit inside the character band and still be cut in the preview. That is not a fault in either reading: the band is what to write towards, and the preview is what the result will actually show. Where they disagree, believe the preview.

The estimate comes from a fixed table of letter widths rather than from measuring the text in your browser, so it is the same number on every machine, and it is checked by unit tests rather than by a screenshot. Nothing on this page is fetched, stored or sent: there is no server call behind any of it.