What it Checks
Google cuts titles and descriptions by width, not by character count. The simulator measures your text in your browser in Arial, the font Google uses for results (20px for titles, 14px for descriptions), wraps it into the columns Google uses for each device, and cuts it with ... where the last line runs out.
You can type the snippet yourself or fetch a live page: the server reads its title, meta description, site name, favicon, publication date and star rating, and the preview fills in from them. A page with a noindex directive is flagged: it gets no snippet at all.
Bulk does the same for a list of pages: their real titles and descriptions, measured against both layouts, in a table you can export.
Run a Test
- Paste a page URL and press Fetch, or skip it and edit the sample snippet directly.
- Edit the page title and meta description. The preview and the counters update as you type.
- Switch between Mobile and Desktop. The verdict reads Fits the preview., Title would be cut off., Description would be cut off., Both would be cut off. or No title.
- For many pages, open Bulk, paste up to 100 URLs (or pick a CSV file: every cell that is a URL is read, other columns are skipped) and press Check. Rows appear as pages are fetched, four at a time.
Options
- Description cut-off (characters). Where the preview cuts the description before the pixel check: 120 on mobile and 158 on desktop by default, matching Google's usual snippet, adjustable from 50 to 320. Google has no fixed limit. Switching device resets it to that device's default.
- Search query. Words of the query are shown in bold in the description, the way Google highlights them.
- Date, Rating, Favicon. Show or hide the date before the description, the star rating line and the site icon. Date and Rating switch on by themselves when the fetched page has them; otherwise the preview uses today's date and a sample rating.
- PNG. Downloads the preview as an image at twice its size.
The layouts used for each device:
| Device | Title | Description |
|---|---|---|
| Desktop | 1 line of 600px | 2 lines of 600px, 158 characters |
| Mobile | 2 lines of 330px | 4 lines of 330px, 120 characters |
Reading the Result
- Title: on desktop, the title's width against its one line, for example
512px / 600px; on mobile, how many of its two lines it fills, for example2 of 2 lines · 384px(words wrap, so the width alone doesn't tell). The field hint also shows the character count and the device's limit. - Description: characters used against the maximum length, for example
142 / 158 chars. The description is cut when it is longer than the maximum or when it does not fit in its lines. - Preview: the result as Google lays it out: favicon, site name and breadcrumb built from the URL path, title, optional rating, optional date and the description, with cut text ending in
.... - Bulk table: per URL the title with its characters, pixels and mobile lines, fits, cut or missing for the title and the description on desktop and on mobile, and a noindex mark. Pages that couldn't be read show why (bot wall, error status, not HTML). The verdict counts titles and descriptions cut, and pages missing either. CSV and Excel export the filtered rows.
Good to Know
- Measuring happens in the browser, so no request is made while you edit. Only Fetch calls the server.
- The page is fetched with a Googlebot user agent. A site that answers that user agent differently shows what it serves to Googlebot; one that refuses it from a data centre (a bot wall) is reported as such, and you can still type the snippet by hand.
- Widths are measured in Arial at Google's sizes in your browser, so results can differ by a few pixels between systems. Google's own layout changes from time to time: treat the limits as a close guide, not an exact rule.
- The date comes from
article:published_timeordatePublished; the rating from anaggregateRatingin the page's JSON-LD.
API
POST /api/page-meta
Fetch returns what a search result is built from. The pixel measurement is not part of the API: it runs in the browser. The favicon comes back as a data URL (empty when it could not be fetched, or when the request sets "favicon": false, as Bulk does), rating is null when the page has none, and noindex is true when meta robots or X-Robots-Tag keeps the page out of results. A bot wall, an error status or a non-HTML answer comes back as an error with HTTP 400.
curl -X POST https://plumb.reacthive.dev/api/page-meta \
-H "content-type: application/json" \
-d '{ "url": "https://www.bbc.com/news" }'{
"url": "https://www.bbc.com/news",
"status": 200,
"title": "BBC News - Breaking news, video and the latest top stories from the U.S. and around the world",
"description": "Visit BBC News for the latest news, breaking news, video, audio and analysis. …",
"ogTitle": "BBC News - Breaking news, video and the latest top stories from the U.S. and around the world",
"siteName": "",
"favicon": "data:image/png;base64,iVBORw0KGgo…",
"date": "",
"rating": null,
"noindex": false
}{ "error": "PerimeterX answered HTTP 403 with a challenge page instead of the page. The title and description could not be read." }