Google SERP Preview Tool
See how your page will look in Google results on desktop and mobile before you publish. Renders the title link, breadcrumb URL and snippet with realistic truncation, and highlights query terms the way Google bolds them.

A meta title reads differently in a CMS field than it does on a results page surrounded by six competitors. Enter your title, URL and description to see the rendered result on desktop and mobile, with truncation applied where Google would apply it.
What this tool does
It renders a realistic Google result from three inputs: the title, the URL and the meta description. Switch between desktop and mobile to see how the same text is cut differently. Enter a target query and matching words are bolded, which is how Google actually renders term matches in a snippet and a large part of why one result draws the eye over another.
The rendering uses pixel-width estimation rather than character counting, so a title in capitals truncates where a title in sentence case does not.
A worked example
You have written:
- Title:
Complete Guide to Workflow Automation Software for Small and Medium Businesses in 2026 - URL:
https://example.com/blog/complete-guide-workflow-automation-software-smb-2026 - Description: 210 characters of introduction copied from the first paragraph.
The preview shows the title cut after "Small and", the URL rendered as a breadcrumb reading example.com › blog › complete-guide-workflow-…, and the description cut mid-sentence. Rewriting the title to Workflow Automation Software for SMBs: 2026 Guide fits, keeps the query terms at the front, and reads as a complete thought.
What Google shows, and what it decides for itself
| Element | Who controls it |
|---|---|
| Title link | You propose, Google may rewrite |
| URL breadcrumb | Derived from the URL and any breadcrumb markup |
| Snippet | Generated per query, often not your description |
| Sitelinks | Google, entirely |
| Rich results | Your structured data, if Google trusts it |
Where people go wrong
Treating the preview as a guarantee. It is a planning aid. Google generates snippets per query and rewrites titles when it judges yours unsuitable — the criteria are set out in Google's title link documentation. What the preview does reliably tell you is whether your text fits, and whether it reads well when it does not.
Writing the title for the page and the description for the crawler. Both are read by a person deciding between ten blue links. The description that wins is the one that answers the query, not the one that repeats the keyword three times.
Letting the URL sprawl. A long, deeply nested URL renders as an ellipsis in the breadcrumb, which throws away a free signal of what the page is about. Google's URL structure guidance is worth reading before you settle on a permalink pattern.
Forgetting the description may be ignored entirely. If your page can be summarised better by its body copy, Google will do that. The controls you have over snippet generation — max-snippet, data-nosnippet, nosnippet — are documented in Google's snippet reference.
FAQ
Does the preview match Google exactly?
No preview can, because Google's rendering varies by query, device, locale and result type, and because it may substitute its own title or snippet. The truncation model here is calibrated to be accurate about width, which is the part that is under your control.
Why is my title bolded in places?
Because you entered a target query and those words appear in the title. Google emboldens query terms and close variants in results, and seeing that highlight is a good way to judge whether the important words are actually visible.
Should I write the description at all if Google might replace it?
Yes. When Google does use it — which is often for navigational and branded queries — it is the only sales copy you get. When it does not, you have lost nothing.
Why does mobile show more of the description than I expected?
Mobile results are narrower but taller, so the snippet often wraps to more lines. The trade-off is that the title has less room, which is the opposite of what people assume.
Next steps
Get the lengths right first with the meta length checker, then audit the live page with the On-Page SEO Auditor and check your social cards with the Open Graph preview. Structured data that produces rich results is generated by the Schema Markup Generator.
If the content pipeline behind those pages is the real bottleneck, What Is Workflow Automation is a plain-English starting point.
Want the whole site reviewed rather than one result? Book a discovery call.

Want this built against your real numbers?
A 30-minute call to scope the workflow, agent, or automation you actually need.
More seo tools
All tools301 Redirect Rule Generator
Turn a list of old and new URLs into redirect rules for Apache htaccess, Nginx, Cloudflare or Netlify. Detects redirect chains and loops before you deploy them, and handles bulk migrations from a pasted list.
Canonical Tag Generator
Generate a correct rel=canonical tag from any URL. Normalises the scheme, strips tracking parameters, resolves trailing slash and case issues, and warns about the canonical mistakes that quietly deindex pages.
Content Brief Generator
Generate a complete SEO content brief from any keyword — ready to hand to a writer
Hreflang Tag Generator
Build a complete, reciprocal hreflang set for a multilingual page and export it as link tags, an HTTP header block or XML sitemap entries. Validates language and region codes and adds x-default automatically.
Keyword Clustering Tool
Group any keyword list by search intent and topic — ready for content planning
Keyword Density Checker
Analyse the word and phrase frequency of any piece of content, with one, two and three-word groupings, stop words filtered out, and a flag on anything repeated often enough to read as keyword stuffing.
Have a workflow that's burning hours every week?
Bring me one real bottleneck. I'll tell you whether it's worth automating, and what it would take.