JSON-LD generator
Fill in a few fields and get a JSON-LD script block that describes your page to search engines using schema.org vocabulary. Empty fields are left out, and the tool warns about the most common mistakes.
Runs in your browser: nothing you enter is sent anywhere.
How to use it
- Choose Article, FAQ page or Organization.
- Fill in the fields. For an FAQ, write each question on its own line with the answer below it, and separate items with a blank line.
- Copy the script block into your page.
How it works
The tool builds a plain object with @context set to https://schema.org and the chosen @type. For an Article the author becomes a Person and the publisher an Organization. For an FAQ page each item becomes a Question with an acceptedAnswer of type Answer. For an Organization the profile links become the sameAs list. The object is printed as indented JSON inside <script type="application/ld+json">.
Tips
- Use full URLs for images, logos and profiles.
- Use an ISO date such as 2026-01-15 for dates.
- Test the page after publishing; markup that does not match the visible content can be ignored.
Frequently asked questions
Where do I put the code?
Paste the whole script block into the head or the body of the page it describes. Search engines read it from either place.
Will this give me rich results?
Not guaranteed. Valid markup makes a page eligible, but search engines decide what to show, and Google has limited the display of FAQ rich results to a small set of sites. Check the result in Google's Rich Results Test.
Must the markup match what is on the page?
Yes. Search engines expect structured data to describe content that visitors can actually see on the page, such as the real questions and answers or the real article headline.
Why does the output contain <?
If a value contains a less-than sign, the tool writes it as the JSON escape < so text like a closing script tag cannot end the block early. Parsers read it back as the same character.
Which fields are required?
Schema.org itself requires none, but search engines list properties they want for each type, for example headline and author for articles. The warnings point out the missing basics.