Schema.org's online JSON-LD generator
The tool is suitable for articles, products, companies, local businesses, authors, events, and other pages. The JSON LD generator reduces manual steps, but the resulting markup must still accurately match the page content and search engine requirements.
The structured data generator assembles code from the values the user enters into the form. Each entity requires a different set of fields: a product requires offer characteristics, an article requires the author and dates, and a company requires the name, URL, and contact information.
After filling out the form, the tool generates JSON-LD code with the required Schema.org properties. This code can be copied, validated with a schema validator, and added to the site via a CMS, page template, or server-side rendering.
English-language documentation and services often include queries such as "json ld generator", "schema generator", "schema markup generator", "schema markup generator online", "schema.org generator", "seo schema generator", and "structured data generator". All of these refer to tools that help generate schema markup for specific page content.
In Russian-language search, the terms "json ld generator", "schema org generator", "schema microdata generator", and "structured data generator" are used. The names may vary, but the goal remains the same: to generate correct structured markup for a website's real data.
How to use the Schema.org generator?
First, determine what exactly the page describes: a product, an article, a company, a specialist, an event, or another object. Once you select the type, the corresponding fields will appear, so you don't need to fill in unnecessary information or select an entity just to get the desired snippet.
The workflow is simple: select the type → fill in the data → create JSON-LD → validate → publish. After implementation, it's a good idea to open the resulting URL and ensure that the search engine crawler receives the same code generated by the generator.
Step 1: Select the markup type
The markup type should match the main content of the page. Product is appropriate for a product card, Article or BlogPosting is appropriate for a publication, Organization is appropriate for an organization page, and LocalBusiness is appropriate for a local business with a physical address.
If a page contains multiple related objects, they can be described as separate entities. For example, an article might contain an author (Person), a publisher (Organization), and a breadcrumb (BreadcrumbList) breadcrumb, without repeating the same data across blocks.
Step 2. Fill in the details
Enter the title, URL, description, images, dates, and other information exactly as they appear to the user. Google structured data must be supported by the visible content of the page and should not contain fictitious characteristics.
If a value is missing, it's best to leave the field blank when the selected type allows it. Don't add a non-existent price, rating, author, or product availability to fill in all available properties.
Step 3: Get JSON-LD
After filling out the form, the generator creates a ready-made block with the application/ld+json type. It contains the entity, its properties, and values, written in JSON-LD syntax.
There's no need to re-enter this data manually. Before using, check URLs, numeric values, images, dates, and required fields, as even correct syntax won't correct incorrect input.
Step 4: Copy and check the code
First, validate the copied code using Schema.org Markup Validator and Google's tools for supported rich results. This validation helps find syntax errors, missing properties, and problems in the object structure.
After publishing, it's helpful to run a second check using the public URL. This can help you detect situations where the CMS has changed the code, the template has created a second Schema.org block, or the page's source code differs from the version in the generator.
Common mistakes when creating Schema.org microdata
Most issues are related to incorrect entity selection, outdated values, and attempts to pass data to the search engine that the user doesn't see. A separate group of errors appears after updating the CMS, theme, or SEO plugin.
Before publishing, it's helpful to run a short check: verify types, URLs, images, prices, currencies, dates, and related entities. After that, the code should be checked with a validator and tested on the public page.
Mismatch between markup and page content
The name, price, rating, address, and other properties must match the actual information on the page. If the user is shown one price, but the JSON-LD contains a different one, the markup becomes invalid.
Such discrepancies often arise on dynamic websites when the visible portion and structured data receive data from different sources. It's more reliable to use a single value store for the page and JSON-LD.
Fake reviews and ratings
Review and AggregateRating shouldn't be added just to get stars next to search results. Such data must be based on real reviews and a verifiable rating, accessible to the user on the page.
The same logic applies to the number of reviews and average rating. If the data changes, the markup should be updated along with the corresponding site block.
Invalid entity type
The type is selected based on the page's content, not the appearance of the desired result. A standard service page cannot be automatically considered a Product if its content and structure do not correspond to the selected entity.
Before generation, it's helpful to define the main page object and related objects. This reduces the number of unnecessary properties and makes the structure clearer for future maintenance.
Errors in JSON-LD
Manual editing sometimes results in missing quotes, extra commas, incorrect URLs, and invalid value types. It's also best to remove empty properties if they're not required for the selected structure.
The schema markup generator reduces the number of such errors, but after manual editing, the check must be repeated. Pay particular attention to dates, numbers, and nested objects.
Duplicate markup
A CMS, theme, and SEO plugin can all generate the same entity simultaneously. This results in multiple Organization, Article, or Product entries appearing on the page, each with a different ID and value.
Before adding a new block, review the existing source code. If the required entity is already automatically generated, it's safer to fix or extend the current implementation rather than adding an independent duplicate.
I view Schema.org as a technical way to more accurately convey page content to search engines. If a page doesn't have a rating, price, or reviews, I don't add them to the JSON-LD. After generation, I always check the syntax, the selected types, and whether the structured data matches what the user actually sees.
What types of Schema.org can be created?
The set of available types depends on the generator's functionality. The entity should be selected based on the actual page content, and additional properties should only be populated when the relevant information is actually present on the site.
For most commercial and informational projects, Article, Product, Organization, LocalBusiness, and BreadcrumbList are most commonly used. Additional entities help more accurately describe an author, offer, event, video, or the structure of a specific page.
Article and BlogPosting
Article is suitable for articles, news, and editorial posts, while BlogPosting is typically used for blog content. Common properties include headline, description, image, author, datePublished, and dateModified.
The publication date and modification date must correspond to the actual content of the material. It is advisable to describe the author by their real name or the associated Person entity when a dedicated specialist page exists on the website.
Product and Offer
Product describes the product, while Offer conveys the details of a specific offer: price, currency, and availability. For an online store, the name, image, description, SKU, and brand may also be used if this information is present on the product card.
The price and currency are transmitted separately: price contains the numeric value, while priceCurrency contains the currency code, such as UAH. A string like "20,000 UAH" in a single field creates the risk of incorrect value processing during automatic generation.
Organization and Local Business
Organization is suitable for describing a company, brand, or organization. The markup can include the name, primary URL, logo, contact information, and official profiles, as long as this information is relevant to the organization.
LocalBusiness is used for local companies with a physical location. Address, phone number, and business hours may be required, and all these values must match the information displayed to the user.
BreadcrumbList
BreadcrumbList describes the breadcrumbs and the page's position within the site structure. Each position contains the element's name and a link that corresponds to the user's actual path.
This type of markup is convenient to generate from template data, especially on large websites. When generating it automatically, ensure that URLs are absolute, positions are ordered, and names match the visible navigation.
FAQPage and QAPage
FAQPage is used for a page with questions and answers published by the website owner. QAPage refers to single-question pages where users can post their own answers.
These types aren't interchangeable, as they have different structures and purposes. Even a valid FAQPage doesn't guarantee a separate FAQ section in Google search results, so adding such markup should be tailored to the page's purpose.
Event, Person, WebSite, VideoObject and other types
Event is suitable for events with a date and location, Person is for a person, author, or specialist. VideoObject describes a video, and WebSite can convey site-wide data and related properties.
Before using an additional type, it's worth checking whether it's implemented in the generator and what mandatory properties are needed for a specific task. Adding a large number of entities without any connection to their content complicates the code and makes future maintenance more difficult.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history on a website builder. We built the semantic core for both cities, reworked the landing pages and built the link profile from zero. Four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and closed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
Answers to your questions
What does the Schema.org generator do?
The generator creates a ready-made JSON-LD based on the selected type and user-entered data. The resulting code can be copied, checked with validators, and added to a template or a specific website page.
This approach is especially convenient when you need to quickly prepare a basic structure without manually writing syntax. The final markup should still be reviewed before publication and after implementation.
Do I need to know JSON-LD to use the generator?
Filling out the form doesn't require in-depth syntax knowledge, as the code is generated automatically. The user simply needs to understand what object is on the page and what data actually pertains to it.
A basic understanding of the structure helps with subsequent testing and implementation. It's especially helpful to distinguish between the entity type, its properties, and related objects within a single JSON-LD block.
Which microdata format is best to use?
For many modern projects, JSON-LD is convenient because the code is stored separately from the main HTML markup. It's easier to generate from CMS data, update programmatically, and validate with specialized services.
Microdata and RDFa are also supported markup methods. The choice depends on the project architecture, but for new implementations, JSON-LD is often easier to maintain.
Can I use multiple Schema.org types on one page?
Yes, when each type describes the actual essence of the page and there are no contradictions between the objects. For example, a publication might contain an Article, an author Person, a publisher Organization, and a BreadcrumbList.
It's best to create related entities consistently and use the same identifiers where required by the architecture. This makes it easier for the developer to maintain data after site changes.
Does Schema.org guarantee a rich snippet?
A valid Schema.org doesn't guarantee a specific snippet format in Google search results. The markup must pass technical verification, be relevant to the page, and meet the requirements of the specific search function.
After this, the search engine itself decides whether to display the expanded result. Therefore, the results are assessed primarily on the accuracy of the data and the absence of errors.
Where can I check the generated JSON-LD?
The general structure can be easily verified using Schema.org Markup Validator. For Google features, the Rich Results Test is additionally used, which shows support for specific types and requirements for their properties.
After publishing, re-check the public URL. This helps detect changes made by the CMS, template, JavaScript, or third-party SEO plugin.
Is it possible to add a rating or reviews that are not on the page?
Adding fictitious Review or AggregateRating values is not allowed, as structured data must match real content. Rating and review count values must be supported by user-accessible information.
The same rule applies to price, product availability, and other commercial properties. The structured data generator should retrieve the actual values, not the data for the desired snippet type.
What if Yoast, Rank Math, or another SEO plugin is already running on your site?
First, check the source code and determine which entities the plugin already creates. Additional JSON-LD is only needed when the existing implementation is insufficient or cannot be configured correctly.
Pay special attention to Organization, Article, BreadcrumbList, and Product. Simultaneous generation of identical entities by different systems complicates diagnostics and can lead to inconsistent values.
Related services
Organization Schema Generator
Free Organization Schema Generator: Create JSON-LD markup for your company, add your name, logo, address, contact information, and sameAs, copy the code, and validate it.
BreadcrumbList Schema Generator
Breadcrumb Schema Generator for creating JSON-LD markup for BreadcrumbList. Add names and URLs, get the finished code, and validate it for Google.
Article Schema Generator
Free Article Schema Generator: Generate JSON-LD for Article, BlogPosting, and NewsArticle, copy the code, and validate the markup before publishing.
Product Schema Generator
Online Product Schema Generator: create JSON-LD microdata for your product with price, availability, brand, rating, and offer information. Copy the code and test it before publishing.
The Schema.org generator helps you quickly prepare JSON-LD for a specific page, but the quality of the result depends on the source data and the correct entity selection. After generating the code, check the properties, match them with the visible content, and test the published page using validators.
Select the desired Schema.org type, fill in the actual page data, and get the finished code. Before deployment, test the JSON-LD, and after publishing, repeat the test using the final URL.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: Schema.org Generator
What is Schema.org and JSON-LD?
Schema.org is a common vocabulary of types and properties used to describe entities on web pages. It defines Article, Product, Organization, Person, Event, VideoObject, and many other types, as well as the relationships between them.
JSON-LD is a format for storing structured data. It is stored as a separate block in the page's source code, eliminating the need for developers to add additional attributes directly to each HTML element.
How is Schema.org different from JSON-LD?
Schema.org defines the meaning of the data: what object is being described, what properties it has, and how different entities are related. JSON-LD defines the technical format for recording this information within a page.
In addition to JSON-LD, there are Microdata and RDFa, but for many modern projects, a separate JSON-LD block is more convenient. It's easier to generate dynamically, update along with site data, and validate without interfering with the main HTML markup.
Why do we need structured data?
Structured markup helps search engines more accurately recognize page content and relationships between objects. For example, "Product" indicates that the crawler is looking at a product, "Organization" describes the company, and "BreadcrumbList" conveys the structure of breadcrumbs.
For some supported types, Google may use this information when generating a rich result. Having the correct code alone does not guarantee a rich result, as the final snippet format depends on the requirements of the specific search function and Google's algorithms.
How do I choose the appropriate Schema.org type for my page?
The selection begins with the page's main object, as it defines the core essence of the markup. A single URL can contain multiple related types, as long as each describes the actual information presented and helps convey the document's structure.
For a quick check, you can use the table below. It shows common options, but the final choice depends on the specific page's content and search engine requirements.
| Page type | Recommended type |
|---|---|
| Article or publication | Article / BlogPosting |
| Product card | Product + Offer |
| Company page | Organization |
| Local business | LocalBusiness |
| Breadcrumbs | BreadcrumbList |
| Event | Event |
| Author or specialist | Person |
| Video page | VideoObject |
On complex pages, it's best to link entities together when the site architecture and generator support this pattern. This helps avoid multiple independent descriptions of a single company, author, or page with different meanings.
What Schema.org fields need to be filled in?
The set of properties depends on the selected type and the requirements of the search function. Some fields are based on the Schema.org vocabulary, while others may be required or recommended for a specific Google rich result.
Therefore, before implementing, you should check the documentation for the desired type and the page itself. A valid Schema.org object may contain the correct properties but still not meet Google's requirements for a particular rich snippet.
Required and recommended properties
Required properties are needed for a specific function or type of validation, while recommended properties add useful information about the entity. These should only be populated with real data that can be verified by the page content.
If the generator displays a warning about a missing required property, first check that the value exists on the site. If the data is missing, it's better to change the page structure or remove the corresponding function than to invent a value.
What to do if the required data is not available?
Missing information cannot be replaced with fictitious values, as the markup must describe the actual content. This is especially true for Review, AggregateRating, Offer, price, availability, and company information.
If a page doesn't have user reviews, adding AggregateRating to gain stars in search results is prohibited. A similar rule applies to product price, availability, author, address, and other information that may be verified by search engines.
How to add JSON-LD to a website?
The completed JSON-LD is placed in the HTML page within the tag. The specific method depends on the CMS, template engine, and where the values that should be included in the structured data are stored.
For dynamic pages, it's preferable to pull data from the same fields that generate the visible content. This way, the price, title, URL, image, and other values are updated simultaneously, reducing the risk of discrepancies between the page and the markup.
Where to insert JSON-LD?
JSON-LD can be added to a page's source code via a template, component, content management system, or server-side rendering. After implementation, open the completed URL and verify that the block is present in the search engine-readable HTML.
If a site uses JavaScript to generate data later, you should check the final result Google receives. For critical SEO markup, it's more reliable to return the correct values during server-side page generation.
How to add markup via CMS?
In a CMS, markup can be generated automatically from page fields or added as a separate code block. The former option is more convenient for repeating templates, as the values change along with the product, article, or company page.
If the system already generates Schema.org, you should first check the existing code. A second schema.org generator, applied on top of the existing markup, sometimes creates duplicates of Organization, Article, or Product with different data.
WordPress
In WordPress, structured data is often created by SEO plugins or specialized Schema.org plugins. Before adding your own block, you should check the source code and determine which entities are already generated automatically.
When implementing code manually, it's best to add it via a child theme, snippets plugin, or managed template. This way, the changes will persist after updating the main theme, eliminating the need to re-apply the markup after each update.
Designers and SaaS platforms
Website builders typically offer a custom HTML field or a separate page code setting. In this case, a schema generator helps generate a ready-made block, which is then inserted into the system's designated location.
After publishing, be sure to check the source code of the resulting URL. Some platforms filter user scripts, modify content, or add their own markup on top of the inserted JSON-LD.
Custom Websites and SSR
On SSR-based websites, JSON-LD is conveniently generated directly from page data during server rendering. This approach reduces the risk of discrepancies between the product page, metadata, and structured properties.
Manually inserting changing values into a shared component is undesirable. Price, URL, images, availability, author, and other properties should be populated from relevant fields on a specific page.
How to validate Schema.org after generation?
Verification is necessary both before and after the page is published. The first stage helps find errors in the JSON-LD structure, while the second shows what code is actually accessible to search engines in the final URL.
The json ld generator reduces the risk of syntax errors, but it doesn't validate all entered data. Therefore, automatic validation should be supplemented by a simple comparison of the markup with the page content.
Checking with Rich Results Test
Rich Results Test is used for structured data types supported by Google search functions. The service displays detected entities, critical errors, and warnings for required or recommended properties.
A successful check means that the markup meets the technical requirements of a specific test. It doesn't necessarily mean that a rich result will appear the next time the page is indexed.
Validation via Schema.org Markup Validator
Schema.org Markup Validator helps validate your structure against the Schema.org vocabulary. It's a convenient way to find incorrect types, properties, and errors in relationships between entities.
This check should be used in conjunction with Google's tools, as the two services serve different purposes. One checks for compliance with a common dictionary, while the other focuses on supported Google Search features.
Post-publication review
After placing the code, open the public page and repeat the test using the URL. Then check the source code, canonical tags, meta robots tags, and the page's indexability, as correct semantic markup won't fix technical restrictions.
After re-crawling a page, its status can be monitored in Search Console if the selected type has a corresponding report. It's recommended to repeat the check if the template or CMS changes.
Why doesn't a valid Schema.org guarantee a rich result?
Several validation steps separate a valid JSON-LD from the actual rich result. The code must have the correct syntax, comply with the dictionary, meet Google's requirements, and accurately describe the visible content of the page.
Even after these conditions are met, the search engine independently decides whether to use additional elements in the search results. Therefore, the schema.org generator should be viewed as a means of preparing correct data, not as a mechanism for obtaining a guaranteed snippet.
How does Schema.org's validity differ from Google's requirements?
Schema.org contains a universal vocabulary for a large number of entities and scenarios. Google supports a subset of types for search functions and sets its own requirements for required and recommended properties.
Because of this, code may pass the general validator but fail for a specific rich result. For SEO testing, it's helpful to check both levels and consult Google's current documentation for the selected type.
Why might Google not show a rich result?
This could be due to an unsupported type, a missing required property, or a discrepancy between the JSON-LD and the visible text. Issues also arise when the page is blocked from indexing, contains inconsistent data, or violates the requirements of a specific feature.
Even a completely correct page may be displayed as a simple snippet. Google decides on the result format, so markup should be assessed based on its technical correctness and the quality of the data transmitted.
Mixing price and currency
For Offer, the numeric value and currency are passed as separate properties price indicate the price value, and in priceCurrency– currency code, for example UAH, EUR or USD.
This format is easier for automated systems and validators to process correctly. Before publishing, also check that the total matches the price the user sees on the product page.
Schema.org and SEO: What Does Structured Markup Provide?
Schema.org helps search engines more accurately interpret page entities, their properties, and relationships. For SEO, this is a useful technical layer, especially on sites with products, articles, organizations, authors, and recurring templates.
Structured data doesn't replace high-quality content, internal links, indexing, or a technically sound website. Its purpose is to convey existing information in a machine-readable form.
Does Schema.org affect website rankings?
Adding Schema.org doesn't guarantee a ranking boost. Search engines evaluate pages based on multiple signals, so markup can't be used as a substitute for proper optimization.
The benefits include more accurate content descriptions and the ability to participate in supported extended search formats. For large sites, a consistent description of entities across all templates is an additional advantage.
How does microdata relate to snippets and CTR?
For some search types, Google may use structured data when creating a rich result. This snippet can contain additional information if the page meets technical requirements and the selected feature is available for that type.
Enhanced display can sometimes make results more visible, but it's impossible to predict CTR based on the presence of JSON-LD alone. First, you need to ensure the data is correct, the page is indexable, and it meets Google's requirements.