Summary
The free schema markup generator writes valid JSON-LD for five schema.org types: Article, FAQPage, LocalBusiness, Product and HowTo. Pick a type, fill in the form, copy the code and paste it into your page, then test it in Google's Rich Results Test. In 2026, Product, Article and LocalBusiness markup can still earn enhanced results in Google; FAQ and HowTo no longer do, but they still describe your content to any system that reads schema.org.
Want to go further? Ask
A schema markup generator turns facts about a page into structured data that machines read without guessing: who wrote the article, what the product costs, where the shop is. Google says it "uses structured data that it finds on the web to understand the content of the page" and recommends JSON-LD as the format, a script block that sits apart from your visible HTML (Google, introduction to structured data). Writing that block by hand invites syntax errors; the generator builds it from a form.

Which schema types does the generator support?
Five types, chosen because they cover most business websites. Each tab shows the main fields first, and a "More fields" section for the optional ones.
| Type | Use it for | Main fields | Google rich result in 2026 |
|---|---|---|---|
| Article | Blog posts, news, guides | Headline, author, publisher and logo, dates, image, URL | Yes: article details such as title, image and dates |
| Product | Product pages | Name, brand, SKU, price, currency, availability, rating | Yes: price, availability and review stars |
| LocalBusiness | Shops, agencies, practices | Name, address, city, postal code, country, phone, price range | Yes: business details in a knowledge panel or a carousel |
| FAQPage | A list of questions and answers | Up to 3 question and answer pairs | No: removed from Google Search in May 2026 |
| HowTo | Step-by-step tutorials | Title, total time, up to 3 steps | No: deprecated in September 2023 |
The generator runs in your browser: nothing is sent to a server and there is no daily limit.
How do you add the generated schema to your page?
Copy the code and paste it into the HTML of the page it describes. Google reads JSON-LD placed in the head or in the body.
- Choose the type that matches the main content of the page, not the site as a whole.
- Fill in the fields with the exact information visible on the page: same price, same author name, same address.
- Generate and copy the JSON-LD block, which already includes its script tag.
- Paste it into the page head, or into a custom code block in WordPress, Webflow or Shopify.
- Test the live URL with the Rich Results Test, then watch the enhancement reports in Search Console.
The order matters at step 2. Google's guidelines say: "Don't mark up content that is not visible to readers of the page" (Google, structured data general guidelines). A price in the markup that differs from the price on the page is a classic reason for a rich result to disappear.
Which schema type should you use for each page?
One main type per page, matching what the visitor came for. A product page gets Product, an article gets Article, the contact or home page of a local company gets LocalBusiness.
- Article: Google lists no required properties for it; add the ones that apply, and always the author and the dates, which help readers and machines judge freshness (Google, Article structured data).
- Product: Google distinguishes product snippets, for pages where people cannot buy, from merchant listings, for pages where they can (Google, product structured data). Fill in price, currency and availability whenever the product is for sale.
- LocalBusiness: the name and the address are the two required properties. Use the same name, address and phone number as in your Google Business Profile.
- FAQPage and HowTo: use them if the page really is a list of questions or a tutorial, for clarity, but do not expect a visual result in Google.
For the vocabulary itself, see our glossary entries on schema markup and rich snippets.
What changed for FAQ and HowTo rich results?
Google has been trimming its results page for three years. In August 2023 it reduced FAQ rich results and limited HowTo to desktop; in September 2023 it stopped showing HowTo results altogether (Google Search Central Blog, 2023). In June 2025 it phased out seven more types, including Course Info, Claim Review and Vehicle Listing, while stating that "this update won't affect how pages are ranked" (Google, simplifying the search results page). Finally, the FAQ rich result stopped appearing in Google Search on May 7, 2026 (Google Search Central, documentation updates).
| Date | Change in Google Search | What to do with existing markup |
|---|---|---|
| August 2023 | FAQ rich results limited to well-known government and health sites; HowTo limited to desktop | Keep it if the content is a real FAQ |
| September 2023 | HowTo rich results no longer shown | Harmless; no need to remove it |
| June 2025 | Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing phased out | No ranking impact; still valid outside Google Search |
| May 2026 | FAQ rich result no longer shown | Keep the visible FAQ section; it still answers readers |
None of these changes makes the markup wrong. They only remove a visual display in Google. The content described by the schema still has to be on the page, so a well-written FAQ section keeps its value for readers and for AI assistants that quote pages.

Breadcrumb schema generator: how to write BreadcrumbList markup
Breadcrumb markup describes where a page sits in your site, as a trail such as Home, Blog, Schema markup, then the page itself. Google can show that trail under a result in place of the raw URL. The generator above covers five types and does not build breadcrumbs, so you write this block yourself. It is short, and it is easy to check.
Google requires at least two items in the trail. Each item needs a position, where 1 is the start of the trail, and a name, the label people read. Each item also needs an item URL, except the last one: if you leave it out there, Google uses the URL of the current page (Google, BreadcrumbList structured data).
Build the trail around the visitor's path
Google advises building breadcrumbs around “a typical user path to a page”, not around your folder structure. A product page might read Home, Shoes, Running, then the product name. Keep each name identical to the link the visitor sees on the page, and show the whole trail on the page as well, since Google's general guidelines warn against marking up content that readers cannot see.
A three-level example
Wrap the JSON in a script tag with type="application/ld+json", placed in the head or the body. The last item has a name but no item URL, which Google accepts.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://www.example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Schema markup",
"item": "https://www.example.com/glossary-geo-seo/schema-markup"
},
{
"@type": "ListItem",
"position": 3,
"name": "Breadcrumb schema"
}
]
} Mistakes to avoid
- One item only. Google needs at least two list items.
- Wrong order. Count positions from 1 and increase them by one at each level.
- Relative links. Use full addresses starting with https://, as Google's examples do.
- Old formats. Data-vocabulary.org markup is no longer eligible for rich results, so write schema.org JSON-LD.
Test the block with the structured data validator before you publish, then check the live URL in Google's Rich Results Test. A clear trail also gives crawlers one more set of internal links, so it fits well with your internal linking plan.
Does schema markup improve rankings?
Not directly. Structured data helps Google understand a page and makes it eligible for richer displays, and those displays can win more clicks. Google's own case study list cites Nestlé, which measured that pages shown as rich results had "an 82% higher click through rate" than the others (Google, introduction to structured data). Eligibility is not a guarantee: Google decides when to show an enhanced result.
Do you need schema markup for AI Overviews and AI answers?
No special markup is required. Google states that "there's no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode, and asks that structured data match the visible text (Google, AI features and your website). Schema still helps any system identify entities without ambiguity: the author of an article, the brand of a product, the address of a business. Check how AI-ready your pages are with the structured data audit for LLMs and the AI Overview checker.
What are the most common schema markup errors?
Most errors come from content mismatch rather than from syntax, since the generator handles the syntax.
- Markup that differs from the page: a price, rating or address that is not the one visitors see.
- Self-serving reviews: star ratings for LocalBusiness and Organization are only eligible on sites that review other businesses, not on your own business page (Google, review snippet).
- A rating without real reviews: if you fill in the average rating, also fill in the true number of reviews.
- Relative or broken URLs for images and logos: use full addresses starting with https.
- The same schema on every page, pasted into a template: each page needs markup that describes that page.
Pair the schema with clean meta tags: the meta tags generator writes them, and the SERP preview tool shows how the result will look.
How do you keep structured data correct over time?
Re-test after every template change, and check the enhancement reports in Search Console each month. Prices, opening hours and authors change; markup that was right last year can become misleading. On a blog, the Sorank blog article generator includes JSON-LD schema and the FAQ section among the factors of each article's SEO score, so you see what is missing before publishing. Then follow the effect on your traffic and AI visibility in the GEO and SEO dashboard.
Valid, honest and page-specific: that is the schema Google can use. Generate your first block now, test it in the Rich Results Test, and see the Sorank plans to keep every page optimized on autopilot.
Local business schema generator: which fields to fill in
Local business schema is JSON-LD that describes a company with a physical location: its name, address, phone number and opening hours. It tells search engines which business stands behind a page, and it supports the business details Google can show in a knowledge panel or carousel. Only name and address are required, but Google advises including as many address properties as possible.
A local business schema generator saves you from syntax errors, but it cannot check your facts. Fill in the main fields first, then open the More fields section for the optional ones. The table below shows what each property expects.
| Property | Status | What to write |
|---|---|---|
| name | Required | The business name exactly as customers see it on your site and in your Google Business Profile |
| address | Required | A PostalAddress with street, city, postal code and country |
| telephone | Recommended | International format, with country code and area code |
| openingHoursSpecification | Recommended | The days, with opening and closing times |
| geo | Recommended | Latitude and longitude, each with at least 5 decimal places |
| priceRange | Recommended | A short range such as $$, under 100 characters |
| url | Recommended | A working link to the business website |
Here is a complete example for a coffee shop in Paris. Replace every value with your own.
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Coffee Roasters",
"url": "https://www.example.com/",
"telephone": "+33 1 23 45 67 89",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 Example Street",
"addressLocality": "Paris",
"postalCode": "75001",
"addressCountry": "FR"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 48.85661,
"longitude": 2.35222
},
"openingHoursSpecification": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "09:00",
"closes": "18:00"
}
} Mistakes that break the match
- Different details across sources. If the phone number or address differs between your site, your Google Business Profile and the schema, search engines have to guess which one is right. That is why name, address and phone (NAP) consistency matters.
- A phone number without the country code. Write it in international format, with the country and area code.
- Coordinates with few decimals. Google asks for at least 5 decimal places in latitude and longitude.
- Hours that changed but not in the markup. When your hours change, update the schema too, or it no longer matches the page.
Read the full walkthrough in our local business schema guide. The NAP guide explains why the same name, address and phone must appear everywhere, and the Google Business Profile guide covers the listing itself.
































































































