Paste JSON-LD or Microdata and see how rich results render for recipes, products, events, FAQs, and how-to cards.
You paste the structured data from your page, either a JSON-LD script block or the HTML that carries the Microdata attributes, and the tool detects the schema.org type it declares, one of recipe, product, event, FAQ page, or how-to, and renders the preview card for that type. The surprise most people hit: a clean preview means the markup parses into a recognizable type, not that Google will show the result. Google runs its own eligibility checks, which change over time and which no third-party preview replicates.
A concrete input and expected output from the current implementation.
Input
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Bamboo Desk Organizer",
"image": "https://example.com/images/bamboo-organizer.jpg",
"description": "Three-tier organizer with a drawer and cable slot.",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "12"
},
"offers": {
"@type": "Offer",
"price": "129.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
} Expected output
The tool detects @type Product, parses the nested AggregateRating and Offer, and renders a product preview card: name 'Bamboo Desk Organizer', a 4.5-star rating, '12 reviews', price $129.00, and availability 'In stock'. The description fills the card's text slot, the image URL its image slot.
The card is built from the markup: ratingValue 4.5 and reviewCount 12 from aggregateRating, price 129.00 with currency USD from offers, and InStock mapped to 'In stock'. A missing or misspelled property leaves its slot empty rather than failing the parse.
The parser scans the pasted text for a schema.org type declaration: the @type property in JSON-LD or the itemtype attribute in Microdata. It reads the properties that type expects, including nested ratings and offers, and maps each onto the preview template. A property the template expects but the markup lacks leaves its slot empty, so a half-blank card usually means a misspelled name or a wrongly nested object.
The card mimics the layout conventions search engines use for that rich result type: star rating and review count for products and recipes, an expandable question list for FAQ pages, and date and location lines for events. That rendering is the tool's model of search results, not a check against a search engine's current eligibility rules, which differ between engines and change over time.
Probably nothing in the markup. The preview proves the snippet parses into a known type; Google's decision to display it depends on its own guidelines and review process, which no third-party preview replicates. Run the page's URL through Google's Rich Results Test for the check that matches its actual requirements.
No. A fully populated card means the fields were recognized, not that the markup conforms to schema.org or to a search engine's requirements. schema.org is a descriptive vocabulary; engines layer their own mandatory fields and policies on top. For spec-level conformance use the schema.org validator, and for Google's rules use the Rich Results Test.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.