Untitled page
Your description will appear here.
Paste a title, description and URL to see the desktop and mobile Google result side by side, with the exact pixel width and where each one is cut.
Paste a title and description to see where each one is cut on desktop and on mobile. Measured with 20px Arial; desktop limit 600px.
Your snippet
Title is capped at 300 characters, description at 500.
Search result preview
Desktop
Untitled page
Your description will appear here.
Measured with 20px Arial · Desktop limit 600px · Approximate
Mobile
Untitled page
Your description will appear here.
Measured with 16px Arial · Mobile limit 920px
Checks
Problem: No title yet. Google will build the title link from your headings or from anchor text on other pages.
Give the page a <title> that names what the page is about. Without one you have no control over the most visible line of the result.
Check: No description. Google will still show a snippet, assembled from page text — often starting mid-sentence.
Write one or two sentences describing this specific page. You lose nothing by having one, and Google uses it whenever it matches the query.
Note: Widths are approximated (this browser did not expose canvas text metrics). Values are within a few percent.
The Arial metric table used here matches Arial, Helvetica and Liberation Sans, so the numbers stay usable.
This page is a simulator, not an audit — it deliberately gives no score.
Next steps
A desktop result today has five parts stacked in this order: the favicon, the site name, the URL breadcrumb, the title link, and the snippet. Only two of them come straight from your HTML — the title link is built from your <title> (usually), and the snippet is built from your meta description or from page text.
The other three are inferred. Google picks the site name from your homepage’s WebSite structured data, the favicon from the icon link on your homepage, and the breadcrumb from your URL path or BreadcrumbList markup. That is why this preview asks for a site name and a URL separately: they occupy their own line and consume none of your title’s width.
An optional date sits at the start of the snippet on many results. Google decides that on its own; datePublished in your structured data is a hint, not a switch. When it appears it takes roughly 95 pixels away from the description.
Google’s own documentation never gives a character limit. It says the title link is truncated “typically to fit the device width”. Width is what matters, and characters have very different widths: in Arial at 20px, a capital W is 18.9px while a lowercase i is 4.4px — more than four times narrower. A 55-character title of narrow letters fits comfortably; a 45-character title in capitals does not.
We cut the desktop title at 600px and the mobile title at 920px, measured with 20px Arial and 16px Arial. Other tools publish different numbers — Portent uses 600px, Sistrix uses 580px desktop and 920px mobile — because each measured a different font size and a different assumption about the container. None of these are official. Treat the last 30–40px as a grey zone rather than a hard line.
The practical rule that follows: put the words that must survive in the first 60% of the title, and keep the brand name for the end where truncation is harmless.
Google states there is no limit on the length of a meta description, and that the snippet is truncated “as needed, typically to fit the device width”. In practice the desktop snippet stops near 920px (about 155–160 Latin characters at 14px Arial) and the mobile snippet near 680px (about 120 characters).
A description below roughly 430px usually wastes the space. But length is not the goal: Google replaces the meta description with text taken from the page whenever it thinks the page text answers the query better. A description that reads like a sentence about this specific page survives more often than one stuffed with keywords.
Google says it replaces the title link when the <title> is a poor match for the page, and lists the situations: titles that are half empty or boilerplate, titles that are obsolete, titles that are inaccurate, micro-boilerplate repeated across a site, titles that do not make the main heading obvious, titles in a language different from the page, and titles that repeat the site name.
Rewrites are not a penalty and they are not ranking-related — Google is choosing a better label for the same result. But it takes the most visible line of your result out of your hands, so the fix is to remove the trigger rather than to fight it: give each page a distinct, accurate title that matches its H1 and the page language.
If the title in the search result is your H1 rather than your <title>, that is the most common signal that the rewrite happened.
The site name above your title is taken from your homepage. The strongest signal is WebSite structured data on the home page with name and url; alternateName provides a shorter form Google may use instead. og:site_name and the <title> of the homepage act as weaker fallbacks.
The favicon is read from the icon link element on your homepage, and one icon is used per host. Google’s requirements: a square image at least 8×8px — 48×48px or larger is recommended and is what actually looks right — in BMP, GIF, ICO, JPEG, PNG, SVG, PPM or TIFF. The file must be crawlable, so do not block it in robots.txt, and the icon should stay at a stable URL because Google recrawls it on its own schedule.
Both take time. A newly added site name or favicon can take days to weeks to appear, and a subdomain gets its own site name only if it looks like an independent site.
The breadcrumb line replaces the raw URL. Google builds it from the URL path, or from BreadcrumbList structured data when you provide it — that is the only way to control the labels, for example showing “Guides” instead of the folder name “g”.
Dates are shown when Google decides the page is time-sensitive. Consistency helps: a visible date in the page, a datePublished in structured data and a lastmod in the sitemap that all agree. Removing dates to look fresh usually backfires, because the snippet then loses the line that tells searchers the content is current.
Not every rich result changes the snippet. Note that FAQ rich results stopped being shown in Google Search on 2026-05-07 and HowTo results were removed earlier, so FAQ or HowTo markup no longer adds lines under your snippet — the markup remains valid for other consumers, but this preview does not simulate it.
CJK characters are full-width: one Hangul syllable or one kanji is about twice as wide as an average Latin letter. At 600px, a Latin title fits roughly 55–60 characters but a Korean title fits about 30 — and a mixed title fits somewhere between, which is why a character counter alone is misleading for these languages.
This tool measures the actual rendered width, so the counter under a Korean title reports “cuts at about 30 characters” rather than a Latin-based number. Two practical consequences: separators like “ | ” and “ — ” cost real width in a line that is already tight, and English brand names inside a Korean title are cheap because Latin letters are narrow.
Korean pages also lose more to the site name line than English ones: if your title ends with “· 브랜드명” and the same brand already appears above the title, you are paying full-width characters for a duplicate.
No. Google has never published a character limit — it truncates by width. 60 characters is a rule of thumb that assumes average-width Latin letters: a title in capitals can be cut at 50, and one made of narrow letters can survive past 65. A Korean title fits about 30 characters in the same space.
Because each tool measures with a different font, font size and container assumption. This page uses 20px Arial with a 600px desktop limit and prints that basis under the cards. Portent uses 600px, Sistrix uses 580px. None of these are official numbers, so treat the last 30–40px as slack rather than a hard line.
Not guaranteed. Google rebuilds the snippet from page text whenever it judges that the page answers the query better than your description does — and it does that per query, so the same page can show different snippets. A description that states the page topic in one clear sentence is used verbatim far more often.
No. Measuring and rendering happen entirely in your browser, and the text is kept only in this page’s URL and in your own browser storage. The single outbound request is the favicon image, and only when you type an https:// address into the favicon field yourself.
It compares two candidates against the same width budget. Both get their own card and their own pixel gauge, so you can see which one survives the cut before you publish. Leave it empty and only one card is rendered.
More SEO & Web tools: SEO & Web