JSON-LD generator
Structured data for articles, products, organisations, FAQs and breadcrumbs.Headline
Image URL
Author
Published (YYYY-MM-DD)
Publisher
All checks pass
- Note: Test the result with a structured-data testing tool before shipping.
- Pass: All required properties for Article are present.
Paste into <head> or <body>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How we made utilyx private by default",
"image": [
"https://utilyx.dev/blog/private.png"
],
"datePublished": "2026-11-20",
"author": {
"@type": "Person",
"name": "Ada Lovelace"
},
"publisher": {
"@type": "Organization",
"name": "utilyx"
}
}
</script>
What it’s good for
Help search engines understand your pages.
- Rich resultsProducts with prices, articles with dates and authors.
- Brand detailsOrganization markup with logo and profiles.
- NavigationBreadcrumbs that match your site structure.
Questions
The short answers.
Where does the script go?
Anywhere in the HTML, usually the head.
Does markup guarantee rich results?
No. It makes pages eligible; search engines decide.
Can I add several types?
Yes. Use one script per type, or combine them in an @graph. This tool builds one type at a time, so paste one script tag for each.
Does the markup have to match the page?
Yes. Structured data must describe content visitors can see on the page. Markup for prices, questions or reviews that aren't shown can be ignored or count against the page.
Why are some characters written as \u003c?
The < character is escaped in the JSON so text like </script> can't end the script block early. JSON parsers read \u003c as <, so the data is unchanged.