The result you write is not the result they see
A snippet preview shows what you intend. What appears in search is decided by the engine, and it rewrites titles and descriptions frequently — usually when it finds text on the page that matches the query better than what you wrote.
That is not a malfunction to work around. One page can rank for dozens of queries, and no single fixed title is the best answer to all of them. A snippet assembled from the exact paragraph that answers a specific search is often better than anything you could have written months earlier.
What you control is the starting point and the raw material. The [msm_tool slug="serp-simulator"] shows the starting point: the URL line, the linked headline, the description beneath, in the desktop layout.
Where the cut actually happens
Truncation is by pixel width, not character count. A title full of wide characters cuts sooner than one of narrow ones, which is why two titles of identical length can behave differently.
The rough guides — around sixty characters for a title, around a hundred and fifty-five for a description — are useful targets and not rules. Mobile results stack differently and cut off sooner, and most of your audience is on a phone.
The preview here measures nothing and warns about nothing deliberately, so judge by eye against the width of the box, which is close to the real one. Reading a truncation warning is a poor substitute for seeing the thing.
Overrunning is not penalised. It is simply cut, and a title ending mid-word looks careless in a list where everything else is complete.
Front-load everything
Since the end may vanish, put the substance at the start. Write the title, then read only the first forty characters and ask whether they still say something useful. Do the same with the first hundred of the description.
This is why brand-first titles waste space. Acme Ltd | Professional Services | Contact spends every visible character on things the reader either knows or does not care about. Put the brand at the end, where losing it costs nothing.
Boilerplate suffixes have the same problem at scale. A site-wide – Best Tools Online appended to every title consumes the same characters on every page and differentiates none of them.
Writing a result that gets chosen
- Answer the query in the title. Someone who searched a question wants to see the answer exists here.
- Be specific. A number, a year, a version or a constraint signals a real page rather than a category of pages.
- Differentiate from the neighbours. Search your own term and read the ten results as a set. What does yours offer that the others do not say?
- Let matched words appear naturally. Terms matching the query are shown in bold, which draws the eye — a visual effect, not a ranking one.
- Do not oversell. A promise the page does not keep buys one click and loses the reader immediately, which is visible in your own analytics.
The URL line is part of the result
It sits above the title, often shown as a breadcrumb rather than a raw address, and readers use it to judge whether the page is what it claims.
A short readable path helps. A long one full of identifiers, dates or encoded characters looks machine-generated and adds nothing. It is also the one element you cannot fix later without a redirect, so it is worth deciding carefully the first time.
How to use the preview well
- Draft three titles, not one. Look at them stacked and pick the one that reads best cold.
- Compare against the live results. Open the real search page next to the preview. Yours has to win against those specific nine, not in the abstract.
- Check the truncated version. Cover the tail with your hand. Is the visible part a complete thought?
- Check the page can support a rewrite. Since the engine may build its own snippet from your content, make sure a clear answering paragraph exists near the top to build from.
- Revisit the pages that underperform. High impressions and low clicks in Search Console is the exact signal that a title is failing.
The preview runs entirely in your browser. Nothing you type is sent anywhere or stored on this site.