Schema generator (JSON-LD)
Fill in the fields and generate structured data code ready to paste on your site. From FAQ and article to page, website, product and service. No sign up, right in your browser.
Generated code
Paste this code in your site's <head>.
<script type="application/ld+json">{
"@context": "https://schema.org",
"@type": "FAQPage"
}</script>Everything about schema, JSON-LD and structured data
The schema generator creates the JSON-LD code that describes your content to search engines and AI assistants. You fill in the fields, copy the ready code and paste it on your site. Structured data is how you talk to Google in its own language: instead of guessing what is on the page, it gets the answer already organized.
What structured data and JSON-LD are
Schema is a markup vocabulary created by Schema.org to describe what a page contains, such as an article, a company, a product or a list of questions. JSON-LD is the format Google recommends for that markup. It is a code block separate from the visible content, which makes it easy to generate, read and maintain without touching the page layout.
JSON-LD, microdata and RDFa
There are three structured data formats, but JSON-LD won. Microdata and RDFa sit scattered inside the visible HTML and break easily. JSON-LD lives in a single <script> block, separate from everything else. Google names JSON-LD as its preferred format, and that is the one to bet on.
Why it helps rich results and getting cited by AIs
Structured data does not change your ranking directly, but it gives context to the search engine, and that changes what shows in the result. With the right markup, Google can display rich results, such as review stars, questions that expand in search, product price or company details. These formats take up more space, stand out and tend to raise your click-through rate.
The newest gain is AI. Tools like ChatGPT, Perplexity and Google's AI Overviews read the markup to understand who answers a question and with what authority. Marking up your content with schema is now one of the foundations of GEO and AEO, the optimization for generative and answer engines. Content that is structured has a better shot at being cited by AI than content left loose in plain text.
- Rich results: stars, expandable FAQ, price and company details right in Google.
- More clicks: a richer result takes up space and draws the eye.
- GEO and AEO: AI assistants understand and cite structured content better.
- Clear context: the search engine stops guessing and starts knowing what each thing on the page is.
Where to paste the JSON-LD on your site
The JSON-LD goes inside a <script type="application/ld+json"> tag, ideally in the HTML <head>. You can also place it in the <body>, since Google reads it in both. Use one block per page, with the schema type that describes that page, and keep the markup faithful to the visible content: marking up something that does not appear on the page breaks the guidelines.
Schema types and when to use each
| Schema type | When to use |
|---|---|
| Article | Blog posts, news and articles. |
| WebPage | Standard and institutional pages of your site. |
| WebSite | The site as a whole, with the sitelinks search box (goes on the home). |
| FAQPage | Pages with frequently asked questions and answers. |
| Organization | Company details, logo and social profiles. |
| LocalBusiness | Businesses with a physical address and local service. |
| Service | Pages for a service you provide. |
| Product | Product pages with price and reviews. |
| BreadcrumbList | Navigation trail across pages. |
| HowTo | Tutorials and step-by-step guides. |
The structure of each schema, explained
The generator covers eight schema types. Here is what each one describes, its main properties and where to use it.
FAQPage (FAQ)
Describes a frequently asked questions page. The mainEntity property holds the list of questions, each a Question with the question text in name and the answer in acceptedAnswer (an Answer with a text property). Use it on pages that gather questions and answers, and it is what can expand the FAQ right in Google's result.
Article
Describes a blog post, a news story or an article. Its main properties are headline (the title), author (a Person with name), datePublished, image and description. Use it on any editorial content so Google understands authorship and date.
WebPage (Page)
Describes a standard or institutional page, such as About, Contact or a content page. It gathers name (the page title), url, description and primaryImageOfPage. It is the most generic type, handy when the page is not an article, a product or a service.
WebSite (Website)
Represents the whole site rather than a single page, so it goes on the home page. It has name, url and description and, optionally, a potentialAction of type SearchAction, with target (an EntryPoint plus urlTemplate using {search_term_string}) and query-input. That SearchAction is what can enable the sitelinks search box in Google's results.
Organization
Describes the identity of your company or brand. Its properties are name, url, logo and sameAs (the list of your social media URLs). Use it to tie the site to the company entity and reinforce the brand in results.
LocalBusiness (Local business)
It is the organization variant for businesses with a physical address and local service. Beyond name, url and telephone, it carries an address of type PostalAddress (with streetAddress, addressLocality and addressCountry). Use it for shops, restaurants, clinics and any business that serves a location.
Product
Describes a product for sale. It has name, image, description, brand (a Brand) and offers of type Offer, with price, priceCurrency and availability. It is the offers with price that enables the price rich result in search. Use it on product pages.
Service
Describes a service you provide rather than a physical product. It gathers name, serviceType, description, provider (an Organization), areaServed and url. Use it on pages that present a service, such as consulting, maintenance or design.
How to validate the schema
After pasting the code, always validate before trusting it. Google's Rich Results Test shows whether your page is eligible for rich results and flags errors and warnings. The Schema.org Validator checks that the syntax is correct. Paste the published URL or the code directly, fix anything that shows in red and only then consider the schema done.
Quick checklist before publishing
- One JSON-LD block per page, with the right schema type.
- The markup reflects what is visible on the page, with no invented data.
- Required fields for each type filled in.
- Validated in the Rich Results Test, with no errors.
Common questions about the schema generator
Is the schema generator free?
Yes. It is 100% free, no sign up and no usage limit. Everything runs in your browser.
Do I need to know how to code?
No. You fill in the fields, the tool builds the JSON-LD and you just copy and paste it on your site.
Where do I paste the generated code?
Inside a <script type="application/ld+json"> tag in your site's <head>. The tool delivers the code with that tag ready to copy.
Does structured data improve my ranking?
It does not change your position directly, but it helps Google understand the page and show rich results, which usually increases clicks.
How do I test if the schema is correct?
Use Google's Rich Results Test or the Schema.org Validator. Paste the URL or the code and check for errors.
Does schema help me show up in AI answers?
Yes. Assistants like ChatGPT, Perplexity and AI Overviews read structured data to understand and cite content. Marking up the page with schema is one of the foundations of GEO and AEO.
Want a blog that generates the schema for you?
Automarticles builds your full blog, with content optimized for Google and to be cited by AIs like ChatGPT. Every article ships with the right structured data, with no manual work.