AI Snippet Preview

Measures your title and description in rendered pixels, the way Google truncates them, and tests whether a section of your page survives being lifted out and quoted. Runs entirely in your browser.

Live v2.0 · Updated September 2026 Free · No login
Preview Idle

Paste one section, heading and opening paragraph. Assistants retrieve passages, not metadata, so this is the part that decides whether you get cited.

Runs locally · nothing sent to a server

How it works

It measures pixels, not characters. Google truncates on rendered width, so character counts are a proxy that fails on exactly the titles you care about. “Illinois” and “Wisconsin” are both nine characters and one is noticeably wider. This tool draws your text to a canvas in Arial at the size Google renders it, measures the result, and wraps it against the real container width.

Desktop titles get one line in a 600px container. Mobile titles get two. Descriptions get two lines on desktop and three on mobile. Where your text crosses that boundary, the preview shows the cut in grey so you can see the words you are about to lose.

The second panel tests something different. An assistant does not quote your meta description. It retrieves a passage from the body of the page and reads it with nothing around it. So the passage box runs five checks that decide whether a section survives that: whether it opens with a dangling reference, whether it names its own subject, whether the claim arrives before the caveat, whether it depends on the section above it, and whether it is a workable length for a chunk.

Every check tells you which words triggered it. The reasoning behind them is in what AI search actually retrieves from a page.

Frequently asked

Because that is what Google does. A title of “Illinois Illinois Illinois” and one of “Wisconsin Wisconsin Wisconsin” are the same character count and different widths, so a character limit will pass one and fail the other for no reason. This tool renders your text to a canvas in Arial at 20px for titles and 14px for descriptions, which is what a results page uses, and measures the actual width. The container widths are approximations of Google’s layout rather than published figures, so treat the last few pixels as a guide.
No. It measures exactly what you type, entirely in your browser, so you can draft a snippet before anything is published. Nothing is fetched and nothing is sent to a server.
Because assistants retrieve passages from the body of a page, not metadata. A section arrives at the model on its own, with everything around it gone. So a paragraph that opens “as we saw above” arrives as a fragment pointing at something the model cannot see, and it will not be used. The meta description still matters for the click; the passage decides the citation. They are different jobs.
Often not. Google rewrites a large share of titles, most commonly when yours is too long, keyword-stuffed, or duplicated across a site. Staying inside the container width is the part you control, which is why the tool measures it. If your title is rewritten anyway, the usual causes are length and a brand suffix repeated on every page.