Free Tool · Analyzer

Google SERP Preview

See how your title and description render on Google desktop, mobile, and as a social card — with real pixel-width truncation.

Import from a URL (optional)

We fetch the page server-side and parse the <head> for title, description, canonical, Open Graph, and Twitter card tags. URLs pointing to private / internal IPs are blocked.

Edit

Title

Aim for 50–60 visible characters. The pixel meter on the right shows the exact Google truncation point.

Meta description

130–155 characters. Read like ad copy — what's the page about, why click.

URL

Used for the breadcrumb display in the Google preview.

og:image URL

Image used for X / Twitter / Facebook / LinkedIn preview cards. 1200×630 PNG/JPG recommended.

og:site_name

twitter:card

Override og:title / og:description (optional)▼

og:title

Overrides title on social cards only. Defaults to page title if empty.

og:description

Overrides description on social cards only.

Google · Desktop SERP

rankrize.io › feed › ai-search-optimization

How to Rank in AI Search Engines in 2026 — A Practical Guide | Rankrize

A complete walkthrough of GEO (Generative Engine Optimization) for ChatGPT, Claude, Perplexity, and Google AI Overviews. Real tactics, real outcomes.

Title0 / 580 px

Description0 / 990 px

Automate it with Rankrize

Tired of writing meta for every page?

Rankrize writes pixel-tested titles and meta descriptions on every article — validated against this same renderer. Run a free site analysis to see how we'd rewrite your existing meta tags.

Run free site analysisOne free per account · No credit card

How to use

How to use the Google SERP Preview

Truncation is by pixels, not characters
Google measures titles in pixels — Arial 20px on desktop, with about 580 px of width before the '…' kicks in. A title with capital letters and wide characters (W, M, capital letters) hits the limit much earlier than one with mostly lowercase narrow characters. The pixel meter in this preview uses canvas measureText — the same primitive Google uses — so the truncation you see is what searchers will actually see.
Test on mobile too — it's a different limit
Mobile SERPs use Arial 16px with ~540 px max width. Many titles that look fine on desktop get cut off on mobile. Switch to the Mobile tab and confirm both layouts before shipping. With mobile traffic now 60%+ of most sites, the mobile preview is arguably the more important one.
Paste a live URL to see what Google sees right now
Use the URL importer to fetch your existing meta tags from any public URL. Useful for: comparing your title to competitors before re-writing, auditing all pages on a site systematically, or showing a client what their current snippet looks like before you fix it.
Watch the Twitter and Facebook tabs separately
X / Twitter and Facebook / LinkedIn each have different aspect ratios for og:image. A 1200×630 image works for both. Square images (1:1) get cropped on Facebook. Tall portrait images get cropped on both. The Twitter tab also distinguishes summary_large_image (full bleed) vs summary (small thumbnail).
When Google rewrites your title, look at your H1
If Google's actual SERP doesn't match the title you set, Google has rewritten it. The most common rewrite source is your <h1>. Match your title intent to your H1 — and make both clearly describe the page (not the brand). Generic titles like 'Home — Acme Inc' get rewritten the most aggressively.
Use the brand suffix carefully
Adding ' | Brand Name' at the end of every title eats 15–25 px of your title budget. For competitive keywords, that's 5–8 characters that could've been keyword. Smart pattern: lead with the page benefit, end with the brand only when there's room. Some pages drop the brand entirely if the keyword is competitive.

Frequently asked questions

About the Google SERP Preview

Two ways. (1) Type or paste your title, description, URL, and og:image into the form on the left. (2) Paste a live URL into the importer at the top — we fetch the page, parse its <head>, and pre-populate the form with what Google currently sees. The preview on the right updates live on every keystroke and uses pixel-accurate measurement (canvas measureText with Arial fonts) so the truncation matches what Google actually shows in real search results.

Google rewrites titles when its analysis suggests something else (your H1, anchor text from inbound links, or page content) is more relevant to the user's query. Common rewrite triggers: titles that look keyword-stuffed, titles that don't match the page content, missing/generic titles, repeated brand suffixes. To minimize rewrites: write descriptive page-specific titles, match the H1, avoid keyword stuffing, and put the brand only when there's space.

<title> is what Google's SERP and the browser tab use. og:title is what Facebook, LinkedIn, Slack, Discord, iMessage use. twitter:title is what X / Twitter uses. Twitter falls back to og:title when twitter:title isn't set; og falls back to <title>. So you can set just <title> if all three should be the same — or override og:title and twitter:title for richer social copy.

Pixel width. Google uses ~580 pixels of width on desktop SERPs (Arial 20px) and ~540 pixels on mobile (Arial 16px). A title with mostly lowercase narrow characters can be 70+ characters before hitting the limit; a title in all caps may hit it at 50. The pixel meter on the right of this tool measures with canvas — the same primitive Google's renderer uses.

No — this tool is read-only and preview-only. It shows you what Google + social cards would render based on the meta tags you provide; it doesn't modify anything on your site. To actually deploy these tags, paste them into your page's <head> using the Meta Tag Generator, or have your CMS handle them.

Most likely: (1) the URL needs to be absolute (https://...), not relative (/img.png). (2) the image needs to be publicly accessible (not behind login). (3) the image needs to be valid (PNG / JPG / WebP — SVG sometimes doesn't render). The social preview here uses your provided URL directly — if it doesn't render here, it won't render on Twitter or Facebook either.

Yes — completely free. No sign-up, no rate limits, no ads. Your input never gets stored on our servers (the URL importer makes a one-shot fetch and discards the result). We pay for hosting because the paid Rankrize platform (rankrize.io) automates this kind of validation across hundreds of articles per month.

More free tools

The full Rankrize free toolkit

Schema Markup Generator

Generate validated JSON-LD schema markup for 9 types — paste-ready for your site.

You're here