Free tool

SERP preview and citation card simulator

Type a title and meta description, or read them from a live page, and see where Google cuts them on desktop and mobile and how an answer engine shows the page as a cited source.

Optional. Reads the live title, description and Open Graph tags so you can edit from what is published. Or type below and nothing is sent anywhere.

0 / 60 charactersFix

Add a title tag.

0 / 160 charactersFix

Add a meta description. Without one, engines pick any sentence from the page.

Google, desktop

e

example.com

https://example.com › page

Your page title appears here

Your meta description appears here. Google shows about two lines on desktop and three on mobile, and bolds the words that match the ...

The description would be cut here.

Google, mobile

e

example.com

https://example.com › page

Your page title appears here

Your meta description appears here. Google shows about two lines on desktop and three on mobile, and ...

The description would be cut here.

Answer engine citation card

1eexample.com

Your page title appears here

Your meta description appears here. Google shows about two lines on desktop and three on mobile, and bolds the words that match the query.

no og:image

A generic rendering of how answer engines list a cited source: site, title, a sentence of the description, and the Open Graph image when there is one. Exact layouts differ by engine.

Widths are approximations: about 600px for a desktop title and 920px for a desktop description, measured in Arial. Google also rewrites titles and snippets it finds unhelpful, so a preview is a floor, not a promise.

Free, no sign-up. Results for the same URL are cached for an hour.

What the preview shows

Three renderings of the same two tags. The Google desktop and mobile panels cut the title and description at the pixel widths Google has used for years, measured in the font Google renders. The citation card shows the same tags the way an answer engine lists a source under its answer: site name, title, a sentence, and the Open Graph image when there is one.

  • Title: about 600 pixels on desktop, roughly 50 to 60 characters. The preview cuts at a word boundary and adds an ellipsis where Google would.
  • Description: about two lines on desktop and three on mobile. The optional query field bolds matching words, as Google does.
  • Verdicts next to each field use the same thresholds as our AI readiness checker, so a green pill here means the signal passes there.

Why the same tags matter for AI answers

Answer engines do not show ten blue links, but they do show sources. When ChatGPT, Perplexity, Gemini or Google's AI Overviews cite a page, the card they render is built from the page's title, its meta description or first sentences, and its Open Graph image. A title that names the question the page answers, and a description that states the answer, make the citation legible and clickable.

The engines also use the meta description as a summary candidate when they describe a page. A description that is a list of keywords gives them nothing to quote; a description that is one clear sentence often gets quoted verbatim.

How to write a title that survives the cut

  1. Lead with what the page is: the product, the question, or the comparison. Readers and engines decide in the first four words.
  2. Add the qualifier that makes it specific: the year, the audience, the platform, the price point.
  3. End with the brand, after a separator. If the title is cut, the brand is what you can afford to lose; the site name line shows it anyway.
  4. Match the H1. Google rewrites titles that disagree with the visible heading, and answer engines treat the H1 as the page's name.

How to write a description that gets quoted

Write the answer, not the teaser. If the page explains how long a title tag should be, the description should say how long a title tag should be. One or two sentences, 80 to 160 characters, in the third person, with the main query's words in it so they bold in the snippet. Leave out prices and dates unless you will keep them current; a stale fact in a description gets repeated by engines for months.

Then read it as a citation card: would you click a source described this way? If the sentence only makes sense after reading the page, rewrite it so it stands alone.

Open Graph tags and the citation card

og:title, og:description, og:image and og:type are what link previews and many citation cards read. The readiness rubric passes a page only when all four are set. Use Read from URL to see which are present on a live page; the og:image verdict appears next to the image field. The image should be at least 1200 by 630 pixels, show the subject rather than a logo, and be served from a URL that does not require cookies or JavaScript to load.

FAQ

How long should a title tag be?

Google cuts a desktop title at about 600 pixels, which is roughly 50 to 60 characters in a normal mix of letters. Width matters more than the count: capital letters and W are wide, lowercase i and l are narrow. Put the words that identify the page first and the brand last, so a cut costs you the least.

How long should a meta description be?

Aim for 80 to 160 characters. That is the range our AI readiness rubric passes, and it fits the two lines Google shows on desktop. Mobile shows up to three lines, so a description near 160 characters is safe on both. Below 80 characters you are leaving the space, and the chance to state your answer, unused.

Does Google always use my title and description?

No. Google rewrites a title when it judges it unhelpful, for example boilerplate, keyword lists or a title that does not match the H1, and it builds a snippet from the page body when the meta description does not match the query. Writing a specific title and a description that states the page's answer is how you keep control most of the time.

Why does the preview bold some words?

Google bolds words in the snippet that match the user's query. Type the query you want the page to rank for in the optional field and the preview bolds those words, which shows whether your description actually contains them.

What is the citation card?

When an answer engine cites a page it shows a small source card: the site, the page title, often one sentence, and sometimes the Open Graph image. The exact layout differs by engine and changes often, so the preview is a generic rendering. The inputs are the same across engines: title, description and og:image, which is why the preview reads those tags.

Does this tool send my text to a server?

Only if you click Read from URL, which fetches the page's head tags so you can start from what is published. Typing in the fields runs entirely in your browser; nothing is stored or sent.

What should I do after the preview looks right?

Publish the tags, then run the AI readiness checker on the page to confirm the meta description and Open Graph signals pass, and the single-page SEO check to confirm there is exactly one title, the canonical is right and nothing blocks indexing.

More free tools

Good tags get you shown. Being cited is the next step.

LeapScope tracks whether the AI engines cite your pages for the prompts your buyers ask, and shows which titles and pages they pick instead.