Free SERP Snippet Checker.
Google truncates a title and description by width, not by character count, so the only accurate check is to measure the rendered text in pixels. A desktop title is cut at roughly 600 pixels and a description at roughly 920, which is about 60 and 155 characters in average prose and far fewer in wide capitals. This measures what you type as a results page would draw it, and checks whether the line carries the keyword, opens with an answer, and says where you are.
Free, no sign up, no email. It runs in your browser, so nothing you type is sent to us or to anyone else.
A line follows its shape and updates as you change the fields above, until you type in it. Then it is yours, and picking a shape again hands it back. Nothing here writes copy; it measures what you give it.
- Title will be cut off
- Description will be cut off
- Keyword in the title, near the front
- Keyword in the description
- Description answers before it argues
- Carries a location
- Brand in the title
- Says something specific
The widths are the ones Google has been observed to truncate at, not a promise: they move, they differ by query, and Google rewrites the description on most results anyway. Nothing you type here is sent anywhere.
How this works.
Google truncates by width, not by character count
Every tool that tells you a title is fine at 60 characters is measuring the wrong thing. A results page fits text into a width, and characters are not the same width: "Illinois" and "WWWWWWWW" are both eight characters and nowhere near the same size on screen. A title of narrow letters can run well past 60 and still fit; a title of capitals and wide letters can be cut at 52.
So this measures the rendered width. The text is drawn into a canvas in the face and size Google draws with, and what comes back is the number of pixels it actually occupies. That is the same method a browser uses to lay the page out, which is why it agrees with what you see rather than with a character count.
What the limits are, and why they are approximate
A desktop title is generally cut around 600 pixels and a description around 920, which works out near 60 and 155 characters in ordinary prose. Mobile gives a title more room and wraps it over more lines. These are the widths Google has been observed to use, not numbers Google publishes, and they move.
There is a larger caveat worth knowing before you spend an afternoon on a description. Google rewrites the description on the majority of results, choosing a passage from the page that matches the query instead. Writing a good one still matters, because it is what gets used when it does fit the query, and because the exercise forces you to say what the page is for. But it is an input, not an instruction.
Why this is a checker and not a generator
There is no model behind this, and no subscription to one. Nothing running in your browser can write copy, and a tool that calls itself a generator without a model behind it is picking from three templates and hoping you do not notice. So this checks rather than writes: it measures what you give it, and tells you what the line is doing.
The shapes are still here, because scaffolding is useful when you are staring at an empty field. Treat them as a starting position rather than an answer: each one drops a structure into the box for you to rewrite. The one field that is not optional is the specific, because a title without something only you can say is the title your competitors already have, and no structure saves it.
Answering before arguing, and saying where you are
The check for whether the description opens with an answer is there because of where search is going. An assistant summarising a page lifts the passage that answers the question, and a description that opens "Performance marketing is…" gives it something to lift. One that opens "We are a leading agency…" does not.
The location check is the same idea for local search. A place in the title or the description is one of the plainer signals that a page is relevant to somebody searching nearby, and it costs a few characters. Neither check is a rule. They are both things worth knowing you have skipped.
Questions we get asked.
How long should a meta title be?
- Around 600 pixels on desktop, which lands near 60 characters in ordinary prose and fewer in wide capitals. Counting characters will be roughly right most of the time and wrong exactly when the title is full of capitals or wide letters, which is when you most need to know.
How long should a meta description be?
- Around 920 pixels, near 155 characters in ordinary prose. Shorter is not a problem in itself: a description that answers the query in 120 characters beats one padded to 155.
Why measure pixels instead of characters?
- Because that is what Google does. It fits the text into a width, so two titles of identical length can truncate differently depending on which letters they use. Measuring the rendered width is the only check that agrees with what appears on the results page.
Does Google always use the description I write?
- No, and on most results it does not. Google frequently replaces the description with a passage from the page that matches the query. Writing a good one still matters, because it is used when it does fit and because the exercise makes you decide what the page is for, but treat it as an input rather than an instruction.
Does this generate titles, or just check them?
- It checks. It will drop a structure into the field to get you started, and it measures and scores whatever ends up there, but it does not write copy and does not claim to: there is no model behind it and everything runs in your browser. Anything advertised as an AI generator without a model behind it is choosing from templates.
Is anything I type here stored or sent anywhere?
- No. The measuring, the shapes and the preview all run in your browser. There is no server behind this tool, no sign up and no email gate.
Ready to move the numbers?
Let us talk about your current goals, what is working, what is not, and where the biggest opportunities may be.