SERP Snippet Preview — Example Report Run Your Own Audit →
📋 Example Report — Demo Data

SERP Preview Example: Title, Description and Snippet

This example shows the aiwebpageseo SERP Preview for a blog article. The title is 67 characters — slightly over the 60-character display limit, causing potential truncation. The meta description is 142 characters — within range. The preview shows exactly how it appears in Google.

SERP Preview — blog.example.com/seo-guide-2026
Title (67 chars)⚠ Over 60 — may truncate
Description (142 chars)✅ Good length
https://blog.example.com › seo-guide-2026
The Complete SEO Guide for 2026 — Rankings, AEO &...
15 Mar 2026 — Everything you need to know about SEO in 2026 including technical fixes, AEO optimisation and AI search visibility strategies that actually work.
⚠ Title is 7 chars over the recommended limit. The word "Rankings" and everything after may be truncated. Consider: "The Complete SEO Guide for 2026 — AEO & AI Search" (50 chars).
With FAQ Rich Result (Add FAQPage Schema)
https://blog.example.com › seo-guide-2026
The Complete SEO Guide for 2026
Everything you need to know about SEO in 2026 including technical fixes and AI search.
What is AEO and how is it different from SEO?
How long does it take to see AEO results?
Do I need paid tools for SEO in 2026?
⚠ Google restricted FAQ rich results in 2023 to a narrow set of government and health sites — most sites will no longer see this dropdown. FAQPage markup still helps answer engines parse your Q&As.
Google rewrites most titles anyway

Before optimising a title to the character, understand what the title tag actually is. It is a strong suggestion, not an instruction. Google rewrites the displayed title on a large proportion of results, and it does so deliberately.

When it rewrites, it draws from the sources it thinks fit the query better — your H1, prominent on-page text, anchor text pointing at the page, or your og:title. This is why the H1 matters more than its ranking weight suggests: it is the most common substitute Google reaches for.

The rewrite is usually triggered by a title that is not doing its job:

The way to keep your title is to write one Google has no reason to replace: descriptive, specific, accurate to the page, and matching what the H1 says. Fighting the rewrite by stuffing more keywords in produces exactly the title most likely to be discarded.

Pixels, not characters — and the 60-character rule is a proxy

The report flags 67 characters as over the limit, and it is right to — but the mechanism is worth understanding, because the character count is a convenient fiction.

Google truncates on pixel width, at roughly 600px on desktop. Characters are not equal: an i or an l is narrow, a W or an M is wide. A 62-character title in narrow characters may fit comfortably where a 55-character title in capitals does not. Capitalised titles truncate far earlier than anyone expects.

structure

Front-load, always

Truncation removes from the right. So the words that distinguish this page from every other page go on the left, and the brand goes on the right where losing it costs nothing. "The Complete SEO Guide for 2026 — Rankings, AEO &…" loses the two terms most likely to be searched for. Reverse it and truncation becomes harmless.

The suggested rewrite in the report — 50 characters — is a sound instinct for a different reason than length: it is a complete, self-contained claim, and it survives whatever the SERP does to it.

The description is not a ranking factor — and Google will probably rewrite it too

Two facts about the meta description that change how much time it deserves:

  1. It has no ranking weight. Google has been explicit about this for many years. Putting keywords in it does not help you rank, and a page with no meta description at all can rank first.
  2. Google replaces it most of the time. When it does, it lifts a passage from your page that matches the specific query. Different queries hitting the same page produce different descriptions — because the passage that answers this search is more useful than a generic summary written months ago.

The consequence is counter-intuitive but freeing. Your best route to a good snippet is not a perfectly-tuned description tag — it is a page containing clear, quotable passages that directly answer the questions people are actually searching. Write those, and Google will find them and use them. That is also, not coincidentally, exactly what makes a page quotable by an answer engine.

Write the description anyway. It is the fallback, it is what social platforms use if no og:description exists, and it costs five minutes. Just do not mistake it for a lever on rankings, and do not be alarmed when Google ignores it. And treat the "142 characters, good length" tick with care: within the pixel budget is a necessary condition, not a good description. Length says nothing about whether the sentence is worth reading.

The FAQ rich result in that second panel — read this first

The panel showing three expandable questions is a preview of what FAQ markup used to produce. It is worth knowing what changed before you build for it.

Google restricted FAQ rich results in 2023 to a narrow set of authoritative government and health sites. For an ordinary business or blog, adding FAQPage markup no longer produces that expanded dropdown in the SERP. HowTo rich results were removed entirely at the same time.

Is FAQ markup therefore worthless? No — but be precise about what it now buys. It no longer earns a SERP enhancement for most sites. It does still state, unambiguously and machine-readably, that this text is a question and that text is its answer, which is exactly the structure retrieval systems parse when assembling an answer. The SEO justification has largely gone; the AEO one has not.

habit

Check the feature exists before you build for it

SERP features are added, restricted and withdrawn. Confirm in Google's current documentation that a feature still exists and that your site type is still eligible, before spending a day on markup for it. This is how sites end up with elaborate schema that has done nothing for two years.

What the preview cannot show you

A snippet preview renders your listing in isolation, on a white background, at the top of the page. That is not where it will appear. The gap between the two is where most CTR expectations go wrong.

The most useful thing you can do with a snippet preview is not look at it in isolation. Run the query, screenshot the real SERP, and place your snippet among its actual neighbours. The question is never "is this a good title" — it is "would I click this one rather than the one above it".

Frequently asked questions

What is the pixel width limit for title tags?

Google displays title tags up to approximately 600 pixels wide in desktop results and slightly narrower on mobile. This typically equates to 50–60 characters depending on the characters used. Wide characters like W and M use more pixels than narrow characters like i and l. The SERP Preview tool measures pixel width, not just character count.

Can I control how Google shows my SERP snippet?

You can influence the snippet with your title and meta description tags, but Google may rewrite them if it determines alternatives better match the user's query. Ensure your title is descriptive and includes the primary keyword. Keep meta descriptions informative and within the pixel limit. Use structured data to enable rich snippets.

What are rich snippets in SERP previews?

Rich snippets are enhancements to standard SERP listings — star ratings from aggregateRating schema, price ranges from Product schema, FAQ dropdowns from FAQPage schema, dates from Event schema. The SERP Preview tool shows how these appear overlaid on your standard snippet, helping you visualise the impact of adding schema.

Why did Google change my title?

Because it judged your title unsuitable for the query, which it does on a large proportion of results. It then draws a replacement from your H1, prominent on-page text, anchor text pointing at the page, or og:title. Rewrites are usually triggered by titles that are keyword-stuffed, boilerplate across every page, too vague, or that promise something the page does not deliver. The way to keep your title is to write one Google has no reason to replace — descriptive, specific, accurate, and consistent with the H1.

Does the meta description affect rankings?

No. Google has been explicit about this for years — keywords in it do not help you rank, and a page with no meta description at all can rank first. Google also replaces it most of the time, lifting a passage from the page that matches the specific query, which is why the same page shows different descriptions for different searches. Write one anyway as a fallback, but your real route to a good snippet is a page containing clear, quotable passages that answer the questions people search.

Should I add FAQ schema to get the expandable dropdown?

For most sites that dropdown is no longer available. Google restricted FAQ rich results in 2023 to a narrow set of authoritative government and health sites, and removed HowTo rich results entirely. FAQPage markup still has value — it states unambiguously that this text is a question and that text is its answer, which is the structure retrieval systems parse — but the SERP enhancement is not coming. Check Google's current documentation before building markup for any specific SERP feature.

My snippet looks perfect but CTR is poor. Why?

Because a preview renders your listing in isolation and that is not where it appears. Look at what sits above you — an AI Overview, a local pack, ads, People Also Ask — which on many queries push the first organic result below the fold entirely. Look at what sits beside you: your title does not need to be good, it needs to be better than the nine alternatives on the same screen. And check the date shown in the snippet, since on any query with a recency expectation a visibly old date deters clicks more than a weak title does. Run the real query and place your snippet among its actual neighbours.

Related Demo Reports

Run SERP Snippet Preview on Your Own Site

Get your real audit with specific issues, fixes and improvements — free to start.

⚡ Run Free Audit View Plans