SERP Simulator: See Your Google Result Before You Publish

Meta description length, pixel widths and where a Google result is cut.

A search result is three short lines laid out in a fixed space, and most of what goes wrong with one happens at the right-hand edge. Here is how that edge is decided, why it moves between a laptop and a phone, and what a regulated firm loses when its most careful words sit last.

What a search result is made of

A standard Google result on the web has four parts, top to bottom. A site line, with the site's icon in a small circle, the site name and the page's address written as a breadcrumb (willowdaleequity.com › blog › 1099-vs-k1). A title link, usually drawn from the page's <title> tag. A snippet of a line or two, often drawn from the meta description. And, on some results, extras such as a date, a rating or sitelinks, which this simulator does not draw.

Only two of those lines are yours to write directly for this page: the title tag and the meta description. The site name and icon are decided once, at the level of the whole site, and the breadcrumb comes from the URL. That is why a SERP simulator asks for three things. The URL sets the site line, and the title and description are what you are really testing.

Characters or pixels: what actually runs out

A result is set in a proportional font, and the space it runs out of is measured in pixels, so a character count is only a stand-in. In Arial, a capital M takes 833 thousandths of the type size and a lowercase l takes 222. At the 20px a desktop title is set in, that is about 17 px against 4 px. "MINIMUM" and "illicit" are both seven letters; the first is about 90 px wide in capitals and the second about 38 px.

This is why the familiar advice, 50 to 60 characters for a title and 150 to 160 for a description, is right on average and wrong at the edges. A title written in plain lowercase words can pass 60 characters and still fit. A title with a firm name in capitals, a ticker, a year and a few W's and M's can be cut at 52. A meta title checker that counts characters will pass both; the width tells you which one the searcher will actually see in full. This simulator reports both numbers for every line, so you can see when they disagree.

The published limits disagree

Google does not publish a pixel limit for either line. Its documentation says title links and snippets are "truncated in Google Search results as needed, typically to fit the device width", and for the meta description adds that "there's no limit on how long a meta description can be". Every number you have read comes from someone measuring results and writing down what they saw, and the tools that rank for this topic have written down different things.

Rather than pick one figure and present it as the rule, this page draws the result at the generous end of each range and marks the words that fall inside it. An underlined word is one that some estimates keep and others cut. If the words that carry your meaning are underlined, rewrite until they are not. The 600 px desktop line and the 920 px description are the same figures this site's Title Tag Checker and Meta Description Checker use, and all three pages measure with the same table of character widths, so a title typed here and the same title published and checked there come out at the same width.

Why the result changes on a phone

Mobile results are narrower, and the two lines behave differently in the smaller space. The title is allowed to wrap, so a title that is cut on one desktop line can show in full across two lines on a phone. The description goes the other way: its budget on mobile, about 680 px in the published figures against about 920 px on desktop, is roughly three quarters of the desktop one, so the end of a description that fits a laptop is the first thing a phone drops.

That asymmetry catches almost everyone who checks a result on one device. Willowdale Equity's home page description is 153 characters and about 931 px wide. On desktop only its last word, "deals.", is at risk. On mobile the whole closing sentence, "Join the Investor Club for first-look deals.", falls past the cut, and that sentence is the call to action. The first sentence, the one that describes the firm, survives on both. Put what the searcher must read first, and treat the end of a description as the part a phone will probably not show.

Bold words take more room

When a searcher's words appear in the snippet, Google usually bolds them, and bold letters are wider: in Arial Bold a lowercase r is 389 thousandths wide against 333 in the regular weight, and an n is 611 against 556. Across ordinary lowercase text, that adds several percent to every bolded word, which is enough to push the last word of a description that fitted on its own past the cut. Estimates of the effect published by ranking tools range from about 5% to about 20%.

Type the words you expect people to search into the optional field above and the simulator bolds each matching word in the description and measures it in Arial Bold. It matches whole words, ignores short joining words such as "for" and "the", and does not bold the title, because in current results the bolding usually falls on the snippet. Google also bolds close variants and synonyms, which no simulator can know in advance, so treat the bolded figure as the lower end of what a real search adds.

When Google does not use what you wrote

A preview shows your words the way they would appear if Google used them, and Google often does not. For titles, it draws on the title tag, the main heading, other prominent text on the page and the links pointing to it, and it replaces titles that are vague, out of date or repeated across many pages. For snippets, its documentation says they "are primarily created from the page content itself", with the meta description used when it describes the page better than the text does. The snippet can also change with the search: the same page can show one sentence for one query and a different sentence for another.

Two habits make your own wording more likely to be the one shown. Write each description for its page alone, since Google says "identical or similar descriptions on every page of a site aren't helpful". And make the title agree with the page's main heading, because the heading is the first thing Google reaches for when it decides a title needs replacing. The H1 Checker shows what that heading is on a published page.

The site name and icon line

The line above the title belongs to the site, not the page. Google chooses the site name from the home page, and its documentation says WebSite structured data is the most important signal if you want to state a preference, with the home page's title, og:site_name and headings also considered. Site names apply to domains and subdomains, never to a folder. The icon is the one linked from the home page with <link rel="icon">; Google asks for a square image and recommends one larger than 48 by 48 pixels. If you leave the site name field blank, the simulator uses your domain, which is what many small sites get until they declare a name.

What gets cut when a regulated firm's wording runs long

Every guide to snippet length frames a cut as lost clicks. For a financial adviser, a fund sponsor, a law firm or a medical practice there is a second cost, and it is the one reviewers care about. Marketing wording that has been through review usually puts the qualifier at the end: the claim first, then "past performance does not guarantee future results", "terms apply", "for accredited investors", "results vary", "not legal advice". A snippet is cut from the end. When the cut falls inside that last clause, the searcher reads the claim without the words that qualified it, and "Past performance ..." or "Returns of up to 9% a year ..." is what sits on the results page under your name.

Nothing about that is visible in the draft, where the whole sentence sits on one screen, and a character count passes it. The fix is structural rather than cosmetic: put the qualifier early, inside the first sentence, or make the description a factual one that needs no qualifier at all, such as what the page covers and for whom. Keep promises and performance figures out of the title and description entirely where you can, because those two lines are the most read and least reviewed copy you publish.

To help with the first check, the simulator looks for common qualifying words and phrases and flags any that fall past a cut: past performance, results vary, results may vary, individual results, no guarantee, not guaranteed, does not guarantee, not legal advice, not financial advice, not tax advice, terms apply, conditions apply, restrictions apply, subject to, accredited investors, licensed in, consult, see disclosures, disclosures, disclaimer, may, might, typically, generally, up to, estimated, hypothetical and not. It is a heuristic list, not a rule set: it knows nothing about your regulator, and a flag is a prompt to look again, not a judgement. Have your reviewer sign off the title and description the way they sign off body copy. This page is not legal advice. For wording checked against a specific industry's advertising rules, the Marketing Compliance Checker flags phrases for review by industry.

Writing a title and description that survive the cut

• Lead with the words the searcher used. The start of a title shows on every device. Put the topic there, not the firm's name.
• Brand last, after a separator. If the end of the title is cut, the part that goes is the name the searcher can already read in the site line.
• One idea per description, in the first sentence. Treat everything after the first full stop as optional on mobile.
• Qualifier early, or no claim that needs one. The words that make a sentence accurate should not be the ones a phone cuts.
• Match the page's intent. A guide should read like a guide and a service page like a service. A description that promises something the page does not deliver earns a click and loses the visitor.
• Unique to the page. Six office pages sharing one description compete with each other and give Google a reason to write its own.
• Current. A year in the title that has passed, or a rate that has changed, is the kind of stale wording Google replaces and a reviewer should catch.

Before you publish, and after

This simulator is the before: a place to try wording while it is still a draft, with nothing live and nothing fetched. Once the page is published, what matters is what the server actually sends, which a template, an SEO plugin or a script can change without anyone noticing. The Title Tag Checker and Meta Description Checker read a live URL's served HTML and draw the same preview from it, so the two halves line up: write it here, publish, then confirm the page carries the title and description you signed off.