Search engines truncate on rendered pixel width, not character count, so this is an approximation — a title of capital letters truncates earlier than the same count in lower case. Treat the ranges as conventions rather than limits. And what is shown here is what you asked for: engines frequently rewrite titles and descriptions, so the preview is your proposal rather than a prediction.
Renders your proposed title, URL and description as a search result, with length checks alongside.
Everything happens in the page — nothing is uploaded, nothing is stored, and no address is required.
Replace the example with your own text. The counts update as you type, and the panel shows the result rather than a score.
The defaults are examples chosen to make the shape obvious. They are not recommendations.
Search engines truncate on rendered pixel width, not character count, so this is an approximation — a title of capital letters truncates earlier than the same count in lower case. Treat the ranges as conventions rather than limits. And what is shown here is what you asked for: engines frequently rewrite titles and descriptions, so the preview is your proposal rather than a prediction.
The ranges are conventions rather than rules, and being outside one is not automatically wrong.
What matters is whether the meaning survives truncation — check that the opening still says what the page is about, because that part always survives.
No. It runs in the page, nothing is sent anywhere, and there is no follow-up.
They are character counts. Truncation happens on rendered pixel width, so treat them as an approximation.
No. It works on the text you paste, and makes no requests.
Half an hour on your own figures, and an honest answer about the parts Treepie does not improve.