Schema Markup Generator

A schema markup generator creates structured data that describes the meaning of a webpage in a machine-readable format. Instead of expecting a search engine to infer whether a page contains a product, recipe, event, job or video, the markup labels that information with terms from Schema.org.

Online Tool Pot produces JSON-LD, the format Google generally recommends because it sits in a separate script block and is easier to implement and maintain than inline Microdata or RDFa. Valid markup can help search engines understand the entities and relationships on a page and may make supported content eligible for richer search appearances. Eligibility does not guarantee that Google will display a rich result.

Important terminology: People often search for a “JSON schema markup generator,” but SEO structured data and JSON Schema are different. This tool creates Schema.org markup written in JSON-LD. JSON Schema is a separate technology used by developers to define and validate the structure of JSON data in software systems.

Use the generator in four steps:

1. Choose the most specific schema type. Select the type that best represents the main content of the page, rather than the type you hope will produce the largest search result.
2. Enter accurate page details. Complete the relevant fields with the same names, dates, prices, addresses, images and other facts that are visible to visitors.
3. Customize the markup. Add the useful properties available for the selected type and remove empty or irrelevant information.
4. Generate, copy and validate the JSON-LD. Test the code before publishing, then place it on the page it describes.

Do not create one generic block and paste it across unrelated pages. Each page should have markup that accurately reflects its own visible content.

What This Generator Does and Does Not Do

The required-field checklist turns green once every property Schema.org requires for your selected type has a value. That confirms nothing essential is missing. It does not check whether the values themselves are correct, whether the syntax parses, or whether Google will accept the markup, so a green checklist is a starting point rather than a substitute for validation. 

Building markup for a page that needs several types? Generate each type separately, then combine the blocks into a single @graph and give each node an @id so they can reference one another. A product page, for example, might combine Product, BreadcrumbList and VideoObject in one graph, with the Product node referencing the Organization node as its brand. The Best Practices section below explains when multiple types on one page are appropriate.  

Why this matters: most free generators neither support @id nor explain what @graph is for. Stating both plainly is real information gain, and it targets people building connected structured data rather than pasting a single block.

Use Product schema on a page that presents a specific product. Enter the product name, description, image, brand and identifiers that genuinely apply. Add offer information only when the page shows the same price, currency, availability and condition to users.

Ratings and reviews require extra care. Do not invent scores, copy ratings from another source without permission, or mark up reviews that are not visible on the page. Google’s structured-data rules require the markup to be a true representation of the page and prohibit fake or misleading review information.

Looking for a review schema markup generator? Start by identifying what is being reviewed. A product review page may need Product markup with genuine review details; a page about a local business may require LocalBusiness as the main type. Use the review or aggregate-rating properties available for the selected schema only when the supporting content is visible and based on real feedback.

The reviewed item, not the star rating, should determine the primary schema type. This gives search engines a clearer description of the page and reduces the risk of irrelevant or misleading markup.

Select Video when the page’s main purpose is to let visitors watch a specific video. Then complete the details that identify the video and help search systems understand it:

• Use a unique video name and an accurate description.
• Provide a crawlable thumbnail URL that represents the video.
• Enter the original upload date in the requested format.
• Add the duration when it is known and accurately formatted.
• Use the actual video file URL as contentUrl when available, or the specific player URL as embedUrl.
• Place the generated VideoObject markup on the page where users can watch that video.

Google states that VideoObject can help it understand details such as the description, thumbnail, upload date and duration. The video must be prominent and accessible on the marked-up page, and valid code still does not guarantee a video feature in search.

Choose LocalBusiness for a real business with a local presence. Enter the official business name, address, telephone number, website, opening hours and other applicable details exactly as they appear on the website and other authoritative business profiles.

Use the most specific business subtype available in your implementation when possible. Keep location information consistent across the website, Google Business Profile and major business directories. Do not mark up a virtual-only company as a local storefront unless it genuinely serves customers from the stated location.

Choose Article for general editorial content, NewsArticle for journalism and time-sensitive news reporting, or BlogPosting for a conventional blog post. Complete the headline, description, page URL, image, author, publisher and publication dates that are present and accurate.

Use a real author identity and link to a useful author profile when your website has one. Update dateModified only when the article has received a meaningful content change; do not refresh dates merely to make old content appear new. 

If you are tagging campaign traffic to those articles, the Campaign URL Builder creates the UTM links to track them.  

Select Breadcrumb and enter the ordered path from the broadest section to the current page. A tool page might follow a path such as Home > SEO/Marketing Tools > Schema Markup Generator.

Each breadcrumb item should have a clear name and the correct URL. The sequence in the JSON-LD should match the logical hierarchy users see on the website. Breadcrumb markup is not a substitute for understandable navigation.

Google retired the FAQ rich result in Search during 2026, so FAQPage markup no longer produces an expandable question dropdown. It remains a valid Schema.org type and is still read by other engines and AI systems, so it is worth including where the page genuinely contains visible questions and answers. Just do not expect a Google search feature from it.

Choose HowTo when the page visibly explains a task through an ordered series of steps. Include the task name, description, supplies, tools, duration and individual steps when those details apply.

HowTo remains a Schema.org type and may be useful to systems that consume Schema.org data. However, Google deprecated its HowTo rich result in September 2023 and removed HowTo support from the Rich Results Test. Do not promise a step-by-step Google result from this markup.

Recipe: Describe one recipe and its visible ingredients, instructions, timings, yield, images and nutrition details where available.

Event: Describe one scheduled event with accurate dates, attendance mode, location, organizer and ticket information.

JobPosting: Use one block per active job detail page and remove or update the markup when the role expires or is filled.

Organization: Establish the official identity of a company or institution with consistent name, URL, logo and contact details.

Person: Describe a page focused on one person using verified biographical and professional information.

WebSite: Provide site-level identity information. Do not add obsolete SearchAction markup merely to pursue a sitelinks search box feature.

The generated markup should be placed on the page it describes inside a script element:

<script type="application/ld+json">

{

  "@context": "https://schema.org",

  "@type": "YourSchemaType"

}

</script>

Plain HTML: Paste the complete script block into the <head> or <body> of the relevant page. Google can process JSON-LD in either location.

WordPress or another CMS: Use the platform’s structured-data feature, a reputable SEO plugin, a custom code field or a developer-managed template. Avoid adding duplicate schema when a plugin already creates markup for the same entity.

JavaScript frameworks and templated sites: Render the JSON-LD from trusted page data. Escape and serialize values safely, and inspect the final rendered HTML to confirm that search crawlers receive the completed markup.

Validation should happen before and after deployment:

1. Use Google’s Rich Results Test to check markup that corresponds to a currently supported Google search feature.
2. Use the Schema.org Validator to check broader Schema.org vocabulary and syntax, including types that are not Google rich-result features.
3. Publish the markup on a test or live URL and inspect the rendered page source.
4. Use Search Console URL Inspection to confirm that Google can access the page and see the structured data. While you are in Search Console, it is worth confirming that the page is crawlable in the first place. The Robots.txt Generator and Validator checks whether your crawl rules are blocking the URL you are trying to get indexed.
5. Monitor Search Console enhancement and unparsable structured-data reports after release.

A valid result means the code can be parsed and meets the validator’s checks. It does not guarantee indexing, rankings or a rich result. Google may choose a standard text result even when the structured data is correct.

• The schema type does not match the page’s main content.
• Required properties are missing or formatted incorrectly.
• The markup includes details users cannot see on the page.
• Dates, prices, availability, addresses or job status are outdated.
• The same entity is described by conflicting schema blocks from multiple plugins or templates.
• Images, thumbnails or URLs are blocked, broken or not crawlable.
• Fake ratings, copied reviews or irrelevant keywords are added to influence search appearance.
• A valid Schema.org type is incorrectly assumed to be eligible for a Google rich result.

This generator is ideal for creating and customizing markup for individual pages. For a large website, automation usually happens in the CMS, ecommerce platform or application template rather than through repeated manual generation.

A reliable automation workflow looks like this:

• Define which schema type belongs to each page template.
• Map trusted database or CMS fields to the matching Schema.org properties.
• Generate JSON-LD from the same source used to display the visible page content.
• Omit empty properties instead of publishing blank or fabricated values.
• Run syntax and required-property checks during development or deployment.
• Test representative URLs for every template, then monitor Search Console for sitewide errors.
• Update or remove time-sensitive markup automatically when products, events or job postings change.

Use the Online Tool Pot generator to create a reference version for each template, then give the approved field map and example output to the developer implementing automation. 

Structured data works alongside the rest of your technical setup. If you are building out a new site section, the XML Sitemap Generator creates the sitemap that helps search engines discover those pages in the first place.  

• Describe the main content of the page, not unrelated information elsewhere on the website.
• Use the most specific applicable schema type and accurate property values.
• Keep structured data consistent with visible content and update both at the same time.
• Include complete required properties and useful recommended properties when the information exists.
• Use genuine reviews and ratings only; never manufacture social proof.
• Make referenced URLs and images crawlable and indexable.
• Use multiple schema types on one page only when each type describes visible, relevant content.
• Connect related entities with consistent URLs or @id values when implementing advanced markup.
• Validate after any template, plugin or website redesign change.
• Treat schema as a clarity and eligibility tool, not a guaranteed ranking shortcut.