S SCHEMA.BIZ

Last updated:

SERP Simulator & Rich Snippet Preview

This SERP simulator shows how a page may look in Google's results on a desktop and a phone, with its title and description cut where results cut them and the rich results its structured data can earn.

Result fields
86 characters · 803 px
168 characters · 1046 px

Preview of how a Google result may look

Example Audiohttps://www.example.com › Headphones › Trail Runner 2
Trail Runner 2 Wireless Headphones – 40-Hour Battery…

Trail Runner 2 wireless headphones with active noise cancelling, 40 hours of battery and a 10-minute quick charge. Free delivery and free 30-day…

Rating: 4.61,287 reviews$129.99In stock
Free delivery · Free 30-day returns
Title, desktop803 px of 550 px · 86 characters (often quoted: 60) · cut after 52 of 86 characters

Shown up to “…– 40-Hour Battery”; the rest, “, Noise Cancelling | Example Audio”, is cut.

Description, desktop1046 px of 920 px · 168 characters (often quoted: 160) · cut after 144 of 168 characters

Shown up to “…delivery and free 30-day”; the rest, “returns on every order.”, is cut.

Rich results from the structured data

  • Eligibleon BreadcrumbList

    The page's position in the site hierarchy, shown in its search result (desktop only). Drawn on the preview above.

    From: itemListElement[].name

  • Eligibleon Product

    Shopping results for pages where a shopper can buy the product. Drawn on the preview above.

    From: offers.price, offers.priceCurrency, offers.availability, offers.shippingDetails.shippingRate.value, offers.hasMerchantReturnPolicy.merchantReturnDays

  • Eligibleon Product

    Price, availability and review stars under a product result. Drawn on the preview above.

    From: aggregateRating.ratingValue, aggregateRating.reviewCount, offers.price, offers.priceCurrency, offers.availability

Widths are measured in Arimo, a font with Arial's letter widths, at 20px for titles and 14px for descriptions (estimated until the font loads). The limits are estimates from SEO tools that measure results; Google publishes none, and often rewrites titles and snippets. Images in the markup aren't loaded: the preview draws placeholders.

What the SERP simulator shows

Type a title, a meta description and an address, or paste a page's HTML, or check a live page by its URL, and the simulator draws the result two ways: as a desktop result about 600 pixels wide and as a phone result. Switch the colors between light and dark to see the result as most people browse today. The title and the description are measured in pixels as you type and cut with an ellipsis at the point a result would cut them, and a ruler under the card shows the width, the limit and the cut. The title tag checker and the meta description length checker are the same tool, opened on the title or the description alone, with both devices side by side.

Below the card is the structured data. In the fields view you can add JSON-LD; in the other two, the page's own JSON-LD, Microdata and RDFa are read with the engine behind the Schema Markup Validator and the Schema Audit. Every Google feature the markup is checked for is listed with its status. The ones it's eligible for are drawn on the card, each with a switch, and the list names the properties that fill each part. When a feature is missing a required property, the list says which and links to the Validator with the same markup, so you can see the issue and its line.

How Google builds a search result

A result takes its parts from different places, and Google decides each one per search. The title link usually comes from the <title> element, but Google's documentation lists other sources it can use: the main visual title on the page, headings such as the <h1>, the og:title meta tag, other large and prominent text, anchor text on the page, the text of links pointing to the page, and the WebSite structured data. It reaches past the <title> when it finds a problem: a title that's half empty, out of date, inaccurate, repeated across many pages, or in a different language from the page.

The snippet, the text under the title, is written mainly from the page's content, chosen to match the search, so one page can show different snippets for different queries. Google uses the meta description when it thinks that describes the page better than text taken from the page. A robots meta tag with nosnippet removes the snippet, max-snippet caps its length in characters, and the data-nosnippet attribute keeps part of a page out of it. The simulator reads the first two from pasted or fetched HTML and applies them to the preview.

Above the title sit the site name and the address. Google prefers the name in the home page's WebSite structured data, then looks at og:site_name, the title and headings. On a desktop the address can be replaced by the page's breadcrumb trail when the page marks one up. Since January 2025, phone results show only the domain, because a breadcrumb was usually cut on a small screen, so the simulator's mobile card shows only the domain even when the breadcrumb is marked up. The favicon next to the site name comes from the page's icon link; it should be square and at least 8 by 8 pixels, and Google recommends larger than 48 by 48.

Pixel limits, and why they're estimates

Google's documentation is plain about length: there's no limit on how long a title or meta description can be, and results cut them "as needed, typically to fit the device width". It doesn't publish that width. SEO tools measure it from real results, and their figures differ, so the simulator uses the smallest credible one:

  • Titles: 550 px on desktop. Semrush gives 550 px, Screaming Frog's SEO Spider flags titles over 561 px, and Ahrefs says 600 px. No current source measures phone titles, so mobile uses the same 550 px, which matched Screaming Frog's last published measurement.
  • Descriptions: 920 px on desktop and 680 px on a phone, across the lines a snippet uses. Ahrefs gives those two figures, Moz gives about 680 px, and Screaming Frog's filter sits at 985 px for desktop.

Widths are measured at 20 pixels for titles and 14 for descriptions in Arimo, an open-source font with the same letter widths as Arial, so a title measures the same on a Mac, a PC or a phone. A cut falls at the end of the last whole word that fits with room for the ellipsis. Treat a result within a few pixels of a limit as borderline: the limits move when Google changes its design. The limits, their sources and the date they were checked are stated in the tool's notes and the checker pages.

What each rich result needs

The parts below the snippet come from structured data, and each has its own required properties. These are the ones the simulator draws, with what has to be in the markup for Google to consider the page; the Validator checks the full requirements, which are longer than this.

  • Review stars: an aggregateRating with a ratingValue and a ratingCount or reviewCount, or a single Review with an author and a rating, on a type Google shows ratings for, such as Product, Recipe, Book or SoftwareApplication. Self-serving reviews of a business on its own site don't get stars.
  • Price and availability (product snippets): a Product with a name and an offers, review or aggregateRating. A merchant listing, for a page where the product can be bought, needs an image and an offer with a price above zero; shippingDetails and hasMerchantReturnPolicy add the delivery and returns line.
  • Breadcrumb: a BreadcrumbList with at least two itemListElement items, each with a position, a name and, except for the last, an item address. Desktop only.
  • Event date and place: an Event with a name, a startDate and a location.
  • Recipe time and calories: a Recipe with a name and an image; the preview draws totalTime (or prep plus cook time) and nutrition.calories when they're there.
  • Video duration: a VideoObject with a name, a thumbnailUrl and an uploadDate; duration fills the badge.
  • Job details: a JobPosting with a title, description, datePosted and hiringOrganization, plus a jobLocation or remote work for the place.

Some features are gone. Google stopped showing FAQ results on May 7, 2026, How-to results on September 13, 2023 and the sitelinks search box on November 21, 2024. The markup is still valid schema.org, and the simulator still recognises it, but it lists those features greyed out with their dates and never draws them, because a preview that showed them would promise something Google no longer displays.

Five worked examples

Each example opens in the simulator above with its link. Change a word and watch the cut point and the rich results update.

1. A product page: stars, price, delivery and returns

The headphone page's title is 86 characters and about 803 px wide, so a desktop result shows "Trail Runner 2 Wireless Headphones – 40-Hour Battery…" and the brand at the end is lost. Its description is cut on both layouts. The JSON-LD earns three features: a product snippet with 4.6 stars from 1,287 reviews, a merchant listing with the price, "In stock", free delivery and free 30-day returns, and a breadcrumb that replaces the address on desktop. Switch the merchant listing off and the delivery line disappears, while the price stays, because the product snippet supplies it too. Open the product example.

2. A recipe: time, calories and a breadcrumb

The sourdough recipe's title, about 498 px, fits whole on both layouts. The Recipe markup has a rating, a total time of 1 hour 15 minutes and 240 calories, so the card shows a rating line and "1 hr 15 min · 240 cal", and the breadcrumb Recipes › Bread › Easy Sourdough Bread replaces the path on desktop. The description, at 974 px, is a little over the desktop limit: compare the two layouts to see how much more a phone loses. Open the recipe example.

3. An event: date and place

The concert's markup has a startDate and a Place with a name and a city, so the result gains a line reading "Sat, Jun 5 · Prospect Park Bandshell, Brooklyn". Its title is about 624 px and is cut on both layouts, losing the site name. Its description fits a desktop result at 792 px but not a phone's 680 px. Delete the location in the JSON-LD and the event moves to the "missing required properties" list, with a link to the Validator. Open the event example.

4. An article with a date

The blog post has a date in the Date field and a datePublished in its markup, so "Mar 14, 2026 —" comes before the description. That date takes room: the description is measured after it, which is why a dated snippet is cut sooner than the same text without a date. Google's documentation calls the date its estimate of when the page was published or updated, asks for a visible date that matches the structured data, and doesn't promise to show one. Clear the Date field to compare. Open the article example.

5. An FAQ page, a retired result

The FAQ page's markup is valid, with three questions and answers. Until May 7, 2026 it could have shown expandable questions under the result. Now the simulator lists the FAQ feature as retired, greyed out, and draws a plain result: the title, about 614 px and cut on desktop, and the description. The markup is still valid schema.org, but it no longer changes how the result looks in Google. Open the FAQ example.

Checking a live page

Choose "Check a URL", enter the address and press Check. Our server fetches the page as SchemaBizBot, following up to five redirects, and returns the HTML to your browser, where the title, meta description, canonical address, site name and structured data are read. The fields fill from the page, so you can try a different wording without editing the page. A link to the check, made with "Copy a link to this check", runs the same check when it's opened. The fetch reads the HTML as served: if a page adds its title or structured data with JavaScript, paste the rendered HTML instead. To open a page from the Validator, the Audit or the Generator, use their "Preview in search results" button; it carries the markup over in the address's fragment.

Frequently asked questions

FAQ

Is this exactly what Google will show?

No. It's a preview of how a Google result may look, drawn from what your page gives Google. Google chooses the title link and the snippet for each search and often rewrites both, its layout changes, and it doesn't publish where it cuts text. The simulator shows the likely result if Google uses your title and description as they are, cut at limits measured by SEO tools.

Why does it measure pixels instead of characters?

Because results cut text by width. A title of narrow letters fits more characters than a title of capitals, so a character count can say a title fits when it doesn't, or the reverse. The simulator measures each title and description in Arimo, a free font with the same letter widths as Arial, at the size results use, and shows the character count next to the width.

Which rich results can it show?

Review stars, price and availability, delivery and returns, a breadcrumb path in place of the address, an event's date and place, a recipe's cooking time and calories, a video's duration and a job's employer, place and salary, plus an article's date. It draws one only when the markup is eligible for it under Google's current requirements, read by the same engine as the Schema Markup Validator. Retired results, such as FAQ, are listed greyed out with the date Google stopped showing them.

Is what I paste or type sent anywhere?

No. The fields, the JSON-LD and pasted HTML stay in your browser, and a share link keeps them after the # in the address, which browsers don't send to servers. To check a URL, our server fetches that page as SchemaBizBot and sends the HTML back to your browser. Like every tool here, the simulator records what kind of check ran: the input type, whether the title and description get cut, their widths in pixels, how many rich results are drawn, and the schema.org types and issue codes found. Never the title, the description or the markup itself.

Why are images shown as grey boxes?

Loading a favicon, logo or video thumbnail named in your markup would make your browser request it from that site, which would tell the site you were previewing its page. The simulator draws a placeholder instead: a letter for the favicon, a grey frame with the duration for a video.