SERP Snippet Previewer
See the exact result Google will render — standard, FAQ, review, product, video, event or breadcrumb — before you publish it.
Snippet type
Pick the rich result you are aiming for. Your inputs are kept when you switch.
A standard result has nothing to add beyond the fields above. Switch type to layer a rich result on top of it.
Google preview
Your title tag will appear here
The title and description are cut at the measured pixel width, the way Google truncates a desktop result.
How to use it
- Choose a snippet type, then fill in the title, URL and description. The preview updates as you type — there is nothing to submit.
- Already published, or copying a competitor? Use Fetch from URL. The page is read server-side, and any FAQ, product, video, event or breadcrumb markup on it pre-fills the matching type.
- Check desktop and mobile separately. Desktop cuts the title at its measured pixel width; mobile wraps to two lines instead, so the same title behaves differently on each.
- Copy the preview as an image or download it as a PNG when you need to put the snippet in a brief, a ticket or a client deck.
Earning the click, not just the ranking
- Keep titles under about 580 pixels — roughly 55–60 characters — or the tail gets cut. Front-load the term you want to rank for so the half that survives is the half doing the work.
- A rich result is worth more than a better title. FAQ rows, star ratings and video thumbnails all take vertical space away from the results below you, and space is what CTR is made of.
- Star ratings and prices come from markup Google trusts, not from what you type here. This tool shows you what the result would look like; Schema.org markup on the page is what makes it happen.
- Breadcrumb markup replaces the URL slug with a readable trail. It is one of the few rich results Google shows almost universally, and one of the cheapest to add.
- Google rewrites titles on roughly a third of queries and descriptions on more than half. Preview what you control, then write something specific enough that rewriting it would make the snippet worse.
Frequently asked questions
What are rich snippets in Google?
A rich snippet — Google now calls them rich results — is an ordinary search result with extra detail attached: star ratings, a price, a video thumbnail, expandable questions, a breadcrumb trail. Google builds them from structured data on the page, usually Schema.org markup in JSON-LD, and it only shows them when it both understands the markup and judges it useful for that query. The markup is a request, never an instruction: a page can be perfectly marked up and still render as a plain blue link.
How do I get star ratings in search results?
Add AggregateRating or Review markup to the page and make sure the ratings it describes are genuinely visible to visitors — Google checks. The important restriction is that self-serving reviews do not qualify: since 2019, ratings you have written about your own Organization or LocalBusiness are ignored, so a business cannot star-rate itself. Ratings attached to products, recipes, courses, books, software and events are the ones that do earn stars, and they earn them only when the review data is real, on-page and matched to the entity being rated.
Does Google always show FAQ rich results?
No, and for most sites it now never does. In August 2023 Google restricted FAQ rich results to well-known, authoritative government and health websites, so a normal commercial or editorial site with valid FAQPage markup will simply not get the expandable rows any more. The markup itself is still valid and still helps machines parse the page, and this preview still renders the FAQ layout so you can see what the treatment looks like — but treat it as a historical or eligible-site view rather than something you should expect on a new page.
Can I control how my site appears in Google?
You control the inputs, not the output. The title tag, meta description, canonical URL, favicon and structured data are all yours to set, and Google starts from them. It then rewrites freely — pulling a title from an H1 or a link's anchor text, or a description from whatever passage on the page best answers the query. You can rule some things out with directives like nosnippet, max-snippet and nositelinkssearchbox, but there is no way to force a specific snippet. The practical strategy is to make your own version the best available answer so there is nothing better to substitute.