Why measure by pixels instead of character count?

Google truncates titles and descriptions by rendered pixel width, not by character count. Wide letters (W, M, all capitals) take much more space than narrow ones (i, l). Two titles of identical character count can render very differently — one fits, one truncates. We render the text on an HTML canvas in the same font (Arial-style) and weight Google uses, then compare to the actual pixel budgets (≈580px desktop, ≈420px mobile).

Does this tool simulate exactly what Google shows?

It closely mirrors Google's snippet layout — pixel-measured truncation at ≈580px desktop title, ≈990px desktop description, ≈420px mobile title, ≈690px mobile description. The exact display varies slightly by device, browser font rendering, query context, and rich result features. Treat the tool as a tight upper bound — if our preview shows truncation, Google almost certainly will too; if it shows a fit, you have a small safety buffer.

Is my content stored or sent anywhere?

No. Everything runs in your browser. Your title and description text never leaves your device — there is no server upload, no login, and no tracking on the snippet contents.

What is the ideal meta title length?

Google typically displays 50–60 characters before truncating. Aim for your primary keyword near the start and keep the total under 60 characters to avoid the truncation ellipsis in search results.

What is the ideal meta description length?

Around 120–160 characters. Shorter descriptions may be expanded by Google; longer ones get cut off. Include your target keyword naturally and end with a clear value proposition or call to action.

Can I test multiple pages at once?

The tool previews one page at a time. Paste your title and description, preview, adjust, then repeat for each page. There is no limit on how many pages you can check in a session.

Why does Google sometimes show a different title than what I set?

Google rewrites titles when they think the rewrite better matches user intent. Common triggers are very long titles, missing query keyword, generic phrases like 'Home' or 'Untitled', and aggressive keyword stuffing. Write descriptive, query-relevant titles to minimize rewrites.

Should I include the current year in titles?

Yes for content where freshness signals matter — guides, lists, comparison posts, year-tagged tutorials — and update yearly. For evergreen tool pages or product pages, omit the year so the title doesn't appear stale.

Is the SERP layout the same in all countries?

Mostly yes within English-speaking markets. Some countries (Japan, China) and non-Latin scripts may render slightly differently due to character width. Bing, Yandex, and Naver use different layouts entirely and require separate previews if those markets matter to you.

Will Google strip emojis from my title?

Sometimes. Google retains some color emojis that match query intent (food emojis on recipe queries, for example) but strips many decorative emojis it judges irrelevant or rendered inconsistently across devices. If your title's value depends on the emoji being shown, write a fallback that works without it — and remember emojis cost roughly the width of an uppercase letter in pixel budget.

Are 2026 title and description length rules different from a few years ago?

The pixel budgets have stayed roughly stable (≈580px desktop title, ≈990px description), but Google's appetite for rewriting titles has grown sharply since 2021 and continued through the AI-generated search era. Today, expect titles to be rewritten if they're too long, too generic, missing the query phrase, or stuffed with keywords. The defensive move is the same as always: write a clear, query-relevant title within the pixel budget and let Google honor it.

Web 与 SEO属于 Web 与 SEO 工具 →

Meta 标题和描述预览

预览页面标题和描述在搜索结果里的基础呈现方式。

数据留在您的设备无需上传至服务器可离线使用

标题描述显示链接

标题宽度 · 桌面

✓ 符合

描述宽度 · 桌面

✓ 符合

标题宽度 · 移动

✓ 符合

描述宽度 · 移动

✓ 符合

搜索结果预览

桌面预览

toolgrid.app/tools/url-parser

Utility tools for everyday web tasks

A clean index of browser-based utility tools.

移动端预览

toolgrid.app/tools/url-parser

Utility tools for everyday web tasks

A clean index of browser-based utility tools.

富结果（Rich result）提示

富片段（FAQ、面包屑、站内链接、评分）来自页面里的 JSON-LD，跟 snippet 文本本身无关。要被收录：FAQ 页加 FAQPage schema、层级页加 BreadcrumbList、产品页加 Product/Review、教程页加 HowTo。上线前用 Google 的 Rich Results Test 校验一次。

为什么用这个工具

一边写标题和描述，一边查看长度和搜索摘要预览。

适合发布前快速检查标题长度、描述长度和摘要语气。

它是规划预览，不代表搜索引擎一定按这个样式展示。

如何使用

01填写标题、描述和展示链接。

02查看长度统计和预览卡片。

复制前快速检查

先确认输入格式符合你的预期。

在把结果用于文档、链接、配置或消息前快速扫一眼。

只复制你真正需要的输出。

常见问题

这能保证 Google 按同样文案展示吗？

不能，它只提供一个接近搜索结果的本地预览。

Meta 标题和描述预览

搜索结果预览

富结果（Rich result）提示

为什么用这个工具

如何使用

复制前快速检查

常见问题

相关工具

seo preflight workspace

snippet workspace

Canonical 检查器

搜索结果预览

富结果（Rich result）提示

Meta 标题和描述预览

seo preflight workspace→

snippet workspace→

Canonical 检查器→

seo preflight workspace

snippet workspace

Canonical 检查器