Tool AT-W42REV. 2026-A

Snippet preview: is your title cut off on Google?

Google shortens titles and descriptions by width, not by characters. On desktop, about 600 pixels is usual for the title and about 920 for the description; depending on the letters, that is roughly 50 to 60 and 130 to 145 characters. The preview measures your text in Arial, as Google sets it, shortens it for desktop and mobile, and checks a whole list if you wish. What Google then actually shows for a search is for Google to decide.

  • free
  • no sign-up
  • measures in the browser

Enter title and description, read off the preview

Preview · title and description on Google

Google decides the title and snippet itself and gives no fixed widths. The preview shows what fits into the usual width, not what Google actually displays for a particular search.

Step 1Title, description and address

Pre-filled with this page. Replace the texts with your own; the preview recalculates with every input.

Step 2Optional: search term and website name

With a search term, the preview sets matches in bold as Google does and checks whether all the words appear in the visible part.

The name above the title. Google takes it from the structured data of the home page; if left blank, the domain is shown here.

Result

Traffic light: open

Enter a title.

How the entry might look

Desktop

Title 600 px on one line, description 920 px

Phone

Phone 375 px wide: 2 lines of 343 px each

Notes

    Measured in Arial without kerning: title 20 px, description 14 px. Character widths from arial.ttf, the same as in our checking script for our own pages. As of 14 November 2026. Whether Google shows your text like this is decided anew by Google for every search; the SpotLens website check provides an overall picture of your website.

    Measures in your browser. Nothing is sent or stored.

    Google shortens by pixels, not by characters

    In Arial, the typeface in which Google sets the results list on desktop, a “W” is 1933 units wide and an “i” only 455. So 135 small “i”s fit into the 600 pixels of a title line, but only 31 capital “W”s. Anyone who counts characters shortens in the wrong place. Three examples show how far apart the two can be: the shortest title is the widest, by 160 pixels more than the longest.

    LIMIT 600 PXLichtplanung für Büro und Lager in Rodewisch | Elektro Muster61 CHARACTERS · 555 PX · FITSHeizungswartung in Plauen und Zwickau | Muster Haustechnik58 CHARACTERS · 554 PX · FITSWLAN-MESSUNG UND WARTUNG IM VOGTLAND | AUREUM TECHNOLOGY56 CHARACTERS · 715 PX · GETS SHORTENED

    Fig. 1 · Width in 20 px Arial, scale 4 : 5. Hatched: the part that Google cuts off on desktop. What stays visible is “WLAN-MESSUNG UND WARTUNG IM VOGTLAND | AUREUM ...”.

    The widths the preview works with
    ViewElementFontWidthLinesOrigin
    DesktopTitle20 px600 px1usual value of preview tools, a few give 580 px
    DesktopDescription14 px920 px2observed over years; we also check our own pages against this limit
    PhoneTitle20 px343 px2Phone 375 px wide with 16 px margin, font size assumed
    PhoneDescription14 px343 px2gives about 650 to 686 px, close to the usual 680 px

    Google does not publish any of these figures. They are observed values, as of 14 November 2026; on desktop Google shows the description on two lines, and it is shortened by total width.

    How the preview measures

    Your browser measures the text with the canvas function measureText in Arial and calculates without kerning. This gives exactly the advance widths from the font file arial.ttf, which we also use to check the descriptions of our own pages. If Arial is missing on the device, for example on many Android phones, the preview carries on with the same table. It shortens at the last whole word boundary, and Google adds “ ...” after it. On mobile, the preview wraps the text into lines just as the phone would.

    Two things shift the cut-off in the real result by a few characters. Google sets search words in bold in the snippet, and bold letters are wider. And a date before the description, which Google often shows for guides, costs about 92 pixels; there is a tick box for this in the preview. If you are just under the limit, it is best to leave a word of room.

    Google often writes titles and descriptions itself

    What is in your title element is a suggestion. By its own guidance, Google generates the title link fully automatically and draws on several sources: the title element, the main heading, other headings, og:title, link text pointing to the page, and the structured data of the website (Google, as of 10.12.2025). There is no length limit for the title element itself; it is only shortened in the display, usually to the width of the device.

    Google itself once put a figure on how often it replaces the title. After a change in August 2021, the displayed title came from the title element in about 87 per cent of cases, previously in about 80 per cent (Google blog, 17.09.2021). Roughly speaking, then, Google shows a different title for one result in eight. Google names the reasons in its guidance and on its blog; most of them can be checked in advance.

    Why Google replaces titles, and which of those reasons the preview detects
    Reason according to GoogleExampleThe preview checks
    half-empty„| Muster GmbH"separator at the start or end, title consisting only of the website name
    outdated“Prices 2024” in 2026year before the current year
    too longtitle running beyond the linewidth over 600 px
    stuffed with search terms“Heating Plauen, heating Zwickau, heating Reichenbach”the same word three times or more
    boilerplate fragmentsmany pages with almost the same titlein list mode: identical titles
    generic“Home page”, “Home”very short title
    inaccurate, another language, no clear main headingtitle does not match the contentnot possible without the page itself; the SpotLens website check sees this

    The description is freer still

    Google builds the snippet under the title mainly from the content of the page. It uses the meta description when it describes the page more accurately than the text itself (Google, as of 20.04.2026). Behind this lies an old finding of search research: snippets that match the query let people recognise faster and more reliably whether a result is any good Tombros and Sanderson 1998. The same page therefore often shows two different snippets for two searches.

    Your description is still the best lever. Google advises a separate description for each page, no keyword lists and not too brief; the preview reports all three cases, with “short” meaning under 460 pixels. If you want to keep individual paragraphs out of the snippet, mark them with data-nosnippet; max-snippet limits the length (Google, as of 24.03.2026). Google chooses the name above the title automatically; you state your preferred name with WebSite data on the home page, and og:site_name, titles and headings count as well (Google, as of 10.12.2025).

    What a good entry achieves, and what it does not

    The preview’s notes rest on 15 papers from search research; the complete list with checking notes is further down. The most important finding is an uncomfortable one: position comes first in determining clicks.

    • Position counts first. In an experiment with secretly swapped results, students chose the top link even when it was a poorer match Pan et al. 2007. Click behaviour at the top of the list is best explained by a model in which users read from top to bottom and stop at the first worthwhile result Craswell et al. 2008, and placement shaped the judgement more strongly than the text of the snippets Bar-Ilan et al. 2008. A better title therefore does not bring an entry forward from position eight.
    • At the same position, the entry makes the difference. In the click data of a large search engine, even simple features had an effect: whether all the search words appear, how readable the snippet is and how long the address is Clarke et al. 2007. More appealing titles were preferred beyond the position effect Yue et al. 2010. That is why the preview checks the search term in the visible part and sets it in bold.
    • The name of the source has an effect. Of three credibility signals, only the reputation of the source had an effect of its own on the choice Unkel and Haas 2017. A well-known company name therefore belongs at the start or end of the title, as Google recommends.
    • Longer is not automatically better. More text in the snippet helped with information searches and got in the way when someone wanted to reach a specific page Cutrell and Guan 2007. Longer snippets were felt to be more informative and were clicked more often, but accuracy did not improve Maxwell et al. 2017. For guides and service pages the full width is worthwhile; for the home page and contact page a clear, short description is enough.

    It gets tighter on mobile

    On small screens, test participants found it harder to draw information from the results list Kim et al. 2014, and depending on the size of the device they searched differently, scrolling a lot on the smallest Kim et al. 2015. Two to three lines of snippet were enough on mobile; longer ones cost time without better results Kim et al. 2017. A single line, on the other hand, gave too little information Sachse 2019. The preview therefore calculates mobile with two lines. In the description of this page, the visible part there ends after “in pixels, for desktop and”; nobody sees what comes after that on a phone.

    Why the preview does not promise a click rate

    Clicks are a biased signal. They are no good as an absolute verdict on a result, only as a comparison between results Joachims et al. 2007. A review of 41 eye-tracking studies found no consistent results for many influences on gaze behaviour Lewandowski and Kammerer 2020. A figure such as “20 per cent more clicks” would therefore be a guess. How many clicks to expect at which position is estimated by the click potential calculator from your own Search Console data.

    How to write titles and descriptions

    1. One page, one question. The title first says what the page is about, using the term people use to search for you. The website name comes last, separated by a vertical bar or hyphen.
    2. Get the title under 600 pixels. Capital letters and long compound words eat up width. Filler words such as “Welcome to” go first.
    3. Write the description as an answer. What does the reader get on the page? One whole sentence, not a list. The key message belongs in the front part, because on mobile the text ends after two lines.
    4. A phone number only if it stays fully visible. Nobody can call a half-cut-off number; in that case the content takes priority.
    5. Every page gets its own texts. Check the whole website in list mode: identical titles and descriptions stand out there at once.
    6. Then keep watching. Google only picks up changes after its next visit to the page. Whether your text appears is shown by the search itself; Search Console shows the clicks.

    Where the preview stops

    • An approximation, not a replica. Google keeps changing the results list and chooses title and snippet for each search. The preview shows what fits into the usual width.
    • Widths are observed values. Bold type, a date, other fonts on Android and narrower or wider phones shift the cut-off by a few characters.
    • No judgement on the content. Whether the page matches the search and is in the index at all is something the preview cannot see.

    The overall picture of your website, right down to visibility in AI searches, is provided by the SpotLens website check. Individual questions are answered by the other tools under SEO and visibility, for example how a shared link looks on WhatsApp or LinkedIn in the link preview check. If your page is not found at all, the guide Website not found on Google helps. How we build titles, descriptions and page structure for businesses in the region is described under SEO in Rodewisch.

    Using this tool from an AI assistant

    Assistants such as Claude or ChatGPT that speak the Model Context Protocol (MCP) can call this page’s calculation directly instead of rebuilding it. The server is public, needs no sign-in and stores nothing. The answer always includes the link to this page, the date of the data and the limits of the result.

    Endpoint
    https://aureum-tech.com/mcp
    Tool
    werkzeug_snippet_vorschau
    Transport
    Streamable HTTP, read-only
    Inputs
    NameRequiredMeaning
    titelnoSingle check: content of the <title> element. Give either titel or seiten.
    beschreibungnoSingle check: content of <meta name="description">. Empty if the page has none.
    urlnoSingle check: address of the page; the breadcrumb is built from it (“https://host › path”).
    suchbegriffnoOptional: search term the page should be found for. Checks whether its words appear in the title and description.
    websitenamenoOptional: name of the website or company, as Google shows it above the title.
    datumnoOptional: date that Google puts before the description (e.g. for guides), in the form DD.MM.YYYY. It costs width.
    seitennoList check: up to 200 pages with url, titel, beschreibung. Also reports duplicate titles and descriptions.

    Questions where an assistant should call it

    • “Will my page title ‘Heizung und Sanitär in Plauen – Notdienst, Wartung, Badsanierung | Müller’ be cut off on Google?”
    • “Is this meta description too long for Google, and what does it look like on mobile?”
    • “Check these 30 titles and descriptions from my Screaming Frog export: which are too wide or duplicated?”
    • “Is my search term ‘IT-Service Vogtland’ in the visible part of the title and description?”

    How the connection works and what MCP can do in your own business is explained on the page about MCP integrations.

    Common questions about title and meta description

    How long can a page title be on Google?

    On desktop, Google shows the title on one line of about 600 pixels, set in 20 px Arial. Depending on the letters, that is roughly 50 to 60 characters: 135 narrow lowercase letters such as “i” fit in, but only 31 capital “W”s. According to Google, there is no length limit for the title element itself; the title is only shortened in the display, usually to the width of the device.

    How long can the meta description be?

    On desktop, a width of about 920 pixels in 14 px Arial is taken as the limit, which is roughly 130 to 145 characters. On mobile it ends sooner: we work with two lines of 343 pixels, so about three quarters of that at most. Google gives no figure itself and shortens as needed. More important than the full width is putting the key message first.

    Why does Google show a different title from the one I entered?

    Google generates the title link fully automatically and, besides the title element, also draws on headings, the Open Graph title and link text. It mainly replaces half-empty, outdated, inaccurate and keyword-stuffed titles, as well as near-identical titles across many pages. By Google’s own account, in September 2021 the displayed title came from the title element in about 87 per cent of cases; Google gives no more recent figures.

    Why does Google not show my meta description?

    According to its own guidance, Google builds the snippet mainly from the content of the page, matched to the particular search. Google uses the meta description when it describes the page more accurately than the text itself. That is why the same page can show two different snippets for two searches. A separate, accurate description for each page raises the chance that your text appears.

    Does Google count characters or pixels?

    Pixels. In Arial, a “W” is more than four times as wide as an “i”. The title “Lichtplanung für Büro und Lager in Rodewisch | Elektro Muster” has 61 characters and 555 pixels, so it fits. “WLAN-MESSUNG UND WARTUNG IM VOGTLAND | AUREUM TECHNOLOGY” has only 56 characters, but in capitals it is 715 pixels wide and gets shortened.

    Can I check all the pages of my website at once?

    Yes, in list mode below the preview. Paste in a list with address, title and description, or choose a CSV file, for example an export from Screaming Frog. For each page the table shows the width, a traffic-light rating and notes, and it reports duplicate titles and descriptions. You can save the result as CSV; the file is only read in your browser.

    Where does the snippet preview stop?

    It measures widths and checks the reasons why Google rewrites. It cannot see whether a title matches the content, whether the page is found at all, or which snippet Google picks for a search. We are happy to write titles and descriptions for your most important pages with you, from Rodewisch for the whole Vogtland; the overall picture of the website is provided by the SpotLens website check.

    What the tool is based on

    The guide values and notes above are based on these 15 scientific papers. Each one has been checked via its DOI or the publisher’s page (most recently on 14 November 2026): it exists, it has not been retracted, and its findings still hold for this question today.

    1. Clarke, C. L. A.; Agichtein, E.; Dumais, S. et al. (2007): The influence of caption features on clickthrough patterns in web search. Proceedings of the 30th ACM SIGIR Conference (SIGIR '07), pp. 135–142

      Finding Analysis of the click logs of a large search engine: even simple features of a result entry change the clicks markedly, namely whether all the search words appear, how readable the snippet is and how long the displayed address is.

      In the tool With a search term, the tool checks whether all its words appear in the title and description; it warns about keyword lists instead of sentences and about long addresses.

    2. Tombros, A.; Sanderson, M. (1998): Advantages of query biased summaries in information retrieval. Proceedings of the 21st ACM SIGIR Conference (SIGIR '98), pp. 2–10

      Finding Snippets tailored to the search query let test participants judge relevance faster and more accurately than fixed snippets made of the title and first sentences.

      In the tool Explains why Google often takes the snippet from the page to match the search; the tool therefore advises having the key message in the visible page text as well.

    3. Cutrell, E.; Guan, Z. (2007): What are you looking for? An eye-tracking study of information usage in web search. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '07), pp. 407–416

      Finding Eye-tracking study: more text in the snippet improved performance on information tasks, but made it worse when someone wanted to reach a specific page.

      In the tool The length note distinguishes: guides and service pages use the full width, while for the home page or contact page the description may be shorter and unambiguous.

    4. Maxwell, D.; Azzopardi, L.; Moshfeghi, Y. (2017): A Study of Snippet Length and Informativeness: Behaviour, Performance and User Experience. Proceedings of the 40th ACM SIGIR Conference (SIGIR '17), pp. 135–144

      Finding 53 people, four lengths from the bare title to four text fragments: longer snippets were preferred, felt to be more informative and clicked more often; the people did not recognise relevant documents any better, though.

      In the tool That is why the tool reports a very short description as wasted space, but does not promise better results from the full width.

    5. Kim, J.; Thomas, P.; Sankaranarayana, R. et al. (2017): What Snippet Size is Needed in Mobile Web Search?. Proceedings of the 2017 Conference on Human Information Interaction and Retrieval (CHIIR '17), pp. 97–106

      Finding On mobile, long snippets lengthened search time on information tasks without improving accuracy; unlike on desktop, two to three lines are best there.

      In the tool The mobile preview uses two lines, and the tool advises putting the key message in this visible part.

    6. Sachse, J. (2019): The influence of snippet length on user behavior in mobile web search. Aslib Journal of Information Management 71 (3), pp. 325–343

      Finding Eye tracking with 31 people on mobile, snippets of one, three or five lines: one line gave too little information, longer snippets improved usability and experience; the visible screen area drew attention more strongly than on desktop.

      In the tool Supports the threshold for descriptions that are too short and the separate mobile preview.

    7. Kim, J.; Thomas, P.; Sankaranarayana, R. et al. (2014): Eye-tracking analysis of user behavior and performance in web search on large and small screens. Journal of the Association for Information Science and Technology 66 (3), pp. 526–544

      Finding Eye tracking on a large and a small screen: on the small one it was harder to draw information from the results list; dwell time and accuracy did not differ significantly.

      In the tool Reason for the separate mobile preview: the same text wraps differently there and is harder to take in.

    8. Kim, J.; Thomas, P.; Sankaranarayana, R. et al. (2015): Understanding eye movements on mobile devices for better presentation of search results. Journal of the Association for Information Science and Technology 67 (11), pp. 2607–2619

      Finding Three screen sizes, from early smartphones to large phones: equally efficient, but different in behaviour, such as frequent scrolling on the smallest screen.

      In the tool The tool uses a 375 px-wide phone and notes, as a limitation, that narrower and wider devices wrap text differently.

    9. Yue, Y.; Patel, R.; Roehrig, H. (2010): Beyond position bias: examining result attractiveness as a source of presentation bias in clickthrough data. Proceedings of the 19th International Conference on World Wide Web (WWW '10), pp. 1011–1018

      Finding Experiments in Google web search: besides position, the attractiveness of the entry influences clicks; results with more appealing titles were preferred.

      In the tool The tool highlights search words in bold as Google does and reports when the search term is missing from the title or only appears in the cut-off part.

    10. Pan, B.; Hembrooke, H.; Joachims, T. et al. (2007): In Google We Trust: Users' Decisions on Rank, Position, and Relevance. Journal of Computer-Mediated Communication 12 (3), pp. 801–823

      Finding Eye tracking with 16 students and secretly swapped results: higher-placed links were chosen even when they were less relevant; after the first two were swapped, they clicked the one now on top about three times as often as the one that was actually best.

      In the tool The page makes clear that a better title does not replace position; clicks by position are estimated by the click potential calculator.

    11. Joachims, T.; Granka, L.; Pan, B. et al. (2007): Evaluating the accuracy of implicit feedback from clicks and query reformulations in Web search. ACM Transactions on Information Systems 25 (2), Art. 7

      Finding Clicks are revealing but biased: they are no good as an absolute relevance judgement, while relative preferences between results can be read off fairly accurately on average.

      In the tool That is why the snippet preview does not calculate a click rate; anyone comparing two titles compares them at the same position.

    12. Craswell, N.; Zoeter, O.; Taylor, M. et al. (2008): An experimental comparison of click position-bias models. Proceedings of the 2008 International Conference on Web Search and Data Mining (WSDM '08), from p. 87

      Finding Large-scale experiment with deliberately swapped rankings: click behaviour at the top of the list was best explained by a cascade model, in which users read from top to bottom and stop at the first worthwhile result.

      In the tool Explains in the text why an entry has to be seen first: hardly anyone reads beyond the first worthwhile result.

    13. Bar-Ilan, J.; Keenoy, K.; Levene, M. et al. (2008): Presentation bias is significant in determining user preference for search results—A user study. Journal of the American Society for Information Science and Technology 60 (1), pp. 135–149

      Finding 65 people compared original and re-sorted results lists: placement determined the judgement of the best result more strongly than the content of the snippets; there was also a small effect from the reputation of the website.

      In the tool Supports the view that position counts first and, together with unkel-2017, the note on the website name in the title.

    14. Unkel, J.; Haas, A. (2017): The effects of credibility cues on the selection of search engine results. Journal of the Association for Information Science and Technology 68 (8), pp. 1850–1862

      Finding Observational study with 247 people and deliberately altered results pages: the ranking strongly shaped the choice; of three credibility signals, only the reputation of the source had an additional effect.

      In the tool Hence the note to put the website name at the start or end of the title, as Google recommends.

    15. Lewandowski, D.; Kammerer, Y. (2020): Factors influencing viewing behaviour on search engine results pages: a review of eye-tracking research. Behaviour & Information Technology 40 (14), pp. 1485–1515

      Finding Review of 41 eye-tracking studies on results pages: for some factors the findings are robust, for many inconsistent; the authors advise larger, theory-led studies.

      In the tool That is why the tool gives notes rather than a predicted click rate, and states its limits.

    Standards, authorities and manufacturer data

    Mon–Fri 8:00–17:00

    Have you checked your list of pages? Send us the result. We rewrite titles and descriptions for the most important pages, put them in place and look in Search Console after a few weeks to see what Google makes of them, in Rodewisch and across the whole Vogtland.

    +49 3744 4399760[email protected]

    Mon–Fri 8:00–17:00 · Straße der Jugend 5, 08228 Rodewisch

    Have titles and descriptions written for you
    +49 3744 4399760Mon–Fri 8:00–17:00
    CallCallback

    PARTS LIST · SHEET 1/1

    What this page is made of

    Values measured at build time. With JavaScript, your browser measures them again live.

    ITEMPARTTYPESIZE
    01index.htmlDocument≈ 29 kB
    02styles.cssStylesheet≈ 20 kB
    03scripts.jsScript≈ 13 kB
    04archivo-variable.woff2Font≈ 58 kB
    05ibm-plex-mono.woff2Font≈ 30 kB
    06favicon.svgImage< 1 kB

    Advertising or analytics cookies: none. Without your consent, the page loads nothing from third-party servers apart from Cloudflare, our delivery service. Fonts, scripts and images are hosted by us. That is how we build your IT, too.

    OUTSIDE OFFICE HOURS

    Feel free to call anyway

    Our regular office hours are Monday to Friday, 8:00–17:00.

    In the evening and at weekends the number is forwarded to us, and often someone will pick up. We cannot promise that, though.

    If nobody answers, leave a short message on the voicemail: your name, your number and what it is about. We will call back as soon as we can, on the next working day at the latest.

    The call costs nothing. If someone has to start work straight away outside office hours, the surcharge in the price list applies.

    Call now+49 3744 4399760

    Prefer to write? Use the contact form or e-mail [email protected]. We will read it on the next working day.

    DIAGNOSIS · AT-K2

    What do you need help with?

    ↵ SELECTESC CLOSECALL: +49 3744 4399760

    Custom settings

    Which services may load?

    Strictly necessary

    The choice you make here and your settings for colour scheme and motion. These are kept as small entries on your device and are never sent to a server. They are needed for the site to work and therefore cannot be switched off.