Load tags from a URL
Pull the current title and meta description from any public page in one click, so rewriting an existing snippet starts from what is actually live rather than a copy and paste.
Type a title and meta description, watch the Google result rebuild as you write, and see exactly where each line gets cut on desktop and on mobile.
Pixel width measured in Arial, the metric Google truncates by rather than character count.
Load any live URL to pull its current tags, then rewrite them against the budget.
Type the title, description, and URL, watch the meters, then switch devices before copying the tags.
Paste any URL into the load field to pull that page's current title and meta description straight into the editor, which is the quickest way to rewrite an existing snippet. Leave it empty when you are drafting a page that does not exist yet.
Enter the title exactly as it will appear in the head of the page. The meter below shows rendered pixel width against the budget for the selected device, alongside the character count, and the preview cuts the line where Google would cut it.
Add the summary you want searchers to read. Google rewrites descriptions often, but a description that fits the budget and answers the query is far more likely to survive intact and earn the click.
The URL builds the site name and the breadcrumb trail Google shows above the title. Path segments appear separated by arrows, so a long or messy slug becomes visible in the result before anyone searches for the page.
Switch between the two devices, since mobile allows a wider title budget than desktop and cuts descriptions later. Once both fit, copy the title, the description, or the whole block of meta tags into your template or CMS.

Pull the current title and meta description from any public page in one click, so rewriting an existing snippet starts from what is actually live rather than a copy and paste.
The result rebuilds on every keystroke with the favicon row, site name, breadcrumb path, blue title, and grey description that Google renders today.
Both lines are measured in Arial at the sizes Google renders, because results are truncated by width and never by character count, with a colored meter showing the exact pixel and character totals.
Each device gets its own title and description budget, so you can catch a snippet that reads fine on one screen and breaks on the other.
The URL turns into the site name and breadcrumb trail, and an optional published date renders in front of the description the way Google shows it for articles.
Copy the title alone, the description alone, or a block containing the title tag, the description meta tag, and a canonical link ready for the head.
These notes cover where the snippet is measured and rendered, which single step uses a server, what happens to the draft when the tab closes, and whether any account is involved.
Titles and descriptions are measured in the open page with the same Arial sizes Google renders, then cut at the pixel budget for the selected device. Loading a live page is the only step that uses a server, and it stops reading at the closing head tag.
Typed titles, descriptions, URLs, and the chosen date stay in current tab state only. A loaded page is held in a brief shared cache and nothing is written to an account.
Writing a snippet, switching between desktop and mobile, and copying the finished meta tags all work without an account or any sign-in step.
A preview is a close model of a Google result, not a promise about what searchers will finally see.
Google replaces the meta description on a large share of queries with text pulled from the page body.
It also rewrites titles when the tag is keyword stuffed, boilerplate heavy, or a poor match for the query.
Pixel budgets are close approximations based on the Arial sizes Google renders in a standard result.
Real results shift with the browser, the device width, the language, and the search features shown around them.
Sitelinks, ratings, prices, dates, and FAQ rows can push or reshape a snippet in ways no preview reproduces.
Treat a comfortably fitting snippet as the goal rather than one that sits exactly on the limit.
Loading a URL reads the tags a server sees, so tags injected by client-side scripts will not appear.
Deploy the tags, then confirm the live result in a search or in Search Console after Google recrawls the page.
SERP Preview Tool measures the title and description in the browser using canvas text metrics, and loading a live page reads only as far as the closing head tag before stopping the download.
Aim for roughly 50 to 60 characters, but width matters more than count. A title full of wide capitals can break at 52 characters while a narrow one survives past 65, which is why this tool measures rendered pixels instead.
Around 150 to 160 characters fits a desktop result comfortably. Mobile allows more, so a slightly longer description can still work if the first sentence carries the important part and reads well on its own.
Search results use a proportional font, so a lowercase letter such as i is far narrower than an uppercase W. Google fills a fixed container width, which means two titles with the same character count can truncate at very different points.
Not always. Google rewrites descriptions on most queries and adjusts titles when the tag is a weak match for the search. A clear, specific, query relevant snippet is the best way to make the version you wrote the one that appears.
Mobile results render in a narrower column but allow the title to wrap over more lines, so the total budget is larger. Descriptions also run longer before being cut, which is why a snippet should be checked on both.
What you type is measured and drawn entirely inside your browser tab. Only the optional load step contacts a server, and it fetches the page you name rather than sending anything you have written.
Very little. Titles and meta descriptions sit in the head, so the transfer is stopped as soon as the closing head tag arrives. On most pages that is a few kilobytes rather than the whole document.
4.8 (311 ratings)