See how a page would look as a Google search result, then paste its JSON-LD to visualize FAQ, HowTo, Review, Product, Recipe, Event, and Breadcrumb rich results before anything goes live.
The preview scales to fit your screen. Measurements refer to its internal pixel preset. Google may rewrite text, choose another favicon, or show different features.
Cards reflect recognized fields in your markup. The inspector checks up to 1,000 objects and displays up to 100 matching items. They do not confirm eligibility or guarantee a Google rich result.
Import a page with structured data, paste JSON-LD, or try the example.
FAQ and HowTo rich results are retired in Google Search. Their cards are markup inspections only. Review the current rules before relying on any rich result.
Open Google Rich Results TestStep-by-step
Five steps from a URL or a blank form to a reviewed, checklist-passed preview.
Paste a published page's URL and click "Import from URL" to pull in its current title, description, and any JSON-LD schema it already has. or skip this and fill in the fields yourself.
Compare title wrapping and description clipping in both device presets. Review pixel measurements rather than judging length from character counts alone.
Paste the exact contents of a <script type="application/ld+json"> block. your own, or the output straight from the Schema Markup Generator. to see which rich result types it would render.
For FAQ, Review, and HowTo markup especially, confirm every piece of marked-up content is something a visitor can actually see and read on the live page. not just present in the schema.
Once published, run the URL through Google's Rich Results Test or URL Inspection tool. the final word on eligibility is Google's, not any preview tool's.
Before you trust the preview
Check the Google structured data guidelines before publishing. Our cards illustrate data fields, including older formats. They do not certify eligibility for a current Google Search feature.
Two titles with 55 characters can have very different widths. Wide capitals take more space than narrow letters. Compare the measured width and visible lines, then put the most useful words early.
Our desktop preset uses 600 pixels for the title and two 480 pixel description lines. Mobile uses 340 pixel lines. These are adjustable viewing contexts through device selection, rather than official Google limits.
Read our guide to writing meta titles with AIExplain what the page offers and why it helps. Avoid repeating the title word for word. Preview optional dates because they use space that could otherwise show descriptive text.
A description can fit this preset and still be rewritten or shortened in search. The query and device influence the final snippet.
Read our meta description guideUse the prominent Import from URL button to load a public page. Switch off the body scan for a quicker metadata check. Keep editing without importing again. Recent successful imports may be reused for five minutes.
Some websites block automated requests or add metadata through JavaScript. Enter the fields manually when the returned HTML does not contain the expected information.
The inspector can display several recognized items from one page. Each card reflects its own fields. FAQ and HowTo cards remain useful for inspecting older markup, although Google has retired both rich result displays.
Check current Google Search feature updatesGoogle does not always use your title
Google sometimes rewrites the displayed title or description based on the query, even when valid meta tags are present. This preview shows what you are providing, not a guarantee it is what gets shown.
Valid markup ≠ guaranteed rich result
Technically valid JSON-LD is necessary but not sufficient. Google applies its own content-quality and eligibility criteria per rich result type, and can choose not to show one even for perfectly valid markup.
Markup must match visible content
FAQ and Review markup is only meant for Q&As and reviews an ordinary visitor can actually see on the page. Markup for content that is not genuinely present is a structured-data policy violation, not just a wasted effort.
Common questions
No. Google truncates title links to fit the device. This simulator uses a 600 pixel desktop title preset as a practical estimate. Mobile uses a narrower layout with more lines. Font, query, and search features can change the result.
Letters have different shapes and widths. A capital W uses more space than a lowercase i. The simulator measures text using browser fonts and checks line wrapping. Character counts remain available as a reference.
Yes. The importer keeps page metadata and selected structured data without downloading images or videos. Quick import stops after the page head. The full scan checks up to 8 MB and reports when later markup may be missing.
No. These optional layouts illustrate visual emphasis and space above organic results. They do not retrieve an AI answer, predict clicks, or measure eye movement. Country selection provides preview context rather than local ranking data.
Save a PNG image, copy escaped metadata HTML, or copy a share link. Share links contain the preview content, so send them only when that content can be shared. Image exports use a site initial instead of external favicons.
Preview your title, URL, and description, or inspect the structured data you provide. Import a public page to start with its existing metadata. Previews are illustrative, and actual search appearances can differ.
This tool recognizes FAQPage, HowTo, Review, AggregateRating, BreadcrumbList, Article, Product, Recipe, and Event. If your markup uses a different type, or the recognized fields are empty, nothing renders. That doesn't necessarily mean the markup itself is invalid.
No. This is an illustrative preview of what your markup describes, not a guarantee. Google applies its own content-quality and policy checks per rich result type, and the final authority is Google's own Rich Results Test and Search Console.
Yes. Paste the JSON-LD it generates directly into the Structured data editor to see how it would render before you publish it.