SERP Preview

Loading tool…

About SERP Preview

Type a title, display URL, and description. Two mocks update as you type: Desktop and Mobile. Truncation uses pixel width, not a raw character count. Desktop title cutoff is 600 pixels, description 920. Mobile title is 680, description 980.

This is a planning preview. Google can rewrite titles from headings and brand names. Sitename and favicon are not drawn. Nothing is fetched; you are typing into a mock, not checking a live URL. Pair it with the Meta Tag Analyzer after the tags are live.

When to use it

Use it while a title and description still live in a brief or a ticket, before they hit the template. That is the moment to see whether Desktop clips while Mobile still shows the last words.

Use it again after Meta Tag Analyzer if you want to edit strings without another fetch. There is no Analyze button. The mocks update as you type.

How to use SERP Preview

  1. 1Enter title, display URL, and description. The sample URL is only a placeholder until you replace it.
  2. 2Watch both previews. Desktop and mobile widths differ. Overflow shows an ellipsis.
  3. 3Shorten the text. Keep editing until the ellipsis disappears if you want the full title visible.
  4. 4Copy the wording. You still need to put those strings in the live title and description tags.

How to read the results

Fields are Title, Display URL, and Description. Two mocks sit under the form: Desktop and Mobile. An ellipsis means that viewport's pixel budget was exceeded. Desktop cuts the title at 600px and the description at 920px. Mobile allows 680px and 980px.

The sample values are a placeholder (aiaq.io title, this tool's path, and a short blurb). Replace all three. Overflow is a length warning, not a ranking score. A clean mock still does not prove Google will keep that wording.

Why this matters

Mobile is given more pixels than Desktop for the same title (680 versus 600). A line that looks complete on a phone can still lose its last words on a laptop SERP. That is why two mocks exist instead of one character counter.

Display URL is the green path readers see, not a fetch target. Changing it never loads a page. Sitename and favicon are omitted because Google draws those from other systems, and packing them into Title as well often doubles the brand.

Limits and privacy

Title, Display URL, and Description never leave this browser. There is no fetch, no hourly cap, and no login. Width is an Arial-like estimate, not the exact result font.

Common mistakes

Leaving Display URL as the sample path and thinking the tool fetched aiaq.io. Nothing is requested.

Writing only against Mobile. Desktop is the tighter title budget. Shorten until the Desktop ellipsis clears if those words must stay visible.

Treating a perfect mock as a live tag check. Publish, then run Meta Tag Analyzer on the URL.

FAQs

Will Google show this exact title?
Not guaranteed. They often rewrite titles. Use this to plan length, then check the live SERP.
Why two widths?
Desktop and mobile snippets use different pixel budgets. A title that fits on mobile can still truncate on desktop.
Is the sitename included?
No. Google may append a sitename separately. This mock is title, URL, and description only.
Is the favicon in the preview?
No. Favicons in results are a separate Google feature. Generate icons with the Favicon Generator.
Does this fetch my page?
No. It is a local mock. Use Meta Tag Analyzer to read live tags from a URL.
Why is there no Analyze button?
The mocks update on every keystroke. Fields are Title, Display URL, and Description. There is nothing to submit and no progress bar. If you need a live fetch, leave this page and open Meta Tag Analyzer.
Why does Desktop clip when Mobile does not?
Desktop title budget is 600px; Mobile is 680px. Descriptions are 920px versus 980px. The same string can show an ellipsis on Desktop and look complete on Mobile. Shorten against the tighter mock.
What is Display URL for?
It is the green path drawn in the mock. It is not fetched and does not have to resolve. Change it to the path you want readers to see. Sitename and favicon are still omitted on purpose.