Tools

Fields

Output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your article headline",
  "description": "A short description of the article."
}
</script>

Why structured data matters

JSON-LD is how you tell Google what a page actually contains, beyond what it can infer from HTML. It is the difference between a plain blue link and a rich result: star ratings on a product, an FAQ dropdown directly in the search results, or a byline and publish date on an article. None of it is guaranteed to render, Google decides that, but without valid markup it is not even in the running.

Where to put it

Render structured data server-side, not with a useEffect or a tag manager that fires after the page loads. Googlebot does not reliably wait for client-side JavaScript to run before it reads the page, so client-injected JSON-LD can be invisible to the first crawl. In Next.js, that means rendering the <script> tag from a Server Component, the same way this tool's own page schema is rendered.

Validate before you ship

Paste the output into Google's Rich Results Test before publishing. A field that looks fine here can still fail Google's stricter validation, particularly for Product schema, where a missing price or availability value silently disqualifies the whole block from rich results.