Schema Markup Generator

What is a schema markup generator, and what does this one create?

A schema markup generator turns the facts on your page into JSON-LD code that search engines can read without guessing. You fill in a form; the tool puts the schema.org property names, nested objects and quotation marks in the right place. As a result, you skip the missing commas and brackets that break most hand-written snippets.

The tool covers six types:

• Organization: brand name, logo, contact details and social profiles.
• LocalBusiness: business type, address, coordinates and opening hours.
• Article: headline, author, dates and cover image.
• Product: price, availability, brand and rating.
• FAQPage and BreadcrumbList: a question and answer list, plus the page path.

Google supports JSON-LD, Microdata and RDFa. In practice, my team and I use JSON-LD on client sites because the code sits in its own block and never touches the visible HTML. If you want the basics first, read my guide to schema markup. Everything here runs in your browser, so nothing you type reaches a server.

Which schema type belongs on which page?

In short, the main topic of the page decides the type. Google's general guidelines say the same thing: markup should describe the page it sits on and use the most specific type that applies. This is the mapping I follow when I set up a site:

• Homepage or About page: Organization. One page with your company details is enough.
• Contact or location page: LocalBusiness, ideally with a subtype such as Restaurant or Dentist.
• Blog post or news story: Article, BlogPosting or NewsArticle.
• Product detail page: Product. Google wants this markup on a specific product, not on a category or a list of products.
• Category and deeper pages: BreadcrumbList.

Also, several types can live on one page. For example, a blog post can carry Article and BreadcrumbList side by side, and a product page can carry Product and BreadcrumbList. This tool builds one type at a time, so for a second type you switch at the top and copy that block separately. On online stores, my team and I settle this mapping at the very start of an e-commerce consulting project, because changing templates later costs far more time.

Local business markup: address, coordinates and opening hours

For LocalBusiness, Google requires only two fields: the business name and its address. However, the recommended fields matter just as much for matching your business correctly. I suggest filling the tool in this order:

1. Business type: Google recommends the most specific subtype. Pick Restaurant, Electrician, Dentist or whatever fits from the list; if nothing fits, keep the general LocalBusiness.
2. Address: street, city, state or region, postal code and the two-letter country code (US). Also keep the spelling identical to your Google Business Profile.
3. Coordinates: Google asks for at least 5 decimal places for latitude and longitude. On desktop, right-click your business in Google Maps and the coordinates appear at the top; one click copies them.
4. Opening hours: choose the open days plus opening and closing time. If Saturday hours differ, add a second OpeningHoursSpecification object after you copy the code.
5. Price range: a short marker such as $$ does the job; Google wants this field under 100 characters.

Your visibility in Maps still comes mainly from your Google Business Profile. The markup, in other words, is a supporting layer that shows your site agrees with the profile. I cover the profile side in my Google Maps SEO guide.

How do you write prices and ratings correctly in Product markup?

Google's rule for product snippets is clear: next to name, you need at least one of review, aggregateRating or offers. The tool builds an offers object when you enter a price. It builds an aggregateRating object when you enter both a rating and a review count.

Specifically, two details decide whether the price works. First, the price field holds a plain number with a dot as the decimal separator; Google's own example uses 1.23, not 1,23. That is why the tool turns 1,299.90 into 1299.9. Second, the currency goes into priceCurrency as an ISO 4217 code such as USD, GBP or EUR; the $ sign does not belong there.

With ratings, honesty comes before syntax:

• Mark up a rating and review count only if the product page actually shows them.
• Google bans reviews that do not reflect a genuine experience. It also bans incentivized reviews that hide the money, discount or free product behind them; that point entered its guidelines in July 2026.
• On LocalBusiness and Organization pages, reviews the business controls about itself do not qualify for review stars.

In the stores I set up, I only map ratings that come from the review system and appear on the page. Anything else simply raises your own risk of a manual action.

Are FAQ and breadcrumb markup still worth adding?

Short answer: breadcrumbs yes, FAQ rich results no. In August 2023 Google limited FAQ rich results to well-known, authoritative government and health sites. According to the Search Central update log, the feature stopped appearing in Search altogether on May 7, 2026. The same log lists an earlier cleanup from June 2025. At that point Google added deprecation notices to Course info, Estimated salary, Learning video, Special announcement, Vehicle listing and Practice problem.

I still kept the FAQPage type in the tool. FAQPage remains a valid schema.org type; Google removed the rich result, not the vocabulary. It also helps when you clean up or rewrite old FAQ markup on existing sites and need to see a correct structure.

Breadcrumbs, on the other hand, are a different story. With its January 23, 2025 announcement, Google stopped showing breadcrumbs in mobile results and now shows only the domain there. On desktop, breadcrumbs still appear and Google still supports the markup. So I keep adding BreadcrumbList on sites with deep category structures. Google needs at least two ListItems, and every step except the last one needs a URL.

How do you add the schema markup generator output to your site?

The tool hands you a ready block with script tags. How you add it depends on your platform:

• Hand-coded site: paste the block into the template of the right page, ideally inside the head element.
• WordPress: use your theme's header code field or a plugin that lets you insert code into the header.
• Hosted e-commerce platform: the product template often outputs Product markup already. First search the page source for ld+json, then add only the type that is missing.

Above all, the code must sit on the page it describes. Organization markup belongs once on the homepage or About page, while product markup belongs only on that product's page. If you repeat the same details on several pages, make sure the values match everywhere.

When I add schema, I also review the title and description tags in the same template, because they live in the same head section. The Meta Tag Generator also speeds that part up. On a multilingual site, give each language version its own markup, with names and descriptions written in that page's language.

How should you test the code before it goes live?

I run every snippet through two separate checks, because the two tools answer different questions:

1. Rich Results Test: shows whether the code qualifies for a rich result Google supports. You can paste the code or enter a live URL.
2. Schema Markup Validator: checks the code against the schema.org vocabulary without Google-specific rules. This is where you check types that Google no longer displays, such as FAQPage.

After launch, monitoring moves to Search Console. The reports in the Enhancements section list valid and invalid items on crawled pages, while URL Inspection shows how Google sees a single page. I explain how I read these reports in my Search Console guide.

Keep one more thing in mind: even flawless code does not guarantee a rich result. Google states plainly that it does not guarantee your structured data will show up in search results; its algorithm decides which feature appears. Therefore, after a clean test, give the reports a few weeks before you draw conclusions.

What do rich results add to clicks, and where is the limit?

Google shares its own case studies in its introduction to structured data. According to that page, Rotten Tomatoes measured a 25% higher click-through rate on pages enhanced with structured data compared with pages without it. In the same document, Nestlé reports an 82% higher click-through rate for pages that show as rich results than for non-rich result pages.

Still, those numbers belong to those sites; nothing guarantees the same lift on yours. Here is what I see in practice:

• Product results with price, stock and stars stand out among plain competitor listings.
• A weak title and description do not turn into clicks just because a rich result appears.
• If a page is slow or hard to crawl, schema will not save it.

That is why I treat schema as the last layer on top of solid technical foundations. I look at speed, crawlability and internal linking first; my checklist is in the technical SEO article. You can also preview your title and description with the Google SERP Preview tool. If you would like to look at the whole site together, see the SEO consulting service my team and I offer.