Nothing in a result entry is fixed. When a query runs, the engine picks a URL and then builds the title link and the passage beneath it for that query, that device and that searcher. A page supplies two inputs: <title> and <meta name="description">. The favicon, the site name line and the › separators in the URL come from the engine's own index.
So this preview shows one plausible rendering, not a guarantee. The counters compare what you typed against the two figures usually quoted for desktop — roughly 60 characters of title and 155 of description. Those are approximations for average-width Latin text rather than limits. Truncation happens on rendered pixel width, so a 58-character title of narrow letters can survive while a 52-character one of wide capitals loses its last word. Either field is also rewritten when page text or anchor text fits the query better.
The title is a genuine ranking input: its words are read. The description is not, but it is the sentence a searcher reads before deciding whether to click.
| Element | Surfaces as | If absent or weak |
|---|---|---|
<title> | The clickable line, the browser tab and the default bookmark name | The engine substitutes prominent on-page text, often the largest heading, or anchor text from inbound links. |
<meta name="description"> | The grey passage under the title | The engine composes a passage from surrounding body text, biased towards the query terms. |
Each field gets a pill and a bar. The bar turns amber past roughly 85% of the guide and red beyond it. A pill is red at zero characters rather than green, because an empty title means the engine writes its own from whatever it finds, and an empty description means the visible passage is whatever sentence sits nearest the query terms.
For a product page, Trail Running Shoes — Grip, Cushion and Fit | Northline sits just under the 60-character guide and leads with the topic rather than the company. The matching description, Compare trail running shoes by grip, cushioning and fit. Filter by terrain, drop and width., fits at desktop width, while on a narrow viewport the closing clause clips first — which is why the load-bearing words sit at the front of both fields. Swap in Northline | Shop and the preview looks tidier while discarding the only words that distinguish this page from the other four hundred on the domain.
Northline | Best Running Shoes | Blog keeps the part that identifies nobody and loses the part that described the page.No. There is no character limit; the constraint is the width of the container the engine draws, which 60 characters of average Latin text approximates. A longer title is not penalised, only clipped.
No. It uses it when it suits the query and falls back to a passage composed from page text. A description that matches the page is more likely to be kept, but retention is never assured.
Not as a rule. The title occupies one line and the description another, so restating the first spends the only space available for a concrete detail.
It was generated for another query, another device and possibly another version of the page. Rewrites, generated passages, query bolding and injected dates all happen outside the page.